Boot-Problem (Suse 9.1, externes RAID)



Hallo allseits,

vorweg: Bin aktuell nicht mehr so der Linux-Spezi und zehre daher eher
von "veraltetem" Wissen.

Konkret folgendes Problem: Ein Bekannter hat in seinem Suse 9.1 Server
ein sterbendes internes RAID (Mylex -- megaraid-Treiber). Drum externes
RAID bestellt (4 primäre Partitionen, /boot --> ext3, Rest XFS) und an
onBoard-Adaptec angeschlossen (aic79xx-Treiber).

Ich konnte remote noch nahezu alle Daten vom internen auf das neue RAID
werfen aber habe jetzt ein Problem, weil das System nicht mehr booten
will. Konkret werden noch die "richtigen" Kernelmodule geladen aber
dann erscheint nur noch eine Meldung von wegen "kjournald started" und
das war's dann. Die letzten Meldungen auf der Konsole:

--------------------------------- >8 ---------------------------------
<4>(scsi2:A:11): 40.000MB/s transfers (40.000MHz)
<5> Type: Direct-Access ANSI SCSI revision: 04
Vendor: easyRAID Model Q12+ Rev: R0.0
<4>scsi2:A:11:0: Tagged Queuing enabled. Depth 32
[...]
SCSI device sda: 2925051904 512-byte hdwr sectors (1497627 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi2, channel 0,id11, lun 0
Loading kernel/fs/xfs/xfs.ko
SGI-XFS CVS-2004-04-28_05:00_UTC with ACLs, security attributes,
realtime, large block numbers, no debug enabled
SGI-XFS CVS-2004-04-28_05:00_UTC with ACLs, security attributes,
realtime, large block numbers, no debug enabled
Loading kernel/fs/jbd/jbd.ko
Loading kernel/fs/ext3/ext3.ko
warning:can't open /etc/mtab: No such file or directory
warning:can't open /etc/mtab: No such file or directory
kjournald starting. Commit interval 5 seconds
--------------------------------- 8< ---------------------------------

Da das interne RAID zwischenzeitlich komplett weggestorben ist, machen
wir jetzt immer den Spaß das System von einer Knoppix-CD zu botten,
dann fummel ich in chroot-Umgebung herum, es wird wieder gestartet und
das System steht wieder. Bin mit meinem Latein am Ende. Vielleicht hat
ja hier wer noch eine Idee oder stupst mich auf meinen Denkfehler?

Nachfolgend das, was ich mal -- mit Knoppix gebootet -- gesammelt habe:

--------------------------------- >8 ---------------------------------
Auditor:/# fdisk /dev/sda
Command (m for help): p

Disk /dev/sda: 1497.6 GB, 1497626574848 bytes
255 heads, 63 sectors/track, 182076 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 263 2008125 82 Linux swap
/dev/sda3 * 264 2754 20008957+ 83 Linux
/dev/sda4 2755 182076 1440403965 83 Linux

Auditor:/# chroot /mnt/easyraid

Auditor:/# mkinitrd -i initrd.knoppix -k vmlinuz-2.6.5-7.111-smp -m
"aic79xx xfs ext3"
Root device: /dev/sda3 (mounted on / as xfs)
Module list: aic79xx xfs ext3

Kernel image: /boot/vmlinuz-2.6.5-7.111-smp
Initrd image: /boot/initrd.knoppix
Shared libs: lib/ld-2.3.3.so lib/libc.so.6 lib/libselinux.so.1
pcilib: Cannot open /sys/bus/pci/devices
Modules: kernel/drivers/scsi/scsi_mod.ko
kernel/drivers/scsi/sd_mod.ko kernel/drivers/scsi/aic7xxx/aic79xx.ko
kernel/fs/xfs/xfs.ko kernel/fs/jbd/jbd.ko kernel/fs/ext3/ext3.ko
Bootsplash: SuSE (640x480)
SuSE (800x600)

Auditor:/# cat /etc/lilo.conf
boot = /dev/sda
vga = 785
read-only
menu-scheme = Wg:kw:Wg:Wg
lba32
prompt
timeout = 80
default = linux
message = /boot/message

image = /boot/vmlinuz
label = linux
root = /dev/sda1
initrd = /boot/initrd.knoppix
append = "vga=0x0311"

image = /boot/vmlinuz
label = linux-alt
root = /dev/rd/c0d0p3
initrd = /boot/initrd
append = "vga=0x0311"

image = /boot/vmlinuz-2.6.14-tk
label = linux-2.6.14-tk
root = /dev/rd/c0d0p3
initrd = /boot/initrd-2.6.14-tk
append = "vga=0x0311"

Auditor:/# lilo -v
LILO version 22.3.4, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2002 John Coffman
Released 01-Nov-2002 and compiled at 18:23:59 on Apr 6 2004.

Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data
Mapping message file /boot/message
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-2.6.5-7.111-smp
Mapping RAM disk /boot/initrd.knoppix
Added linux *

Boot image: /boot/vmlinuz -> vmlinuz-2.6.5-7.111-smp
Mapping RAM disk /boot/initrd -> initrd.knoppix
Added linux-alt

Boot image: /boot/vmlinuz-2.6.14-tk
Mapping RAM disk /boot/initrd-2.6.14-tk
Added linux-2.6.14-tk

/boot/boot.0800 exists - no backup copy made.
Writing boot sector.
--------------------------------- 8< ---------------------------------

Dank' und Gruss,

Thomas

.



Relevant Pages

  • [SLE] SuSE 9.2 stuck in maint mode with trashed FS
    ... I had a drive failure in a raid 5 array. ... Now I can't get SuSE to do anything ... I lost all my logical volumes on the raid filesystem. ... Also in this crippled state won't run lvm command line tool. ...
    (SuSE)
  • [SLE] GRUB/RAID/Root Partition problem
    ... I am running SuSE 9.1 on a dual boot system with XP Home. ... /dev/hda7 35.1GB Linux RAID ... Last night after moving the computer's location, SuSE locked up on load. ... I have around 100GB of data on the RAID partitions that I ...
    (SuSE)
  • Re: [SLE] SUSE 9.0, software RAID, and booting
    ... > I have been running RH for some time now and am now thinking of moving to SUSE. ... Each partition on one disk is mirrored to the ... > Also, on RH, I use GRUB to boot. ... > states that SUSE setup installs LILO by default if the root is on software RAID, ...
    (SuSE)
  • RE: [SLE] hdh is a free 10GB (NTFS) looking for something to do
    ... > Relocating /opt is a good option to free up space on hdb. ... This is documented by SuSE: ... |> Parallel Use of Multiple Disks ... > you may want to look into setting up a RAID array. ...
    (SuSE)
  • Re: [SLE] live CD how-to? REVISITED - re-the Josephine urls
    ... You tell me how a WIKKI should work and I will implement one ... >>HOME directory) which SUSE does not allow for. ... >master fstab and shadow and passwd, but from kernel and mostly, initrd. ... Suse LiveCD works faster that knoppix because ...
    (SuSE)