It's the HD partitioning: FDISK can't handle the situation. It thinks there is a logical partition in the extended partition after deleting the logical part. Hence, can't delete the ext. part. and hence can't delete the Pri. partition.
Found a procedure on www.fdisk.com that uses fdisk to force the creation of partitions with switches on the command line: fdisk 1/PRI:100 should create a 100 MB primary DOS partition--but fdisk later sees this as an active, primary partition of no size and unknown system. Also used fdisk 1/LOG:100 to force a logical partition into the extended partition, which worked. However, after fdisk successfully deleted this log. part., still couldn't delete ext. part. because fdisk still thought there was a logical partition in it. Whew, this is frustrating. Any suggestions? or is this drive now a model boat anchor? BTW, have tried disk druid from RH 7.1 and it doesn't seem to work either. Also a few fdisk /mbr attempts, too. Thanks much, Bill At 7/11/02 02:36 PM , you wrote: > I believe 03:08 is /dev/hda8. If something is wrong with that >partition, or you didn't really put your root file system on /dev/hda8, >neither your floppy nor any other boot system will be able to start up >linux with root on 03:08. What's really on /dev/hda8? If you think your >root is somewhere else, such as /dev/hda2, specify root=/dev/hda2 at the >lilo prompt during boot (or do the equivalent with grub if that's what you >use). > >On Thu, 11 Jul 2002, Bill Flanagan wrote: > > > Thanks for the suggestion about the check sum, but I got the disks from > > RedHat at a trade show. > > > > Same disk has loaded all the workstation packages, but still exits saying > > "unable to mount root fS on 03:08" which also happens on reboot from > > emergency floppy. > > > > Bill > > > > At 7/10/02 09:13 PM , you wrote: > > >-----BEGIN PGP SIGNED MESSAGE----- > > >Hash: SHA1 > > > > > >On Wednesday 10 July 2002 08:58 pm, William Flanagan wrote: > > > > Two questions: > > > > > > > > Is the archive searchable? > > > > > >Not in any useful way. However, it's archived and searchable here: > > >http://www.prairienet.org/library/redhat/ > > > > > > > Any hints on why 7.1 should end on "install exited abnormally" at a > > > > random points in loading packages? Has happened quite early, just > > > > after Xsystem started successfully, minutes before completing the > > > > projected-35-minute process, and in-between (as on Python). > > > > > >Did you burn your own disks? If so, have you verified that the iso images > > >and resulting disks have good md5sums? > > > > > >- -- > > >- -Michael > > > > > >pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt > > >Red Hat Linux 7.2 in 8M of RAM: http://www.rule-project.org/ > > >- -- > > >-----BEGIN PGP SIGNATURE----- > > >Version: GnuPG v1.0.6 (GNU/Linux) > > >Comment: For info see http://www.gnupg.org > > > > > >iEYEARECAAYFAj0s29AACgkQn/07WoAb/SvPwACgu7uFf43Uv0PTZZCZ5H2P6cYV > > >xFsAoKSLdzPRz3dOzN3zuSeUZ0YDKOA/ > > >=W5gQ > > >-----END PGP SIGNATURE----- > > > > > > > > > > > >_______________________________________________ > > >Seawolf-list mailing list > > >[EMAIL PROTECTED] > > >https://listman.redhat.com/mailman/listinfo/seawolf-list > > > > > > > > _______________________________________________ > > Seawolf-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/seawolf-list > > > >-- >Steven Yellin > > > >_______________________________________________ >Seawolf-list mailing list >[EMAIL PROTECTED] >https://listman.redhat.com/mailman/listinfo/seawolf-list _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
