Thanks to all. I swear in the pantheon to all possible Gods that i did
nothing of the sort suggested by Lawson. That very day when boot crashed I
never went into root/su. BTW when I had all 'fixed' I tested booting twice
and it worked till the third time.
Now I am back in Linux with reinstall. All went smooth. Doing e2fdsk -p
/dev/hda8, my root now, it dit a forced check. Then doing e2fdsk -p
/dev/hda9, my swap now, I get:
[root@Peter /]# e2fsck -p /dev/hda9
e2fsck: Bad magic number in super-block while trying to open /dev/hda9
(null):
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What have I to do with this?
And yes it's me who gets those messages:
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
ide0: reset: success
What is the meaning of it?
Now I am scared to shutdown.
>On Thu, 29 Mar 2001 [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> When I tried to boot this morning after a normal shutdown of RH6.2
>> the evening before I received the following message:
>>
>> Activating Swap: /dev/hd8: invalid argument :[failed]
>>
>> the superblock could not be read or does not describe a correct
>> ext2 filesystem. Your might try running 2fsck with an alternate
>> superblock
>> e2fsck -b 8193 <device>
>>
>> Bad magic number in super-block while trying to open /dev/hda2:
>> [failed]
>
>> Now on the second booting the same problem appears again.
>
>> What have I to do to solve the problem.
>The canonical answer to that is:
>Undo whatever you did to cause it.
>I doubt /dev/hd8 is a swap partition, or even a device at all.
>
>The easiest way to get a bad superblock message is to try to mount
>something that has no filesystem on /, either with a wrong or missing
>root = in lilo.conf (the kernel will use whatever is compiled in or set
>with rdev if a bootloader does not tell it, and unless it was compiled
>on a box with the same configuration the default is unlikely to be
>right.)
>
>If /dev/hda2 really is your / partition, though, I guess you must be
>doing something more ingenious.
>You could wreck the superblock by doing, say
>ls >/dev/hda2
>or
>cat /dev/zero >/dev/hda2
>or even
>dd of=/dev/hda2 bs=1024 seek=1 count=1 </bin/sh
>I guess if you are getting as far as a normal shutdown, though, you must
>be doing it in the shutdown scripts. You might try
>ls -l /etc/rc.d/rc0.d
>to see what those are.
>
> Thanks
> Peter
>I guess that might not be too helpful. Sorry. It is the best I can
>think of just now.
>Lawson
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
