--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Reboot fails with ROOT on a raid1 partition with a kernel 2.6
- From: Pierre Machard <pierre@machard.org>
- Date: Mon, 11 Oct 2004 16:23:03 +0200
- Message-id: <20041011142303.GA1849@zegal>
Package: installation-reports
Debian-installer-version: PRE RC-2
uname -a: Linux zegal 2.6.8-1-386 #1 Mon Sep 13 23:29:55 EDT 2004 i586 GNU/Linux
Date: 11 oct 2004 ~ 11 H 00 (GMT+2)
Method: expert26
NetInstall
From SCSI CDRW Drive
Local Network without DHCP and without Proxy
Machine: PackardBell MultimediaGL. I changed some hardware on this
box in order to have a new gateway for my personnal usage.
Processor: Pentium 200 MMX
Memory: 48 Mb
Root Device: IDE /dev/md0
Root Size/partition table:
Disk /dev/hda: 4311 MB, 4311982080 bytes
15 heads, 63 sectors/track, 8912 cylinders, total 8421840 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 63 408239 204088+ fd Linux raid autodetect
/dev/hda2 408240 8421839 4006800 f W95 Ext'd (LBA)
/dev/hda5 408303 3568319 1580008+ fd Linux raid autodetect
/dev/hda6 3568383 4931954 681786 83 Linux
/dev/hda7 4932018 5201279 134631 82 Linux swap
/dev/hda8 5201343 5443199 120928+ 83 Linux
/dev/hda9 5443263 8421839 1489288+ 83 Linux
Disk /dev/hdc: 2160 MB, 2160431104 bytes
15 heads, 63 sectors/track, 4465 cylinders, total 4219592 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 63 3161024 1580481 fd Linux raid autodetect
/dev/hdc2 3161025 3525794 182385 fd Linux raid autodetect
/dev/hdc3 3525795 4219424 346815 83 Linux
content of /etc/mdadm/mdadm.conf:
DEVICE partitions
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=7e1d9927:1620cd05:82e23a2f:eb86dbd0
devices=/dev/hda5,/dev/hdc1
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=520029b9:0014b5b3:75abf49a:67bf05f6
devices=/dev/hda1,/dev/hdc2
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/md0 / ext3 defaults,errors=remount-ro 0 1
/dev/hda9 /home ext3 defaults 0 2
/dev/hda8 /tmp ext3 defaults 0 2
/dev/md1 /usr ext3 defaults 0 2
/dev/hda6 /var ext3 defaults 0 2
/dev/hda7 none swap sw 0 0
/dev/scd0 /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
Output of lspci:
0000:00:00.0 Host bridge: Intel Corp. 430VX - 82437VX TVX [Triton VX] (rev 02)
0000:00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
0000:00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]
0000:00:07.2 USB Controller: Intel Corp. 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
0000:00:08.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 54)
0000:00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
0000:00:13.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03)
Output of lspci -n:
0000:00:00.0 0600: 8086:7030 (rev 02)
0000:00:07.0 0601: 8086:7000 (rev 01)
0000:00:07.1 0101: 8086:7010
0000:00:07.2 0c03: 8086:7020 (rev 01)
0000:00:08.0 0300: 5333:8811 (rev 54)
0000:00:11.0 0200: 10ec:8029
0000:00:13.0 0100: 10cd:1300 (rev 03)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [E] Kernel hangs on raid1 root partition[1]
Comments/Problems:
The installation failed with the kernel 2.6.8-1-386 and a raid1 root
partition. The kernel hangs[1] with the default initird. To solve the
problem, I booted on a root backup stored on /dev/hdc3. Then I made
a mkinitrd as it's written in the documentation of mdadm. That is to say:
1) add md and raid1 into /etc/mkinitrd/modules
md
raid1
2) change ROOT on /etc/mkinitrd.conf
ROOT=/dev/md0
3) run mkinitrd -o /boot/initrd.img-2.6.8-raid
4) modify /boot/grub/menu.lst to specify to use the initrd I had
created
[1] :
[...]
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
EISA: Probing bus 0 at eisa0
EISA: Detected 9 cards.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 8
NET: Registered protocol family 20
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4360 blocks [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Unable to handle kernel NULL pointer dereference at virtual address 0000000c
printing eip:
c024b6c8
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0060:[<c024b6c8>] Not tainted
EFLAGS: 00010002 (2.6.8-1-386)
EIP is at __down+0x40/0xef
eax: 00000008 exb: 00000286 ecx: 00000000 edx: c294a000
esi: 00000000 edi: c294be20 ebp: c2fa0b90 esp: c294be0c
ds: 007b es: 007b ss: 0068
Process mount (pid: 194, threadinfo=c294a000 task=c2fa0b90)
Stack: 00000001 c2fa0b90 c01161b1 00000000 00000000 00000001 00000000 00000282
c10555e0 c028d8a0 c2aaf000 0037d926 c024b8a0 00000000 00000a64 02aaf000
c017fa61 c2ba4800 00000000 c10555e0 c29503b8 00000000 c2b9e420 c012df97
Call Trace:
[<c01161b1>] default_wake_function+0x0/0x12
[<c024b8a0>] __down_failed+0x8/0xc
[<c017fa61>] .text.lock.inode+0x7d/0x8c
[<c012df97>] page_cache_read+0x53/0xb7
[<c012e1c3>] filemap_nopage+0x1c8/0x30d
[<c01393f2>] do_no_page+0xa6/0x2cf
[<c013974f>] handle_mm_fault+0x6c/0x125
[<c0114be1>] do_page_fault+0x14d/0x49f
[<c011990c>] profile_hook+0x1c/0x34
[<c0112ac4>] smp_local_timer_interrupt+0xc/0x90
[<c018e852>] copy_from_user+0x2e/0x54
[<c0104a5f>] sys_set_thread_area+0x72/0x1ac
[<c0114a94>] do_page_fault+0x0/0x49f
[<c0106a19>] error_code+0x2d/0x38
Code: 8b 50 04 8d 4c 24 0c 89 48 04 89 44 24 0c 89 54 24 10 89 0a
<6>note: mount[194] exited with preempt_count 1
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---