Bug#814036: initramfs-tools: mdadm doesn't assemble disk

Samuel Thibault sthibault at debian.org
Thu Mar 10 14:57:45 UTC 2016


Samuel Thibault, on Thu 10 Mar 2016 14:45:20 +0100, wrote:
> Dmitry Smirnov, on Mon 29 Feb 2016 18:46:10 +1100, wrote:
> > I tried adding "rootdelay=4" to kernel boot parameters but it did not help.
> 
> I had tried rootdelay=15, it didn't help me either.

Ok, I had to increase that to 45 seconds to get it working
automatically.  Leaving notes here for people with the same problem,
needing a workaround until this gets fixed.

More precisely, here is the boot log with that I get with rootdelay=15
only:

[    5.720053] floppy0: no floppy controllers found
[    5.729329] work still pending

Here it pauses for about 10 seconds more, i.e. up to the rootdelay, then
this:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Warning: starting local-top mdadm
Warning: MD_DEVS is all
Begin: Assembling all MD arrays ... mdadm: No devices listed in conf file were found.
Failure: failed to assemble all arrays.
done.

I.e. it failed to assemble. Then it pauses again for about 15 more seconds.

[   32.775174] scsi0 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16

At last scsi responds...

[   32.828520] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x5000cca00758d704
[   32.848561] scsi 0:0:0:0: Direct-Access     HITACHI  HUS151414VLS300  A48B PQ: 0 ANSI: 5
[   32.869051] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 1, sas_addr 0x5000cca00759b0d4
[   32.889048] scsi 0:0:1:0: Direct-Access     HITACHI  HUS151414VLS300  A48B PQ: 0 ANSI: 5
[   32.909548] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 4, phy 4, sas_addr 0x1221000004000000
[   32.931826] scsi 0:0:2:0: Direct-Access     ATA      Samsung SSD 850  2B6Q PQ: 0 ANSI: 5
[   32.951748] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 5, phy 5, sas_addr 0x1221000005000000
[   32.974070] scsi 0:0:3:0: Direct-Access     ATA      Samsung SSD 850  2B6Q PQ: 0 ANSI: 5
[   33.003539] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   33.014259] sd 0:0:0:0: [sda] 286749480 512-byte logical blocks: (146 GB/136 GiB)
[   33.029511] sd 0:0:1:0: Attached scsi generic sg1 type 0
[   33.040297] sd 0:0:2:0: Attached scsi generic sg2 type 0
[   33.050973] sd 0:0:3:0: [sdd] 2000409264 512-byte logical blocks: (1.02 TB/953 GiB)
[   33.066336] sd 0:0:1:0: [sdb] 286749480 512-byte logical blocks: (146 GB/136 GiB)
[   33.081347] sd 0:0:2:0: [sdc] 2000409264 512-byte logical blocks: (1.02 TB/953 GiB)
[   33.096778] sd 0:0:3:0: Attached scsi generic sg3 type 0
[   33.107452] sd 0:0:0:0: [sda] Write Protect is off
[   33.120484] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA
[   33.137758] sd 0:0:1:0: [sdb] Write Protect is off
[   33.148356] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
[   33.165631] sd 0:0:3:0: [sdd] Write Protect is off
[   33.175250] sd 0:0:2:0: [sdc] Write Protect is off
[   33.185825] sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   33.203960] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   33.229427]  sdd: sdd1
[   33.234218]  sdc: sdc1
[   33.246768] sd 0:0:3:0: [sdd] Attached SCSI disk
[   33.257655] sd 0:0:2:0: [sdc] Attached SCSI disk
[   33.281649]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
[   33.292320]  sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8 sdb9 >
[   33.312635] sd 0:0:0:0: [sda] Attached SCSI disk
[   33.323737] sd 0:0:1:0: [sdb] Attached SCSI disk
[   33.333010] random: nonblocking pool is initialized
[   33.606845] device-mapper: uevent: version 1.0.3
[   33.616518] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel at redhat.com
done.
Begin: Running /[   33.640698] PM: Starting manual resume from disk
scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

etc.

When I set rootdelay to 45, scsi responds at 32s, and assembly is tried
at 45s and can now succeed.

Samuel



More information about the pkg-mdadm-devel mailing list