fdisk hangs after bad Linux install
Kurt
just hangs there like it's accessing my disk. I once left it for an hour
and it go anywhere else. I can still get into my main partition.
Partition Magic reported a #114 error (undocumented).
The quick and dirty story:
I wanted to re-install RH 6.0 on my machine and accidentally chose
Workstation. Workstation bypasses the Linux fdisk utility and
automatically creates its own partitions at the end of my hard disk.
I wanted to make my own partition, so when I realized what was happening
-- I kind of freaked. I re-booted (I know, I know -- I'm regretting it) my
system midway through. So, my FATs were hosed a this point.
Thinking I could fix the process via Partition Magic, which I had on my
Windows partition, I had FAT errors that prevented me from running PM in
Windows. The DOS version also reported errors.
I was able to get into fdisk at this point, and was going to delete my
extended partition and re-create it. I didn't do anything in fdisk at the
time, but I was able to view table information and might possibly have
been able to select other menu items ( I assume this).
But the second time in fdisk, it started hanging up right after that first
screen.
Do I need a new copy of fdisk? I'd hate to have to re-do my system....
--
Posted via CNET Help.com
http://www.help.com/
Mike Kenzie
Are you using the linux version of fdisk?
just a hunch but the RH install created type 82 and 83 partitions and DOS
fdisk may not recognise them. Try goinhg in with the linux fdisk and
change the partition type to FAT or DOS what ever it's called in REd hat.
I'm running 2 installs of SuSE and 1 of Slakcware, with several DOS boxes
and 1 NT.
Chia Ah Tee, Joseph
scandisk.
If scandisk can't run , reboot again and run fdisk.
If all these won't work you need Disk Manager to the job.
Joseph Chia A T
--
Outsider (6.22/3.11)
to a message. Please try to do this Chia, otherwise it is very
confusing.
Regards,
Outsider
Doug Hassell
news:s20l7t...@corp.supernews.com...
> I can't getfdisk to get past the initial large disk warning screen. It
> just hangs there like it's accessing my disk. I once left it for an hour
> and it go anywhere else. I can still get into my main partition.
>
> Partition Magic reported a #114 error (undocumented).
>
> The quick and dirty story:
>
> I wanted to re-install RH 6.0 on my machine and accidentally chose
> Workstation. Workstation bypasses the Linux fdisk utility and
> automatically creates its own partitions at the end of my hard disk.
>
> I wanted to make my own partition, so when I realized what was happening
> -- I kind of freaked. I re-booted (I know, I know -- I'm regretting it) my
> system midway through. So, my FATs were hosed a this point.
>
> Thinking I could fix the process via Partition Magic, which I had on my
> Windows partition, I had FAT errors that prevented me from running PM in
> Windows. The DOS version also reported errors.
>
> I was able to get into fdisk at this point, and was going to delete my
> extended partition and re-create it. I didn't do anything in fdisk at the
> time, but I was able to view table information and might possibly have
> been able to select other menu items ( I assume this).
>
> But the second time in fdisk, it started hanging up right after that first
> screen.
>
> Do I need a new copy of fdisk? I'd hate to have to re-do my system....
>
> --
> Posted via CNET Help.com
> http://www.help.com/
Kurt,
That's pretty strange stuff, but what gets me is the part about how the
Linux setup was trying to create partitions at the *end* of the drive (not
always the best idea, especially when LBA vs. CHS translation is
in-question). Did you read any of the RH Technical Notes on whether you
should use CHS or LBA "mode" in BIOS?
Either way, it would seem that FDISK is trying to access a partition that is
beyond its ability (probably the case if the drive is controlled in CHS,
rather than LBA, mode)
Whichever mode the BIOS is in, switch it to the other (myself, I have Award
and they have that neat IDE HDD AUTODETECT feature; just answer "Y" to all
four prompts), boot to diskette and try FDISK again.
Beyond these, I would say that a more-potent utility is warranted. I
wouldn't, however, recommend Disk Mangler...er... Manager.
Try this, too...
- Boot clean to diskette (use F5 if the disk is designed to load any
drivers, just press it as you see "Starting [...]" while the disk is
booting. Also, be sure to have a copy of FDISK (even if its not the one
you've been using)
- When the A: prompt appears, enter this command:
FDISK /MBR
- The A: prompt will re-appear after a brief moment. Reboot then and try
running FDISK again (without the /MBR this time).
Good luck!
- Doug
Rez
used on a drive that's had linux partitions on it. I don't remember the
details tho have run into a couple folk who had this happen. More
below..
Outsider (6.22/3.11) wrote:
>
> You are supposed to use Re: in front of the subject when responding
> to a message. Please try to do this Chia, otherwise it is very
> confusing.
>
> Regards,
> Outsider
Some offline mail readers don't let you do that unless you add it
manually.
> Chia Ah Tee, Joseph wrote:
> >
> > If you can boot your computer with a boot disk in drive A then run
> > scandisk.
> > If scandisk can't run , reboot again and run fdisk.
> > If all these won't work you need Disk Manager to the job.
Actually, I have used EZDrive to nuke a stubborn partition. FDISK and
Disk MAnager both got hung up on a BIOS bug and marked a 1.2g drive as
504mb. EZDrive ignored all that and killed the unwanted partition for
me.
~REZ~