[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#443897: cdrom: Freshly installed system with hardware RAID doesn't boot

Package: cdrom
Severity: critical
Justification: breaks the whole system

I have a server with an onboard Adaptec RAID bus controller (ASR-2010s). 
After the fresh installation of stable Debian 4.0 distribution my system 
was rendered unbootable. It got stucked waiting for the root partition.

The main problem was that grub menu entries were pointing at /dev/sda1
as the root partition, while the Linux kernel didn't know that name. 
Booting message issued by "block-osm" reported registration of i2o/hda 
device, so the root partition was apparentely seen as /dev/i2o/hda1.

Manual editing grub entry has helped to mount the root partition, but 
the system was unable to mount all the other partitions, because all 
fstab entries created by the installer were also following the 
"/dev/sda" schema. Renaming them to the "/dev/i2o/hda" schema fixed this 
problem and my system started to work as expected.

But I faced the problem with grub once again few minutes later, after 
the kernel was upgraded with standard "apt-get dist-upgrade" operation. 
Soon I have discovered that it was most probably caused by "update-grub" 
script. Every time it was activated, both entries in /boot/grub/menu.lst 
file were pointing at root partition /dev/sda1 again. I had to change 
the line:

# kopt=root=/dev/sda1 ro

to look like this:

# kopt=root=/dev/i2o/hda1 ro

This was the right solution. Now my update-grub script does not break 
root partition name in grub entries anymore.

I'm not sure if this is a grub issue or maybe the installer's fault, 
but I don't know how to check it, so I leave it at the CD level.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Reply to: