Hi Stephan,
I was able to get most of the things you asked. I believe this is a LVM disk system. The two disks appear as one volume under normal use. I could not get any information of e2label. The rest is below. I forgot to mention that I had an external disk drive connected via usb port when I shutdown and disconnected when the machine was off. Since it was a temporary disk I assumed that it would not matter, obviously not. Here are the fdisk -l, then the mtab (I did not find fstab, but found mtab instead) and finally the proc/partition information.
How do I skip the external disk part on booting as I am guessing that is the problem?
Thanks for responding so quickly.
Bobby
fdisk -l
Disk /dev/sda: 250.0 GB 250056000000 bytes
255 heads, 63 sectors/track, 30400 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 30400 244083577+ 8e Linux LVM
Disk /dev/sdb: 250.0 GB 250056000000 bytes
255 heads, 63 sectors/track, 30400 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 30400 244083577 8e Linux LVM
Disk /dev/sdc: 500.1 GB 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 60801 488384001 83 Linux
I did not find fstab, but found an mtab. It contains the following:
rootfs / rootfs rw 0 0
/proc /proc proc rw 0 0
/dev /dev tmpfs rw 0 0
/dev/pts /dev/pts devpts rw 0 0
/sys /sys sysfs rw 0 0
none /tmp ramfs rw 0 0
none /tmp/ramfs ramfs rw 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
/tmp/loop0 /mnt/runtime squashfs ro 0 0
/selinux /selinux selinuxfs rw 0 0
The content of /proc/partitions is
major minor #blocks name
7 0 85712 loop0
8 0 244195312 sda
8 1 104391 sda1
8 2 244083577 sda
8 16 244195312 sdb
8 17 244187968 sdb1
8 32 488386584 sdc
8 33 488384001 sdc1
---- Original message ----
>Date: Sat, 26 Apr 2008 22:08:07 +0200 (CEST)
>From: Stephan Wiesand <[log in to unmask]>
>Subject: Re: boot error during SL5.0 startup
>To: Bobby Barnett <[log in to unmask]>
>Cc: Scientific Linux Users <[log in to unmask]>
>
>Hi Bobby,
>
>On Sat, 26 Apr 2008, Bobby Barnett wrote:
>
>> Hi Troy,
>>
>> I have been using SL5 for about 6 months without any problems. I
>> installed this with CD's downloaded from your site. My machine is a Sun
>> workstation with 2 core and two disks that were linked together during
>> this install.
>
>what does "linked together" mean? MD? Hardware RAID? LVM?
>
>> I was in a hurry to logout on Friday morning and instead of logging out,
>> I hit shutdown instead. Now I can not boot the system. I get the error
>> fsck.ext3: Bad magic number in super-block while trying to open /dev/sdc
>> [FAILED]
>
>It's looking for a filesystem on an unpartitioned disk. That's not a
>standard setup (and one that Red Hat wouldn't support).
>
>> I can't seem to work around this. I briefly tried the rescue disk
>> without much success. This computer is for protein crystallographic
>> refinement and it is a one man shop, and unfortunately without a linux
>> support staff. Any suggestions would be appreciated.
>
>Universities... ;-) Could you try the rescue disk again? Choose "skip"
>when it asks whether it should try to detect and mount the filesystems,
>and let us know what's there/left - content of /proc/partitions, output
>of "fisk -l" for sda/b/c/d, output of "e2label" for all partitions,...
>If some partition seems likely to contain your /etc/fstab, mount it
>read-only and retrieve fstab. ...
>
>- Stephan
>
>--
>Stephan Wiesand
> DESY - DV -
> Platanenallee 6
> 15738 Zeuthen, Germany
Bobby L. Barnett PhD
Department of Chemistry
University of Cincinnati
PO Box 210172
301 Clifton Court
Cincinnati, OH 45221-0172
Phone:(513)556-9230 Lab:(513)556-9214
FAX:(513)556-9239
|
