The 03.02.24 at 21:44, Paul Uiterlinden wrote:
On Monday 24 February 2003 15:11, Carlos E. R. wrote:
Ahh. No, my root partition is plain reiser, and /boot is ext2, both
non raid, on /dev/hdb. I only have an extra 3 Gb partition as raid,
to experiment with :-)
OK, I see. It only adds to the mystery. Why does it still fail? You
suggested in an earlier mail it might be because initrd is not yet
loaded at that point. But I think that's not possible. I mean: the
whole idea of initrd is that you can insert modules even before the
root partition is mounted.
Yes, that's right.
The sequence is this: the kernel loads, initialises a lot of things, like
IDE, checks the partitions, sees some of them are raid, and tries to load
them:
<4>ide-floppy driver 0.99.newide
<6>Partition check:
<6> hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 > hda3 hda4
<6> hdb: hdb1 hdb2 hdb3 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11 hdb12 hdb13 hdb14
<6>Floppy drive(s): fd0 is 1.44M
<6>FDC 0 is a post-1991 82077
<4>RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
<6>loop: loaded (max 16 devices)
<4>ide-floppy driver 0.99.newide
<6>SCSI subsystem driver Revision: 1.00
<3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
<6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
<6>md: Autodetecting RAID arrays.
<6> [events: 00000344]
<6> [events: 00000344]
<6>md: autorun ...
<6>md: considering hdb14 ...
<6>md: adding hdb14 ...
<6>md: adding hda11 ...
<6>md: created md0
<6>md: bind
<6>md: bind
<6>md: running: <hdb14><hda11>
<6>md: hdb14's event counter: 00000344
<6>md: hda11's event counter: 00000344
<6>md: RAID level 1 does not need chunksize! Continuing anyway.
<3>kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
<3>md: personality 3 is not loaded!
<4>md :do_md_run() returned -22
<6>md: md0 stopped.
<6>md: unbind
<6>md: export_rdev(hdb14)
<6>md: unbind
You see, it fails when it tries to run modprobe. It goes on booting:
<6>md: export_rdev(hda11)
<6>md: ... autorun DONE.
<6>NET4: Linux TCP/IP 1.0 for NET4.0
<6>IP Protocols: ICMP, UDP, TCP, IGMP
<6>IP: routing cache hash table of 2048 buckets, 16Kbytes
<6>TCP: Hash tables configured (established 16384 bind 32768)
<6>Linux IP multicast router 0.06 plus PIM-SM
<6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
<5>RAMDISK: Compressed image found at block 0
<6>Freeing initrd memory: 256k freed
<4>VFS: Mounted root (ext2 filesystem).
Now the initrd has been loaded; that filesystem it mounts (ext2) is not my
root, because it is a reiserfs. So it goes on:
<4>scsi: limiting sg entries to 204
<6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
<4> Vendor: IDE Model: DVD-ROM 16X Rev: 1.06
<4> Type: CD-ROM ANSI SCSI revision: 02
<4> Vendor: MITSUMI Model: CR-48X8TE Rev: 1.1E
<4> Type: CD-ROM ANSI SCSI revision: 02
<4>reiserfs: found format "3.6" with standard journal
<4>reiserfs: checking transaction log (ide0(3,70)) for (ide0(3,70))
<4>reiserfs: using ordered data mode
<4>Using r5 hash to sort names
<4>VFS: Mounted root (reiserfs filesystem) readonly.
<5>Trying to move old root to /initrd ... failed
<5>Unmounting old root
<5>Trying to free ramdisk memory ... okay
Now the root filesystem has been really mounted, and the raid is again
considered:
<6>Freeing unused kernel memory: 168k freed
<6>md: Autodetecting RAID arrays.
<6> [events: 00000344]
<6> [events: 00000344]
<6>md: autorun ...
<6>md: considering hda11 ...
<6>md: adding hda11 ...
<6>md: adding hdb14 ...
<6>md: created md0
<6>md: bind
<6>md: bind
<6>md: running: <hda11><hdb14>
<6>md: hda11's event counter: 00000344
<6>md: hdb14's event counter: 00000344
<6>md: RAID level 1 does not need chunksize! Continuing anyway.
<6>md: raid1 personality registered as nr 3
<6>md0: max total readahead window set to 508k
<6>md0: 1 data-disks, max readahead per data-disk: 508k
<6>raid1: device hda11 operational as mirror 0
<6>raid1: device hdb14 operational as mirror 1
<6>raid1: raid set md0 active with 2 out of 2 mirrors
<6>md: updating md0 RAID superblock on device
<6>md: hda11 [events: 00000345]<6>(write) hda11's sb offset: 3124544
<6>md: hdb14 [events: 00000345]<6>(write) hdb14's sb offset: 3124544
<6> [events: 0f227faa]
<3>md: invalid raid superblock magic on md0
<4>md: md0 has invalid sb, not importing!
<4>md: no nested md device found
<6>md: ... autorun DONE.
Now I'm noticing that it says "invalid raid superblock magic on md0". I
don't know what does that mean? Maybe... :-? I think I remember that when
I created the raid array, I could partittion with two types, one for
autodetect, and the other I don't remember. Maybe that's why it tries to
enable so early :-?
/dev/hda11 6242 6630 3124611 fd Linux raid autodetect
I'll have to read carfully the howto.
--
Cheers,
Carlos Robinson