New to Red Hat 7.2 is the --badblocks option, but that is done during formatting. zerombr and clearpart don't really do anything, especially if your disk is bad or has bad sectors. That way you can reboot any time before the format, and the partition will be left intact. Forrest I got it to work!! My entire kickstart setup was just fine, but something strange has happened with my hard drive. I use a utility called "badblocks", that can write a stream of zeros and ones to the hard drive, bit by bit, overwriting any MBR, partitions and filesystems, at a very low level. After doing this, Kickstart can partition and do everything as it's supposed to. Could my HD be going bad? Could ks have a bug that ignores: zerombr yes clearpart all part /boot --fstype ext3 --size 30 part / --fstype ext3 --size 3256 part swap --size 512 Perhaps there is another command I can give kickstart that will emulate badblocks?? (wishful thinking I suppose) -----Original Message----- From: Ryan Allen Sent: Thursday, December 20, 2001 3:24 PM To: 'kickstart-list@xxxxxxxxxx' Subject: RE: fdisk: can't find /dev/hda This is exactly what driving me nuts. When I comment out the partition info, then anaconda pauses asks me to run the partitioning utility, and then everything installs exactly how I want it. The partitioning info is the exact same as I've always had it. It worked perfectly when I was using NFS to install. But now it's coming from a CDROM. The hard drive it the same as before. This is starting to sound like a bug. However, I cannot believe that I am doing anything strange that hasn't been done before. I've wasted too much time searching the archives and I've found nothing. Anybody have nay ideas? thanks, Ryan -----Original Message----- From: Taylor, ForrestX [mailto:forrestx.taylor@xxxxxxxxx] Sent: Thursday, December 20, 2001 2:46 PM To: 'kickstart-list@xxxxxxxxxx' Subject: RE: fdisk: can't find /dev/hda What happens if you remove the partitioning info? Forrest yup. Same results when I add: zerombr yes It's like there are no IDE drivers being loaded. On <alt>+f4 I see a message: "unable to identify CDROM format" -- Ryan -----Original Message----- From: Taylor, ForrestX [mailto:forrestx.taylor@xxxxxxxxx] Sent: Thursday, December 20, 2001 12:21 PM To: 'kickstart-list@xxxxxxxxxx' Subject: RE: fdisk: can't find /dev/hda I switched to the boot.img floppy to put my ks.cfg on, and now I'm getting a strange error: Could not allocate requested partitions: Partitioning failed: Could not allocate partitions. Press OK to reboot your system. at the console (alt+F2), I try 'fdisk /dev/had' with the error "unable to open /dev/hda" . Is this a bug? Does this kernel not have IDE block devices compiled in? Anybody know the work around? ## A sample from my ks.cfg file: This worked fine with the bootnet.img disk bootloader --location=mbr install cdrom clearpart all part /boot --fstype ext3 --size 30 part / --fstype ext3 --size 3256 part swap --size 512 Thanks, -- Ryan Did you try the zerombr yes option? Forrest _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
