* Mounting array at boot - works with some kernels but not others
@ 2011-04-03 16:34 Dennis Grant
2011-04-03 17:13 ` Phil Turmel
0 siblings, 1 reply; 10+ messages in thread
From: Dennis Grant @ 2011-04-03 16:34 UTC (permalink / raw)
To: linux-raid
Good afternoon.
I love that these old-school mailing lists are still around. :)
To make a long story short, today I started drilling in to why a
machine I have will boot fine on 2.6.31-22 but not on anything newer
(2.6.32-24 to 2.6.32-30)
This is a Ubuntu machine, and all the kernels are the generic models
provided by Ubuntu.
From what I can tell (and the Ubuntu splash screens and various other
shenanigans tend to make troubleshooting more challenging than
required) the boot sequence is failing to mount the raid partition on
the newer kernels. That drops the boot to a console where one is
provided the options to keep waiting, (S)kip the mount, or (M)anually
recover (which drops to a shell). Skipping will boot the machine, but
with the array unmounted.
So something is different about how Ubuntu or the kernel is handling
the raid array between the 2.6.31-22 and all the newer kernels.
When I boot from the 31-22 kernel, the array does appear to be functional.
Machine has 3 drives: sda and sdb are identical and contain the array.
sdc is an older HD from an earlier machine that has LVM partitions on
it.
Attached is a bunch of diagnostic material. Unfortunately, I don't
have the error messages from failed boot attempts.
Any assistance would be much appreciated. I'd be happy to work
off-list and post a summary of the resolution if that helps keep the
list from being clogged up.
Thanks,
DG
---------------------------------
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md1 : active raid1 sda5[0] sdb5[1]
769706176 blocks [2/2] [UU]
cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 207872 sda1
8 2 204796620 sda2
8 3 2048287 sda3
8 4 1 sda4
8 5 769706248 sda5
8 16 976762584 sdb
8 17 208813 sdb1
8 18 204796620 sdb2
8 19 2048287 sdb3
8 20 1 sdb4
8 21 769706248 sdb5
8 32 245117376 sdc
8 33 104391 sdc1
8 34 245007315 sdc2
9 1 769706176 md1
252 0 10223616 dm-0
252 1 153812992 dm-1
252 2 76775424 dm-2
252 3 1015808 dm-3
252 4 3145728 dm-4
sudo mdadm --detail /dev/md1
/dev/md1:
Version : 00.90
Creation Time : Sat Apr 25 08:43:26 2009
Raid Level : raid1
Array Size : 769706176 (734.05 GiB 788.18 GB)
Used Dev Size : 769706176 (734.05 GiB 788.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sun Apr 3 12:06:23 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : e0cc58c7:6f841366:7a44a462:94a1d56a (local to host karzai)
Events : 0.2844822
Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
1 8 21 1 active sync /dev/sdb5
sudo mdadm --examine /dev/md1
mdadm: No md superblock detected on /dev/md1.
sudo fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ac88c
Device Boot Start End Blocks Id System
/dev/sda1 * 1 26 207872 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 27 25522 204796620 83 Linux
/dev/sda3 25523 25777 2048287+ 82 Linux swap / Solaris
/dev/sda4 25778 121601 769706280 5 Extended
/dev/sda5 25778 121601 769706248+ 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d90a1
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 26 208813+ 83 Linux
/dev/sdb2 27 25522 204796620 83 Linux
/dev/sdb3 25523 25777 2048287+ 82 Linux swap / Solaris
/dev/sdb4 25778 121601 769706280 5 Extended
/dev/sdb5 25778 121601 769706248+ 83 Linux
Disk /dev/sdc: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00042b0a
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 104391 83 Linux
/dev/sdc2 14 30515 245007315 8e Linux LVM
Disk /dev/md1: 788.2 GB, 788179124224 bytes
2 heads, 4 sectors/track, 192426544 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda2 during installation
UUID=0bffc411-e143-4d25-bc59-b8b9fabb788a / ext3
relatime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=b8f4b4ab-2e59-426e-b380-791f36ba473c /boot ext2
relatime 0 2
# /boot2 was on /dev/sdb1 during installation
UUID=e9768910-bfd5-4e04-a244-db4a2da9b215 /boot2 ext2
relatime 0 2
# /home was on /dev/sda5 during installation
#UUID=4f73e3ae-9e5d-432f-b5e4-f7c75a038c7c /home ext3
relatime 0 2
# /home installed on mdraid device by DG. Consists of /home and
/homebak partitions (/dev/sda5 and /dev/sdb5)
/dev/md1 /home ext3 relatime 0 2
# /homeback was on /dev/sdb5 during installation
#UUID=c3c02f6c-1321-4882-90c5-2623033261c5 /homeback ext3
relatime 0 2
# /sysback was on /dev/sdb2 during installation
UUID=9f3bb9ee-ee5e-48a8-bdbe-9c80561f41d0 /sysback ext3
relatime 0 2
# swap was on /dev/sda3 during installation
UUID=873b1a20-cb72-4675-9cc7-fe6ac857490d none swap sw
0 0
# swap was on /dev/sdb3 during installation
UUID=47842e22-d4be-4738-ba2a-b13332b752e9 none swap sw
0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/VolGroupHDB/LogVol00 /oldhd/root ext3 defaults 1 2
/dev/VolGroupHDB/LogVol04 /oldhd/home ext3 defaults 1 2
/dev/VolGroupHDB/LogVol02 /oldhd/root/usr/local ext3 defaults 1 2
/dev/VolGroupHDB/LogVol03 /oldhd/root/var ext3 defaults 1 2
sudo vgdisplay
--- Volume group ---
VG Name VolGroupHDB
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 5
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 233.66 GiB
PE Size 32.00 MiB
Total PE 7477
Alloc PE / Size 7476 / 233.62 GiB
Free PE / Size 1 / 32.00 MiB
VG UUID 2tI8oM-GfB9-OHgv-jQAc-D9bH-zRBK-f3dBAs
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 16:34 Mounting array at boot - works with some kernels but not others Dennis Grant
@ 2011-04-03 17:13 ` Phil Turmel
2011-04-03 17:26 ` Dennis Grant
0 siblings, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2011-04-03 17:13 UTC (permalink / raw)
To: Dennis Grant; +Cc: linux-raid
Hi Dennis,
On 04/03/2011 12:34 PM, Dennis Grant wrote:
> Good afternoon.
>
> I love that these old-school mailing lists are still around. :)
>
> To make a long story short, today I started drilling in to why a
> machine I have will boot fine on 2.6.31-22 but not on anything newer
> (2.6.32-24 to 2.6.32-30)
>
> This is a Ubuntu machine, and all the kernels are the generic models
> provided by Ubuntu.
>
> From what I can tell (and the Ubuntu splash screens and various other
> shenanigans tend to make troubleshooting more challenging than
> required) the boot sequence is failing to mount the raid partition on
> the newer kernels. That drops the boot to a console where one is
> provided the options to keep waiting, (S)kip the mount, or (M)anually
> recover (which drops to a shell). Skipping will boot the machine, but
> with the array unmounted.
>
> So something is different about how Ubuntu or the kernel is handling
> the raid array between the 2.6.31-22 and all the newer kernels.
>
> When I boot from the 31-22 kernel, the array does appear to be functional.
>
> Machine has 3 drives: sda and sdb are identical and contain the array.
> sdc is an older HD from an earlier machine that has LVM partitions on
> it.
>
> Attached is a bunch of diagnostic material. Unfortunately, I don't
> have the error messages from failed boot attempts.
>
> Any assistance would be much appreciated. I'd be happy to work
> off-list and post a summary of the resolution if that helps keep the
> list from being clogged up.
On-list is fine. A couple of clarifications below:
>
> Thanks,
>
> DG
>
> ---------------------------------
> cat /proc/mdstat
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
> [raid4] [raid10]
> md1 : active raid1 sda5[0] sdb5[1]
> 769706176 blocks [2/2] [UU]
>
> cat /proc/partitions
> major minor #blocks name
>
> 8 0 976762584 sda
> 8 1 207872 sda1
> 8 2 204796620 sda2
> 8 3 2048287 sda3
> 8 4 1 sda4
> 8 5 769706248 sda5
> 8 16 976762584 sdb
> 8 17 208813 sdb1
> 8 18 204796620 sdb2
> 8 19 2048287 sdb3
> 8 20 1 sdb4
> 8 21 769706248 sdb5
> 8 32 245117376 sdc
> 8 33 104391 sdc1
> 8 34 245007315 sdc2
> 9 1 769706176 md1
> 252 0 10223616 dm-0
> 252 1 153812992 dm-1
> 252 2 76775424 dm-2
> 252 3 1015808 dm-3
> 252 4 3145728 dm-4
>
> sudo mdadm --detail /dev/md1
> /dev/md1:
> Version : 00.90
> Creation Time : Sat Apr 25 08:43:26 2009
> Raid Level : raid1
> Array Size : 769706176 (734.05 GiB 788.18 GB)
> Used Dev Size : 769706176 (734.05 GiB 788.18 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 1
> Persistence : Superblock is persistent
>
> Update Time : Sun Apr 3 12:06:23 2011
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> UUID : e0cc58c7:6f841366:7a44a462:94a1d56a (local to host karzai)
> Events : 0.2844822
>
> Number Major Minor RaidDevice State
> 0 8 5 0 active sync /dev/sda5
> 1 8 21 1 active sync /dev/sdb5
>
> sudo mdadm --examine /dev/md1
> mdadm: No md superblock detected on /dev/md1.
Please do "mdadm --examine" on the component devices /dev/sda5 and /dev/sdb5.
> sudo fdisk -l
>
> Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000ac88c
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 26 207872 83 Linux
> Partition 1 does not end on cylinder boundary.
> /dev/sda2 27 25522 204796620 83 Linux
> /dev/sda3 25523 25777 2048287+ 82 Linux swap / Solaris
> /dev/sda4 25778 121601 769706280 5 Extended
> /dev/sda5 25778 121601 769706248+ 83 Linux
>
> Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000d90a1
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 26 208813+ 83 Linux
> /dev/sdb2 27 25522 204796620 83 Linux
> /dev/sdb3 25523 25777 2048287+ 82 Linux swap / Solaris
> /dev/sdb4 25778 121601 769706280 5 Extended
> /dev/sdb5 25778 121601 769706248+ 83 Linux
>
> Disk /dev/sdc: 251.0 GB, 251000193024 bytes
> 255 heads, 63 sectors/track, 30515 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00042b0a
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 * 1 13 104391 83 Linux
> /dev/sdc2 14 30515 245007315 8e Linux LVM
>
> Disk /dev/md1: 788.2 GB, 788179124224 bytes
> 2 heads, 4 sectors/track, 192426544 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md1 doesn't contain a valid partition table
>
> cat /etc/fstab
> # /etc/fstab: static file system information.
> #
> # Use 'vol_id --uuid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> # / was on /dev/sda2 during installation
> UUID=0bffc411-e143-4d25-bc59-b8b9fabb788a / ext3
> relatime,errors=remount-ro 0 1
> # /boot was on /dev/sda1 during installation
> UUID=b8f4b4ab-2e59-426e-b380-791f36ba473c /boot ext2
> relatime 0 2
> # /boot2 was on /dev/sdb1 during installation
> UUID=e9768910-bfd5-4e04-a244-db4a2da9b215 /boot2 ext2
> relatime 0 2
> # /home was on /dev/sda5 during installation
> #UUID=4f73e3ae-9e5d-432f-b5e4-f7c75a038c7c /home ext3
> relatime 0 2
> # /home installed on mdraid device by DG. Consists of /home and
> /homebak partitions (/dev/sda5 and /dev/sdb5)
> /dev/md1 /home ext3 relatime 0 2
> # /homeback was on /dev/sdb5 during installation
> #UUID=c3c02f6c-1321-4882-90c5-2623033261c5 /homeback ext3
> relatime 0 2
> # /sysback was on /dev/sdb2 during installation
> UUID=9f3bb9ee-ee5e-48a8-bdbe-9c80561f41d0 /sysback ext3
> relatime 0 2
> # swap was on /dev/sda3 during installation
> UUID=873b1a20-cb72-4675-9cc7-fe6ac857490d none swap sw
> 0 0
> # swap was on /dev/sdb3 during installation
> UUID=47842e22-d4be-4738-ba2a-b13332b752e9 none swap sw
> 0 0
> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
> /dev/VolGroupHDB/LogVol00 /oldhd/root ext3 defaults 1 2
> /dev/VolGroupHDB/LogVol04 /oldhd/home ext3 defaults 1 2
> /dev/VolGroupHDB/LogVol02 /oldhd/root/usr/local ext3 defaults 1 2
> /dev/VolGroupHDB/LogVol03 /oldhd/root/var ext3 defaults 1 2
>
Please also share the output of "blkid" so we can interpret this fstab.
> sudo vgdisplay
> --- Volume group ---
> VG Name VolGroupHDB
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 8
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 5
> Open LV 4
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 233.66 GiB
> PE Size 32.00 MiB
> Total PE 7477
> Alloc PE / Size 7476 / 233.62 GiB
> Free PE / Size 1 / 32.00 MiB
> VG UUID 2tI8oM-GfB9-OHgv-jQAc-D9bH-zRBK-f3dBAs
I suspect that the new kernels are noticing your version 0.90 metadata and trying to be conservative. 0.90 metadata can be ambiguous when on the last partition of a disk (same location and content as if for the whole disk).
You can remove the ambiguity by declaring in mdadm.conf that devices to inspect must be partitions, like so:
DEVICE /dev/sd*[0-9]
Or call them out explicitly:
DEVICE /dev/sda5 /dev/sdb5
Rebuild your initramfs to include these changes in your boot environment.
HTH,
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 17:13 ` Phil Turmel
@ 2011-04-03 17:26 ` Dennis Grant
2011-04-03 17:29 ` Phil Turmel
2011-04-03 17:41 ` Phil Turmel
0 siblings, 2 replies; 10+ messages in thread
From: Dennis Grant @ 2011-04-03 17:26 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
On Sun, Apr 3, 2011 at 1:13 PM, Phil Turmel <philip@turmel.org> wrote:
> On-list is fine. A couple of clarifications below:
> Please do "mdadm --examine" on the component devices /dev/sda5 and /dev/sdb5.
As requested:
sudo mdadm --examine /dev/sda
mdadm: No md superblock detected on /dev/sda.
sudo mdadm --examine /dev/sdb
mdadm: No md superblock detected on /dev/sdb.
> Please also share the output of "blkid" so we can interpret this fstab.
sudo blkid
/dev/sda1: UUID="b8f4b4ab-2e59-426e-b380-791f36ba473c" TYPE="ext2"
/dev/sda2: UUID="0bffc411-e143-4d25-bc59-b8b9fabb788a" TYPE="ext3"
/dev/sda3: LABEL="SWAP-sda3"
UUID="873b1a20-cb72-4675-9cc7-fe6ac857490d" TYPE="swap"
/dev/sda5: UUID="e0cc58c7-6f84-1366-7a44-a46294a1d56a" TYPE="linux_raid_member"
/dev/sdb1: UUID="e9768910-bfd5-4e04-a244-db4a2da9b215" TYPE="ext2"
/dev/sdb2: UUID="9f3bb9ee-ee5e-48a8-bdbe-9c80561f41d0" TYPE="ext3"
/dev/sdb3: LABEL="SWAP-sdb3"
UUID="47842e22-d4be-4738-ba2a-b13332b752e9" TYPE="swap"
/dev/sdb5: UUID="e0cc58c7-6f84-1366-7a44-a46294a1d56a" TYPE="linux_raid_member"
/dev/sdc1: LABEL="/boot1" UUID="d0f1b0b3-81d7-416b-930d-8fc3c246302a"
TYPE="ext3"
/dev/sdc2: UUID="qJ01LE-w3nn-yV23-GFa6-mc0n-01tn-qLI4mv" TYPE="LVM2_member"
/dev/md1: UUID="cdd97ad2-e070-477b-b649-83921f70b9cf" TYPE="ext3"
/dev/mapper/VolGroupHDB-LogVol00:
UUID="eae940e9-e625-4769-b4ff-8929fdd73558" TYPE="ext3"
/dev/mapper/VolGroupHDB-LogVol04:
UUID="3b141c7e-b850-4659-a876-52c8bc592878" TYPE="ext3"
/dev/mapper/VolGroupHDB-LogVol02:
UUID="5cc5ecf4-0b15-410c-b8a6-7712ed35af83" TYPE="ext3"
/dev/mapper/VolGroupHDB-LogVol03:
UUID="787eb25b-537f-4b9a-8871-95a6118224c7" TYPE="ext3"
/dev/mapper/VolGroupHDB-LogVol01: TYPE="swap"
> I suspect that the new kernels are noticing your version 0.90 metadata and trying to be conservative. 0.90 metadata can be ambiguous when on the last partition of a disk (same location and content as if for the whole disk).
> You can remove the ambiguity by declaring in mdadm.conf that devices to inspect must be partitions, like so:
>
> DEVICE /dev/sd*[0-9]
>
> Or call them out explicitly:
>
> DEVICE /dev/sda5 /dev/sdb5
Here's the current version:
cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE /dev/sda5 /dev/sdb5
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md1 devices=/dev/sda5,/dev/sdb5
-------------------------
So it looks like they are already called out.
The lack of superblocks is - that maybe the issue? Can those be
created/restored without trashing the FS?
DG
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 17:26 ` Dennis Grant
@ 2011-04-03 17:29 ` Phil Turmel
2011-04-03 17:32 ` Dennis Grant
2011-04-03 17:41 ` Phil Turmel
1 sibling, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2011-04-03 17:29 UTC (permalink / raw)
To: Dennis Grant; +Cc: linux-raid
On 04/03/2011 01:26 PM, Dennis Grant wrote:
> On Sun, Apr 3, 2011 at 1:13 PM, Phil Turmel <philip@turmel.org> wrote:
>
>> On-list is fine. A couple of clarifications below:
>
>> Please do "mdadm --examine" on the component devices /dev/sda5 and /dev/sdb5.
>
> As requested:
>
> sudo mdadm --examine /dev/sda
> mdadm: No md superblock detected on /dev/sda.
>
> sudo mdadm --examine /dev/sdb
> mdadm: No md superblock detected on /dev/sdb.
Retry:
mdadm --examine /dev/sda5
mdadm --examine /dev/sdb5
------------------------^
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 17:29 ` Phil Turmel
@ 2011-04-03 17:32 ` Dennis Grant
0 siblings, 0 replies; 10+ messages in thread
From: Dennis Grant @ 2011-04-03 17:32 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
> Retry:
Ah, I'm an idiot:
sudo mdadm --examine /dev/sda5
/dev/sda5:
Magic : a92b4efc
Version : 00.90.00
UUID : e0cc58c7:6f841366:7a44a462:94a1d56a (local to host karzai)
Creation Time : Sat Apr 25 08:43:26 2009
Raid Level : raid1
Used Dev Size : 769706176 (734.05 GiB 788.18 GB)
Array Size : 769706176 (734.05 GiB 788.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Update Time : Sun Apr 3 13:31:15 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ce2583e5 - correct
Events : 2844822
Number Major Minor RaidDevice State
this 0 8 5 0 active sync /dev/sda5
0 0 8 5 0 active sync /dev/sda5
1 1 8 21 1 active sync /dev/sdb5
sudo mdadm --examine /dev/sdb5
/dev/sdb5:
Magic : a92b4efc
Version : 00.90.00
UUID : e0cc58c7:6f841366:7a44a462:94a1d56a (local to host karzai)
Creation Time : Sat Apr 25 08:43:26 2009
Raid Level : raid1
Used Dev Size : 769706176 (734.05 GiB 788.18 GB)
Array Size : 769706176 (734.05 GiB 788.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Update Time : Sun Apr 3 13:31:15 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : ce2583f7 - correct
Events : 2844822
Number Major Minor RaidDevice State
this 1 8 21 1 active sync /dev/sdb5
0 0 8 5 0 active sync /dev/sda5
1 1 8 21 1 active sync /dev/sdb5
DG
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 17:26 ` Dennis Grant
2011-04-03 17:29 ` Phil Turmel
@ 2011-04-03 17:41 ` Phil Turmel
2011-04-03 19:48 ` Dennis Grant
1 sibling, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2011-04-03 17:41 UTC (permalink / raw)
To: Dennis Grant; +Cc: linux-raid
On 04/03/2011 01:26 PM, Dennis Grant wrote:
> On Sun, Apr 3, 2011 at 1:13 PM, Phil Turmel <philip@turmel.org> wrote:
>
>> On-list is fine. A couple of clarifications below:
>
>> Please do "mdadm --examine" on the component devices /dev/sda5 and /dev/sdb5.
>
> As requested:
>
> sudo mdadm --examine /dev/sda
> mdadm: No md superblock detected on /dev/sda.
>
> sudo mdadm --examine /dev/sdb
> mdadm: No md superblock detected on /dev/sdb.
>
Hmmm. This means that the metadata location is *not* ambiguous, or it would show for the examine of both the whole device and the partition. So much for that idea.
>> Please also share the output of "blkid" so we can interpret this fstab.
>
> sudo blkid
[snip /]
> /dev/md1: UUID="cdd97ad2-e070-477b-b649-83921f70b9cf" TYPE="ext3"
This is what I wanted, but I'm a dunce. You called out /dev/md1 directly in the fstab. Sorry.
>> I suspect that the new kernels are noticing your version 0.90 metadata and trying to be conservative. 0.90 metadata can be ambiguous when on the last partition of a disk (same location and content as if for the whole disk).
>
>> You can remove the ambiguity by declaring in mdadm.conf that devices to inspect must be partitions, like so:
>>
>> DEVICE /dev/sd*[0-9]
>>
>> Or call them out explicitly:
>>
>> DEVICE /dev/sda5 /dev/sdb5
>
> Here's the current version:
>
> cat /etc/mdadm/mdadm.conf
> # mdadm.conf
> #
> # Please refer to mdadm.conf(5) for information about this file.
> #
>
> # by default, scan all partitions (/proc/partitions) for MD superblocks.
> # alternatively, specify devices to scan, using wildcards if desired.
> DEVICE /dev/sda5 /dev/sdb5
>
> # auto-create devices with Debian standard permissions
> CREATE owner=root group=disk mode=0660 auto=yes
>
> # automatically tag new arrays as belonging to the local system
> HOMEHOST <system>
>
> # instruct the monitoring daemon where to send mail alerts
> MAILADDR root
>
> # definitions of existing MD arrays
> ARRAY /dev/md1 devices=/dev/sda5,/dev/sdb5
>
> -------------------------
> So it looks like they are already called out.
Yup. Blind alley.
You mentioned that the system will boot with a newer kernel, just without the array. Could you boot it like that, but select single-user mode? Then you can save the dmesg to a file, collect any other useful messages, reboot into 2.6.31, then paste the files into an email.
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 17:41 ` Phil Turmel
@ 2011-04-03 19:48 ` Dennis Grant
2011-04-03 20:09 ` Phil Turmel
0 siblings, 1 reply; 10+ messages in thread
From: Dennis Grant @ 2011-04-03 19:48 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
> You mentioned that the system will boot with a newer kernel, just without the array. Could you boot it like that, but select single-user mode? Then you can save the dmesg to a file, collect any other useful messages, reboot into 2.6.31, then paste the files into an email.
Here goes - dmesg heavily redacted:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-30-generic (buildd@vernadsky) (gcc
version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #59-Ubuntu SMP Tue Mar 1
21:30:21 UTC 2011 (Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13)
[ 0.923535] ahci 0000:00:11.0: version 3.0
[ 0.923554] alloc irq_desc for 22 on node -1
[ 0.923555] alloc kstat_irqs on node -1
[ 0.923564] ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 0.923721] ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3
Gbps 0x3f impl SATA mode
[ 0.923758] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led
clo pmp pio slum part ccc
[ 0.929507] scsi0 : ahci
[ 0.936083] scsi1 : ahci
[ 0.943752] scsi2 : ahci
[ 0.945123] scsi3 : ahci
[ 0.945851] scsi4 : ahci
[ 0.947687] scsi5 : ahci
[ 0.947834] ata1: SATA max UDMA/133 irq_stat 0x00400000, PHY RDY
changed irq 22
[ 0.947871] ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port
0xfe02f180 irq 22
[ 0.947907] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port
0xfe02f200 irq 22
[ 0.947944] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port
0xfe02f280 irq 22
[ 0.947980] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port
0xfe02f300 irq 22
[ 0.948017] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port
0xfe02f380 irq 22
[ 0.948339] scsi6 : pata_atiixp
[ 0.948414] scsi7 : pata_atiixp
[ 0.949196] ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
[ 0.949234] ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
[ 1.084835] ata7.00: ATAPI: SONY DVD RW DRU-810A, 1.0e, max UDMA/33
[ 1.101607] ata7.01: HPA unlocked: 490232639 -> 490234752, native 490234752
[ 1.101644] ata7.01: ATA-7: Maxtor 6B250R0, BAH41BY0, max UDMA/133
[ 1.101677] ata7.01: 490234752 sectors, multi 16: LBA48
[ 1.116811] ata7.00: configured for UDMA/33
[ 1.134253] ata7.01: configured for UDMA/100
[ 1.228176] ata3: SATA link down (SStatus 0 SControl 300)
[ 1.233152] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.233210] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.233659] ata6: SATA link down (SStatus 0 SControl 300)
[ 1.341157] scsi8 : SCSI emulation for USB Mass Storage devices
[ 1.393662] ata2: softreset failed (device not ready)
[ 1.393697] ata2: applying SB600 PMP SRST workaround and retrying
[ 1.556196] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.557471] ata2.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
[ 1.557506] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 1.559065] ata2.00: configured for UDMA/133
[ 1.808688] ata1: applying SB600 PMP SRST workaround and retrying
[ 1.972145] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.973383] ata1.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
[ 1.973418] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 1.974956] ata1.00: configured for UDMA/133
[ 1.988276] scsi 0:0:0:0: Direct-Access ATA WDC
WD1001FALS-0 05.0 PQ: 0 ANSI: 5
[ 1.988439] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.988467] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks:
(1.00 TB/931 GiB)
[ 1.988491] sd 0:0:0:0: [sda] Write Protect is off
[ 1.988493] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.988505] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.988593] sda:
[ 1.988691] scsi 1:0:0:0: Direct-Access ATA WDC
WD1001FALS-0 05.0 PQ: 0 ANSI: 5
[ 1.988885] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 1.988888] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks:
(1.00 TB/931 GiB)
[ 1.988943] sd 1:0:0:0: [sdb] Write Protect is off
[ 1.988945] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.988970] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.989163] sdb:
[ 1.991478] scsi 6:0:0:0: CD-ROM SONY DVD RW
DRU-810A 1.0e PQ: 0 ANSI: 5
[ 1.996140] CE: hpet increasing min_delta_ns to 15000 nsec
[ 2.001025] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[ 2.001059] Uniform CD-ROM driver Revision: 3.20
[ 2.001160] sr 6:0:0:0: Attached scsi CD-ROM sr0
[ 2.001199] sr 6:0:0:0: Attached scsi generic sg2 type 5
[ 2.001308] scsi 6:0:1:0: Direct-Access ATA Maxtor 6B250R0
BAH4 PQ: 0 ANSI: 5
[ 2.001430] sd 6:0:1:0: [sdc] 490234752 512-byte logical blocks:
(251 GB/233 GiB)
[ 2.001448] sd 6:0:1:0: Attached scsi generic sg3 type 0
[ 2.001542] sdb1
[ 2.001553] sd 6:0:1:0: [sdc] Write Protect is off
[ 2.001554] sd 6:0:1:0: [sdc] Mode Sense: 00 3a 00 00
[ 2.001578] sd 6:0:1:0: [sdc] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 2.001686] sdb2 sdb3 sdb4 <
[ 2.001901] sdc: sda1 sda2 sda3 sda4 < sdb5 >
[ 2.019924] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 2.020510] sda5 >
[ 2.022265] sdc1 sdc2
[ 2.022532] sd 6:0:1:0: [sdc] Attached SCSI disk
[ 2.027189] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.045157] usb 3-2: new low speed USB device using ohci_hcd and address 3
[ 2.157952] device-mapper: dm-raid45: initialized v0.2594b
[ 2.159783] ohci1394 0000:03:0e.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 2.162472] md: linear personality registered for level -1
[ 2.164145] md: multipath personality registered for level -4
[ 2.166061] md: raid0 personality registered for level 0
[ 2.168346] md: raid1 personality registered for level 1
[ 2.236543] raid6: int32x1 1304 MB/s
[ 2.304530] raid6: int32x2 1410 MB/s
[ 2.372522] raid6: int32x4 964 MB/s
[ 2.440508] raid6: int32x8 681 MB/s
[ 2.508515] raid6: mmxx1 2475 MB/s
[ 2.576505] raid6: mmxx2 4750 MB/s
[ 2.644505] raid6: sse1x1 2030 MB/s
[ 2.712514] raid6: sse1x2 3453 MB/s
[ 2.780520] raid6: sse2x1 3800 MB/s
[ 2.848505] raid6: sse2x2 6223 MB/s
[ 2.848536] raid6: using algorithm sse2x2 (6223 MB/s)
[ 2.852248] md: raid6 personality registered for level 6
[ 2.852282] md: raid5 personality registered for level 5
[ 2.852314] md: raid4 personality registered for level 4
[ 2.856787] md: raid10 personality registered for level 10
[ 2.949118] md: bind<sda5>
[ 2.984447] md: bind<sdb5>
[ 2.986309] raid1: raid set md1 active with 2 out of 2 mirrors
[ 2.986361] md1: detected capacity change from 0 to 788179124224
[ 2.987205] md1: unknown partition table
[ 3.199341] kjournald starting. Commit interval 5 seconds
[ 3.199356] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.671452] scsi 8:0:0:0: Direct-Access Generic USB SD Reader
1.00 PQ: 0 ANSI: 0
[ 29.672325] scsi 8:0:0:1: Direct-Access Generic USB CF Reader
1.01 PQ: 0 ANSI: 0
[ 29.673158] scsi 8:0:0:2: Direct-Access Generic USB xD/SM
Reader 1.02 PQ: 0 ANSI: 0
[ 29.674004] scsi 8:0:0:3: Direct-Access Generic USB MS Reader
1.03 PQ: 0 ANSI: 0
[ 29.674326] sd 8:0:0:0: Attached scsi generic sg4 type 0
[ 29.674432] sd 8:0:0:1: Attached scsi generic sg5 type 0
[ 29.674536] sd 8:0:0:2: Attached scsi generic sg6 type 0
[ 29.674640] sd 8:0:0:3: Attached scsi generic sg7 type 0
[ 29.681659] sd 8:0:0:0: [sdd] Attached SCSI removable disk
[ 29.682292] sd 8:0:0:1: [sde] Attached SCSI removable disk
[ 29.683561] sd 8:0:0:2: [sdf] Attached SCSI removable disk
[ 29.684168] sd 8:0:0:3: [sdg] Attached SCSI removable disk
[ 29.800664] Adding 2048276k swap on /dev/sda3. Priority:-1
extents:1 across:2048276k
[ 29.909600] Adding 2048276k swap on /dev/sdb3. Priority:-2
extents:1 across:2048276k
[ 30.022862] udev: starting version 151
[ 31.253036] shpchp 0000:00:01.0: HPC vendor_id 1022 device_id 9602
ss_vid 0 ss_did 0
[ 31.253040] shpchp 0000:00:01.0: Cannot reserve MMIO region
[ 31.253095] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 31.375816] ACPI: resource piix4_smbus [0xb00-0xb07] conflicts with
ACPI region SOR1 [0xb00-0xb0f]
[ 31.375819] ACPI: If an ACPI driver is available for this device,
you should use it instead of the native driver
[ 40.205687] type=1505 audit(1301858645.806:2):
operation="profile_load" pid=687 name="/sbin/dhclient3"
[ 40.205698] type=1505 audit(1301858645.806:3):
operation="profile_replace" pid=680 name="/sbin/dhclient3"
[ 40.205884] type=1505 audit(1301858645.806:4):
operation="profile_load" pid=687
name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 40.205902] type=1505 audit(1301858645.806:5):
operation="profile_replace" pid=680
name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 40.205995] type=1505 audit(1301858645.806:6):
operation="profile_load" pid=687
name="/usr/lib/connman/scripts/dhclient-script"
[ 40.206020] type=1505 audit(1301858645.806:7):
operation="profile_replace" pid=680
name="/usr/lib/connman/scripts/dhclient-script"
[ 44.951085] type=1505 audit(1301858650.549:8):
operation="profile_load" pid=967 name="/usr/sbin/ntpd"
[ 44.951096] type=1505 audit(1301858650.549:9):
operation="profile_replace" pid=966 name="/usr/sbin/ntpd"
[ 54.291501] EXT3 FS on sda2, internal journal
[ 54.635654] kjournald starting. Commit interval 5 seconds
[ 54.636035] EXT3 FS on sdb2, internal journal
[ 54.636039] EXT3-fs: mounted filesystem with ordered data mode.
[ 54.720501] kjournald starting. Commit interval 5 seconds
[ 54.720663] EXT3 FS on dm-0, internal journal
[ 54.720667] EXT3-fs: mounted filesystem with ordered data mode.
[ 55.437462] kjournald starting. Commit interval 5 seconds
[ 55.437913] EXT3 FS on dm-1, internal journal
[ 55.437917] EXT3-fs: mounted filesystem with ordered data mode.
[ 55.522745] kjournald starting. Commit interval 5 seconds
[ 55.523174] EXT3 FS on dm-2, internal journal
[ 55.523177] EXT3-fs: mounted filesystem with ordered data mode.
[ 55.585619] kjournald starting. Commit interval 5 seconds
[ 55.628189] EXT3 FS on md1, internal journal
[ 55.628193] EXT3-fs: mounted filesystem with ordered data mode.
[ 56.931225] kjournald starting. Commit interval 5 seconds
[ 56.931562] EXT3 FS on dm-3, internal journal
[ 56.931566] EXT3-fs: mounted filesystem with ordered data mode.
[ 65.876933] type=1505 audit(1301858671.474:10):
operation="profile_replace" pid=1164 name="/sbin/dhclient3"
[ 65.877143] type=1505 audit(1301858671.478:11):
operation="profile_replace" pid=1164
name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[ 65.877257] type=1505 audit(1301858671.478:12):
operation="profile_replace" pid=1164
name="/usr/lib/connman/scripts/dhclient-script"
At the end of the 3 second mark lines, the system stops booting and
needs a series of console inputs (space bar or return) to continue
booting. Each input advances the process a little bit.
/var/log/messages offered nothing different.
DG
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 19:48 ` Dennis Grant
@ 2011-04-03 20:09 ` Phil Turmel
2011-04-03 20:17 ` Dennis Grant
0 siblings, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2011-04-03 20:09 UTC (permalink / raw)
To: Dennis Grant; +Cc: linux-raid
On 04/03/2011 03:48 PM, Dennis Grant wrote:
>> You mentioned that the system will boot with a newer kernel, just without the array. Could you boot it like that, but select single-user mode? Then you can save the dmesg to a file, collect any other useful messages, reboot into 2.6.31, then paste the files into an email.
Interesting...
>
> Here goes - dmesg heavily redacted:
>
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Linux version 2.6.32-30-generic (buildd@vernadsky) (gcc
> version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #59-Ubuntu SMP Tue Mar 1
> 21:30:21 UTC 2011 (Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13)
> [ 0.923535] ahci 0000:00:11.0: version 3.0
> [ 0.923554] alloc irq_desc for 22 on node -1
> [ 0.923555] alloc kstat_irqs on node -1
> [ 0.923564] ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> [ 0.923721] ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3
> Gbps 0x3f impl SATA mode
> [ 0.923758] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led
> clo pmp pio slum part ccc
> [ 0.929507] scsi0 : ahci
> [ 0.936083] scsi1 : ahci
> [ 0.943752] scsi2 : ahci
> [ 0.945123] scsi3 : ahci
> [ 0.945851] scsi4 : ahci
> [ 0.947687] scsi5 : ahci
> [ 0.947834] ata1: SATA max UDMA/133 irq_stat 0x00400000, PHY RDY
> changed irq 22
> [ 0.947871] ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port
> 0xfe02f180 irq 22
> [ 0.947907] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port
> 0xfe02f200 irq 22
> [ 0.947944] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port
> 0xfe02f280 irq 22
> [ 0.947980] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port
> 0xfe02f300 irq 22
> [ 0.948017] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port
> 0xfe02f380 irq 22
> [ 0.948339] scsi6 : pata_atiixp
> [ 0.948414] scsi7 : pata_atiixp
> [ 0.949196] ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
> [ 0.949234] ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
> [ 1.084835] ata7.00: ATAPI: SONY DVD RW DRU-810A, 1.0e, max UDMA/33
> [ 1.101607] ata7.01: HPA unlocked: 490232639 -> 490234752, native 490234752
> [ 1.101644] ata7.01: ATA-7: Maxtor 6B250R0, BAH41BY0, max UDMA/133
> [ 1.101677] ata7.01: 490234752 sectors, multi 16: LBA48
> [ 1.116811] ata7.00: configured for UDMA/33
> [ 1.134253] ata7.01: configured for UDMA/100
> [ 1.228176] ata3: SATA link down (SStatus 0 SControl 300)
> [ 1.233152] ata5: SATA link down (SStatus 0 SControl 300)
> [ 1.233210] ata4: SATA link down (SStatus 0 SControl 300)
> [ 1.233659] ata6: SATA link down (SStatus 0 SControl 300)
> [ 1.341157] scsi8 : SCSI emulation for USB Mass Storage devices
> [ 1.393662] ata2: softreset failed (device not ready)
> [ 1.393697] ata2: applying SB600 PMP SRST workaround and retrying
> [ 1.556196] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 1.557471] ata2.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
> [ 1.557506] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
> [ 1.559065] ata2.00: configured for UDMA/133
> [ 1.808688] ata1: applying SB600 PMP SRST workaround and retrying
> [ 1.972145] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 1.973383] ata1.00: ATA-8: WDC WD1001FALS-00J7B0, 05.00K05, max UDMA/133
> [ 1.973418] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
> [ 1.974956] ata1.00: configured for UDMA/133
> [ 1.988276] scsi 0:0:0:0: Direct-Access ATA WDC
> WD1001FALS-0 05.0 PQ: 0 ANSI: 5
> [ 1.988439] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 1.988467] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks:
> (1.00 TB/931 GiB)
> [ 1.988491] sd 0:0:0:0: [sda] Write Protect is off
> [ 1.988493] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 1.988505] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 1.988593] sda:
> [ 1.988691] scsi 1:0:0:0: Direct-Access ATA WDC
> WD1001FALS-0 05.0 PQ: 0 ANSI: 5
> [ 1.988885] sd 1:0:0:0: Attached scsi generic sg1 type 0
> [ 1.988888] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks:
> (1.00 TB/931 GiB)
> [ 1.988943] sd 1:0:0:0: [sdb] Write Protect is off
> [ 1.988945] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 1.988970] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 1.989163] sdb:
> [ 1.991478] scsi 6:0:0:0: CD-ROM SONY DVD RW
> DRU-810A 1.0e PQ: 0 ANSI: 5
> [ 1.996140] CE: hpet increasing min_delta_ns to 15000 nsec
> [ 2.001025] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
> [ 2.001059] Uniform CD-ROM driver Revision: 3.20
> [ 2.001160] sr 6:0:0:0: Attached scsi CD-ROM sr0
> [ 2.001199] sr 6:0:0:0: Attached scsi generic sg2 type 5
> [ 2.001308] scsi 6:0:1:0: Direct-Access ATA Maxtor 6B250R0
> BAH4 PQ: 0 ANSI: 5
> [ 2.001430] sd 6:0:1:0: [sdc] 490234752 512-byte logical blocks:
> (251 GB/233 GiB)
> [ 2.001448] sd 6:0:1:0: Attached scsi generic sg3 type 0
> [ 2.001542] sdb1
> [ 2.001553] sd 6:0:1:0: [sdc] Write Protect is off
> [ 2.001554] sd 6:0:1:0: [sdc] Mode Sense: 00 3a 00 00
> [ 2.001578] sd 6:0:1:0: [sdc] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 2.001686] sdb2 sdb3 sdb4 <
> [ 2.001901] sdc: sda1 sda2 sda3 sda4 < sdb5 >
> [ 2.019924] sd 1:0:0:0: [sdb] Attached SCSI disk
> [ 2.020510] sda5 >
> [ 2.022265] sdc1 sdc2
> [ 2.022532] sd 6:0:1:0: [sdc] Attached SCSI disk
> [ 2.027189] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 2.045157] usb 3-2: new low speed USB device using ohci_hcd and address 3
> [ 2.157952] device-mapper: dm-raid45: initialized v0.2594b
> [ 2.159783] ohci1394 0000:03:0e.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> [ 2.162472] md: linear personality registered for level -1
> [ 2.164145] md: multipath personality registered for level -4
> [ 2.166061] md: raid0 personality registered for level 0
> [ 2.168346] md: raid1 personality registered for level 1
> [ 2.236543] raid6: int32x1 1304 MB/s
> [ 2.304530] raid6: int32x2 1410 MB/s
> [ 2.372522] raid6: int32x4 964 MB/s
> [ 2.440508] raid6: int32x8 681 MB/s
> [ 2.508515] raid6: mmxx1 2475 MB/s
> [ 2.576505] raid6: mmxx2 4750 MB/s
> [ 2.644505] raid6: sse1x1 2030 MB/s
> [ 2.712514] raid6: sse1x2 3453 MB/s
> [ 2.780520] raid6: sse2x1 3800 MB/s
> [ 2.848505] raid6: sse2x2 6223 MB/s
> [ 2.848536] raid6: using algorithm sse2x2 (6223 MB/s)
> [ 2.852248] md: raid6 personality registered for level 6
> [ 2.852282] md: raid5 personality registered for level 5
> [ 2.852314] md: raid4 personality registered for level 4
> [ 2.856787] md: raid10 personality registered for level 10
> [ 2.949118] md: bind<sda5>
> [ 2.984447] md: bind<sdb5>
> [ 2.986309] raid1: raid set md1 active with 2 out of 2 mirrors
> [ 2.986361] md1: detected capacity change from 0 to 788179124224
Your array started.
> [ 2.987205] md1: unknown partition table
This is harmless. Your array isn't internally partitioned.
> [ 3.199341] kjournald starting. Commit interval 5 seconds
> [ 3.199356] EXT3-fs: mounted filesystem with ordered data mode.
Here's the pause you mentioned.
> [ 29.671452] scsi 8:0:0:0: Direct-Access Generic USB SD Reader
> 1.00 PQ: 0 ANSI: 0
> [ 29.672325] scsi 8:0:0:1: Direct-Access Generic USB CF Reader
> 1.01 PQ: 0 ANSI: 0
> [ 29.673158] scsi 8:0:0:2: Direct-Access Generic USB xD/SM
> Reader 1.02 PQ: 0 ANSI: 0
> [ 29.674004] scsi 8:0:0:3: Direct-Access Generic USB MS Reader
> 1.03 PQ: 0 ANSI: 0
> [ 29.674326] sd 8:0:0:0: Attached scsi generic sg4 type 0
> [ 29.674432] sd 8:0:0:1: Attached scsi generic sg5 type 0
> [ 29.674536] sd 8:0:0:2: Attached scsi generic sg6 type 0
> [ 29.674640] sd 8:0:0:3: Attached scsi generic sg7 type 0
> [ 29.681659] sd 8:0:0:0: [sdd] Attached SCSI removable disk
> [ 29.682292] sd 8:0:0:1: [sde] Attached SCSI removable disk
> [ 29.683561] sd 8:0:0:2: [sdf] Attached SCSI removable disk
> [ 29.684168] sd 8:0:0:3: [sdg] Attached SCSI removable disk
> [ 29.800664] Adding 2048276k swap on /dev/sda3. Priority:-1
> extents:1 across:2048276k
> [ 29.909600] Adding 2048276k swap on /dev/sdb3. Priority:-2
> extents:1 across:2048276k
> [ 30.022862] udev: starting version 151
> [ 31.253036] shpchp 0000:00:01.0: HPC vendor_id 1022 device_id 9602
> ss_vid 0 ss_did 0
> [ 31.253040] shpchp 0000:00:01.0: Cannot reserve MMIO region
> [ 31.253095] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> [ 31.375816] ACPI: resource piix4_smbus [0xb00-0xb07] conflicts with
> ACPI region SOR1 [0xb00-0xb0f]
> [ 31.375819] ACPI: If an ACPI driver is available for this device,
> you should use it instead of the native driver
> [ 40.205687] type=1505 audit(1301858645.806:2):
> operation="profile_load" pid=687 name="/sbin/dhclient3"
> [ 40.205698] type=1505 audit(1301858645.806:3):
> operation="profile_replace" pid=680 name="/sbin/dhclient3"
> [ 40.205884] type=1505 audit(1301858645.806:4):
> operation="profile_load" pid=687
> name="/usr/lib/NetworkManager/nm-dhcp-client.action"
> [ 40.205902] type=1505 audit(1301858645.806:5):
> operation="profile_replace" pid=680
> name="/usr/lib/NetworkManager/nm-dhcp-client.action"
> [ 40.205995] type=1505 audit(1301858645.806:6):
> operation="profile_load" pid=687
> name="/usr/lib/connman/scripts/dhclient-script"
> [ 40.206020] type=1505 audit(1301858645.806:7):
> operation="profile_replace" pid=680
> name="/usr/lib/connman/scripts/dhclient-script"
> [ 44.951085] type=1505 audit(1301858650.549:8):
> operation="profile_load" pid=967 name="/usr/sbin/ntpd"
> [ 44.951096] type=1505 audit(1301858650.549:9):
> operation="profile_replace" pid=966 name="/usr/sbin/ntpd"
> [ 54.291501] EXT3 FS on sda2, internal journal
> [ 54.635654] kjournald starting. Commit interval 5 seconds
> [ 54.636035] EXT3 FS on sdb2, internal journal
> [ 54.636039] EXT3-fs: mounted filesystem with ordered data mode.
> [ 54.720501] kjournald starting. Commit interval 5 seconds
> [ 54.720663] EXT3 FS on dm-0, internal journal
> [ 54.720667] EXT3-fs: mounted filesystem with ordered data mode.
> [ 55.437462] kjournald starting. Commit interval 5 seconds
> [ 55.437913] EXT3 FS on dm-1, internal journal
> [ 55.437917] EXT3-fs: mounted filesystem with ordered data mode.
> [ 55.522745] kjournald starting. Commit interval 5 seconds
> [ 55.523174] EXT3 FS on dm-2, internal journal
> [ 55.523177] EXT3-fs: mounted filesystem with ordered data mode.
> [ 55.585619] kjournald starting. Commit interval 5 seconds
> [ 55.628189] EXT3 FS on md1, internal journal
> [ 55.628193] EXT3-fs: mounted filesystem with ordered data mode.
Your array is mounted.
> [ 56.931225] kjournald starting. Commit interval 5 seconds
> [ 56.931562] EXT3 FS on dm-3, internal journal
> [ 56.931566] EXT3-fs: mounted filesystem with ordered data mode.
> [ 65.876933] type=1505 audit(1301858671.474:10):
> operation="profile_replace" pid=1164 name="/sbin/dhclient3"
> [ 65.877143] type=1505 audit(1301858671.478:11):
> operation="profile_replace" pid=1164
> name="/usr/lib/NetworkManager/nm-dhcp-client.action"
> [ 65.877257] type=1505 audit(1301858671.478:12):
> operation="profile_replace" pid=1164
> name="/usr/lib/connman/scripts/dhclient-script"
>
> At the end of the 3 second mark lines, the system stops booting and
> needs a series of console inputs (space bar or return) to continue
> booting. Each input advances the process a little bit.
>
> /var/log/messages offered nothing different.
I don't think you have any array problem. You are suffering from one of the asynchronous device probing problems that have cropped up from time to time. I think they've since been solved. Please try some newer kernels.
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 20:09 ` Phil Turmel
@ 2011-04-03 20:17 ` Dennis Grant
2011-04-03 20:20 ` Mathias Burén
0 siblings, 1 reply; 10+ messages in thread
From: Dennis Grant @ 2011-04-03 20:17 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
> I don't think you have any array problem. You are suffering from one of the asynchronous device probing problems that have cropped up from time to time. I think they've since been solved. Please try some newer kernels.
Is there a way to definitively prove if that's the case?
The 32-30 is the newest kernel pushed out by Ubuntu. :(
DG
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Mounting array at boot - works with some kernels but not others
2011-04-03 20:17 ` Dennis Grant
@ 2011-04-03 20:20 ` Mathias Burén
0 siblings, 0 replies; 10+ messages in thread
From: Mathias Burén @ 2011-04-03 20:20 UTC (permalink / raw)
To: Dennis Grant; +Cc: Phil Turmel, linux-raid
On 3 April 2011 21:17, Dennis Grant <reccedg@gmail.com> wrote:
>> I don't think you have any array problem. You are suffering from one of the asynchronous device probing problems that have cropped up from time to time. I think they've since been solved. Please try some newer kernels.
>
> Is there a way to definitively prove if that's the case?
>
> The 32-30 is the newest kernel pushed out by Ubuntu. :(
>
> DG
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Kernel ppa to the rescue. http://kernel.ubuntu.com/~kernel-ppa/mainline/
// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-04-03 20:20 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-03 16:34 Mounting array at boot - works with some kernels but not others Dennis Grant
2011-04-03 17:13 ` Phil Turmel
2011-04-03 17:26 ` Dennis Grant
2011-04-03 17:29 ` Phil Turmel
2011-04-03 17:32 ` Dennis Grant
2011-04-03 17:41 ` Phil Turmel
2011-04-03 19:48 ` Dennis Grant
2011-04-03 20:09 ` Phil Turmel
2011-04-03 20:17 ` Dennis Grant
2011-04-03 20:20 ` Mathias Burén
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).