-Original Message-
From: Axalon Bloodstone [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Monday, November 22, 1999 6:13 PM
Subject: Re: [expert] Re: [newbie] need help
On Mon, 22 Nov 1999, John Aldrich wrote:
On Mon, 22 Nov 1999, you wrote:
To append the directly above:
I copied the bootup screen messages and the relative part
is as follows.
Checking filesystems
fsck.ext2: Bad magic number in super-block while trying to open
/dev/hdb1
(null):
The super block could not be read or does not descirbe a correct ext2
file system ( and not swap or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 device
Try booting with a "rescue" disk and then "chroot
/dev/hdxx" (drive partition where / is located.)
Then, mkswap /dev/hdb1. It *should* re-format the swap
space, I think. Before you do this, though, you should wait
awhile to see if someone (Axalon???) can provide a better
suggestion. It *sounds* as if your swap space is FUBARED!
John
Sorry wasn't following along, if it's just a swap drive reformat is ok.
whats the partition layout (again?) i thought the bad fs was hdc#
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
Axalon,
Yes the hdc drive is the non bootable drive but the one bootup message
applies to the most recent LM 6.1 installation on hdb's swap file.
My total system except for cd-rom drives:
hda..dos
hdb LM 6.1 , last installation , boots OK but swap file
(irregularity?)
hdb1./swap
hdb2./
hdc.LM 6.1 my main installation , been using for awhile which
now
does not boot per info previously provided but
pasted again
below to bring you up to speed :-)
hdc1.../boot
hdc2../swap
hdc3../
hdc4..extended
hdc5../usr/local
hdc6../usr
The problem started directly after installing LM on hdb.
snip
John,
When I fsck the partitions they all check clean except if I
fsck /swap or / . When I check / a warning note comes
up saying If I fsck a mounted file system serious damage
could occur so I backed out.
Thanks
Larry
To append the directly above:
I copied the bootup screen messages and the relative part
is as follows.
Checking filesystems
fsck.ext2: Bad magic number in super-block while trying to open /dev/hdb1
(null):
The super block could not be read or does not descirbe a correct ext2
file system ( and not swap or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 device
/dev/hdc1: clean (blah blah)
/dev/hdc6: clean "
/dev/hdc5: clean "
*** An error occured during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type control-D for normal startup):
-
The first few lines of the above message "Bad magic number" is indeed
talking about a swap file on the hdb drive. This is the drive that I just
installed the second MD 6.1 and is booting OK. But I don't know why the
message is there? On that drive I have my swap partition first and the
/ partition is the balance of the drive. Normally I don't set it up that way
but during the install linux wanted to install it all in the / partition no
matter
how I set the partitions up it acted like I didn't have enough room in the
/ partition (even though I had it as 1 gb) so I just made it all /.
The last thing I tried is booted the MD cd-rom to due and "upgrade" on the
problem drive (hdc) even though I had installed "everything" before I
figured
it might straighten itself out that way. However, it couldn't mount hdc3 so
I had to back out.
Sorry for this long post but wanted to provide more info :-)
Larry
snip
Hope this is not too confusing,
Thanks to all for your help so far, I'm still working on it. BUT, I haven't
found the rescue image on the cd , just the readme about it and the
boot disk info and I already have a boot disk.
Larry
