First of all you need to determine whch HDD's you have on your system. Open /proc/ide directory and there you will see the real situation. Then do fdisk /dev/hd? (the one you found in the /proc/ide) type print and yuo will see the partition layout of the disk. Type q to leave fdisk without saving any changes.
Then start fsck for the disk partitions you have on your system for sure. Do not try to guess - find out the status for sure. Superbloks can be damaged on the partition. It's not a tragedy -they are restorable from the copies. Then you just need to say the fsck command which superblok to use.
But first find out your disks and partitions. Regards Ray
Evan Brown wrote:
Okay so I'm in single user mode, I do a fsck /dev/hdc0 and its says that it can't find a super block. so then I try /hdc1 and it says the same thing so I go into dev and there are like hdb11 - hdt7 like a billion entries. is that right? I didn't think there was supposed to be so many hd* entries.
Evan Brown
On Tue, 04 Nov 2003 11:09:06 -0700, Evan Brown <[EMAIL PROTECTED]> wrote:
So by logging into single user mode..how would one do that? and I would run it on hdc1 ?
Evan Brown
On Tue, 4 Nov 2003 10:55:13 -0700, Nathanael Noblet <[EMAIL PROTECTED]> wrote:
On Tuesday, November 4, 2003, at 08:25 AM, Evan Brown wrote:
I don't have anything else right now, if it does it again I will though. We had a power outage here last week, could that have affected my file system enough to cause this? is there some kind of scandisk utility to fix stuff besides the integrity check on boot?
I had the same problem awhile ago with a RH 9 box. The cron job that updates the locate db would crash the machine. I had to run fsck about 3 times to get the filesystem in proper working order. I thought the HD was dying and ordered new ones... Now I have new hardrives sitting on my desk.;) Anyway I'd guess it is that as well. So reboot into single user mode, run fsck on all partitions. Reboot.
