Lost root drive... will not boot...

We loaded SUSE Linux on a system with one SAS drive. Then we added an
additional SAS drive and everything was working fine. Then we adding a
third SAS drive and everything was still working fine. Then while we
closed the system the root drive’s data cable was accidentally pulled
out. When we tried to boot the system it would get to the install DVD
boot screen and then after waiting it try to boot from the hard drive.
At that point it would lockup. We saw in the boot sequence that the root
drive was missing. So we open the cabinet and put the dangling cable
back into its proper plug. The boot sequence now shows all the drives
but the system still hangs when it tries to boot from the hard drive. I
went into the recover system and checked with fdisk -l to see that the
root drive was properly partitioned. Everything looked fine. Does
anybody know how we can recover the system without reloading?

Ted

Hi
Boot from the DVD and select Rescue Mode, when it boots, just enter
root, hit enter at the password and run fsck on the drive partition.


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.12-0.7-default
up 5 days 16:44, 3 users, load average: 0.00, 0.03, 0.00
GPU GeForce 8600 GTS Silent - Driver Version: 256.35

malcolmlewis wrote:
>

> Hi
> Boot from the DVD and select Rescue Mode, when it boots, just enter
> root, hit enter at the password and run fsck on the drive partition.
>

That is a great idea. Unfortunately, it did nothing. The system still
hangs when trying to boot from the hard drive. We had a similar problem
with another system. On that system someone was adding two SAS drives
and removing a small SAS drive. After the system attempted to boot from
the hard drive without the system drive connected it never would boot
again. Though the root drive was reconnected it would always hang when
it tried to boot from the hard drive. I finally reloaded the system. I
would like to not have to do that again on this system.

Ted

Are you getting to the grub screen?

Is the boot order the same in the BIOS?

From a live CD show us the output of fdisk -l

gogalthorp wrote:
> From a live CD show us the output of fdisk -l

and the output of:
sudo cat /boot/grub/menu.lst


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio

gogalthorp wrote:
> Are you getting to the grub screen?
>
> Is the boot order the same in the BIOS?
>
> From a live CD show us the output of fdisk -l
>

I get the install DVD boot menu but I never get the grub screen from the
hard drive.

Ted

gogalthorp wrote:
> From a live CD show us the output of fdisk -l

and the output of:
sudo cat /boot/grub/menu.lst

I recommend you provide the above requests…

gogalthorp wrote:
> Are you getting to the grub screen?
>
> Is the boot order the same in the BIOS?
>
> From a live CD show us the output of fdisk -l
>
>
Here is the fdisk -l:

Rescue:~ # fdisk -l

Disk /dev/sda: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003d28f

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap /
Solaris
/dev/sda2 * 263 1568 10490445 83 Linux
/dev/sda3 1569 8924 59087070 83 Linux

Disk /dev/sdb: 300.0 GB, 300000000000 bytes
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000856dc

Device Boot Start End Blocks Id System
/dev/sdb1 1 36472 292961308+ 83 Linux

Disk /dev/sdc: 300.0 GB, 300000000000 bytes
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009c218

Device Boot Start End Blocks Id System
/dev/sdc1 1 36472 292961308+ 83 Linux
Rescue:~ #

DenverD wrote:
> gogalthorp wrote:
>> From a live CD show us the output of fdisk -l
>
> and the output of:
> sudo cat /boot/grub/menu.lst
>

I am having difficulty getting that file because the computer is at a
remote site and the remote console keyboard locked up. It will be
several hours before somebody gets there. What I am not sure is how not
having the cable connected could modify this file? The system was
booting just fine. The cable did not fall out while the machine was
running. I fell out while it was powered off. Then the system was
powered on without the root drive connected. After reconnecting the root
drive it does not want to boot. (Of course that is what the tech person
said but, like all people, sometimes he forgets things.) It seems very
strange to me.

Ted

caf4926 wrote:
>> gogalthorp wrote:
>>> From a live CD show us the output of fdisk -l
>> and the output of:
>> sudo cat /boot/grub/menu.lst
>
> I recommend you provide the above requests…
>
>
I did a little farther down the thread. It was a bit of typing since it
was not possible to copy and paste. :slight_smile:

caf4926 wrote:
>> gogalthorp wrote:
>>> From a live CD show us the output of fdisk -l
>> and the output of:
>> sudo cat /boot/grub/menu.lst
>
> I recommend you provide the above requests…
>
>
I am trying to get the menu.lst but the machine is offline at the moment.

Though I am wondering, since that file is generated by yast, what could
have changed to produce this black screen. I would think that having a
bad menu.lst file grub would at least give some error message. But in
this case there is simply a black screen.

You do not need to be online, just need a live CD.

Until we see that info we can’t say much more.

caf4926 wrote:
> You do not need to be online, just need a live CD.
>
> Until we see that info we can’t say much more.
>
>
I am not sure I understand what is a live CD? And I need the remote KVM
to be online or I can to nothing with that computer. That computer is
sitting in a data center about 9000km from where I am located (and 9
hours difference). So as soon as I get the remote KVM back online I will
be able to access that system.

I did take a linux computer much closer to me (20 cm) and tried to mess
up the menu.lst file to see if I could get the same blank black screen.
So far I cannot. I removed the menu.lst file. Then I received an error
message. I cannot duplicate the black screen. Why do you want to look at
a grub file when grub does not even load? It does not make much sense to me.

Ted Miglautsch wrote:
> I cannot duplicate the black screen. Why do you want to look at
> a grub file when grub does not even load? It does not make much sense to
> me.

you may be right (but maybe not)…after noticing you said in your
first post the machine is “lockup” but later you describe the problem
as “black screen” i think we actually need to know

What is actually going on, exatcly!

to learn that i do not think the DVD is helping at all…

so, i’d suggest you remove the install DVD and make sure to set the
bios to boot from the disk the OS is labeling SDA, and i’d make sure
that disk’s jumper is set to master, and SDB and SDC are set to slave…

then i’d apply power again and see what happens…if we don’t get an
error message we are kinda out of luck…

but i have a question, in your first post you also wrote “We loaded
SUSE Linux on a system” and i wonder which “SUSE Linux” did you load,
exactly?? do you know exactly? if not, the way to learn that is to do
any of these in a terminal:


cat /etc/SuSE-release
lsb_release -sd |cut -f2 -d ""\"
cat /etc/issue

a terminal that you might be able to get to if you boot from the DVD
and at the first green screen type 3, that will appear in the Boot
Options line, then hit enter and at the log in prompt sign in as a
regular user…

hmmmm, you may have to become root to mount SDA, i don’t know if the
DVD will mount it automatically, or not…

btw, a Live CD is a CD which can be downloaded from
software.opensuse.org and from which you can boot directly to a live
KDE or Gnome session (two different versions of the live cd is offered)…

ps: it is entirely possible i can’t actually figure this one out…as
you said “It seems very strange to me.”


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio

I would run fsck on the partition in question from a live disk only thing that makes sense to me.

It looks like the mbr is corrupt why no grub screen but this shouldn’t matter for the boot from hd option that then points to a problem with the second part of grub iirc located at /boot/grub. So in my limited opinion it looks like fs/disk corruption would be the culprit but you mention sas of which I have little knowledge of. I do know sometimes with sata(think might be pata) if the bios is set for auto select it can get confused, so perhaps it is something related to the disk configuration.