* mdadm raid can't set proper devices in super-block
@ 2012-03-12 17:38 Carl Engstrom
2012-03-12 18:33 ` John Robinson
0 siblings, 1 reply; 4+ messages in thread
From: Carl Engstrom @ 2012-03-12 17:38 UTC (permalink / raw)
To: linux-raid
resetting mdadm superblock
--------------------------------------------------------------------------------
Hey folks,
I'm having some issues with my md array after upgrading to 11.04.
In my case I have an RAID0 array created from 2 devices (See below)
Boot drives: /dev/sda1
raid 0 dev 1: /dev/sdb1
raid 0 dev 2: /dev/sdc1
RAID device is: /dev/md0
The issue is that the super blocks for /dev/sdb1 and /dev/sdc1 look like this.
----------------
root@uNAS:~# mdadm -E /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : 3424db31:eeb216cb:4c0d2395:9c0bfdf6 (local to host uNAS)
Creation Time : Mon Nov 9 20:31:42 2009
Raid Level : raid0
Used Dev Size : 0
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Sun Feb 13 11:03:20 2011
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 4c6d7ae7 - correct
Events : 13
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
---------------
root@uNAS:~# mdadm -E /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 3424db31:eeb216cb:4c0d2395:9c0bfdf6 (local to host uNAS)
Creation Time : Mon Nov 9 20:31:42 2009
Raid Level : raid0
Used Dev Size : 0
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Sun Feb 13 11:03:20 2011
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 4c6d7af9 - correct
Events : 13
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
--------
the array will start with:
mdadm -A --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
and the array looks like this:
root@uNAS:~# mdadm -Q --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Mon Nov 9 20:31:42 2009
Raid Level : raid0
Array Size : 3904887168 (3723.99 GiB 3998.60 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Feb 13 11:03:20 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
UUID : 3424db31:eeb216cb:4c0d2395:9c0bfdf6 (local to host uNAS)
Events : 0.13
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
--------------
but for some reason the super block isn't being updated...so the array won't
autostart. My understanding is that the update=super-minor tells the system to
start each drive and update the minor field...which I thought would fix this.
here is the ooutput from the start up:
---------------
root@uNAS:~# mdadm -Av --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
mdadm: looking for devices for /dev/md0
mdadm: updating superblock of /dev/sdb1 with minor number 0
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 0.
mdadm: updating superblock of /dev/sdc1 with minor number 0
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 1.
mdadm: added /dev/sdc1 to /dev/md0 as 1
mdadm: added /dev/sdb1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 2 drives.
-------------------
Anyone know what's going on?
thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mdadm raid can't set proper devices in super-block
2012-03-12 17:38 mdadm raid can't set proper devices in super-block Carl Engstrom
@ 2012-03-12 18:33 ` John Robinson
2012-03-14 17:04 ` Carl Engstrom
0 siblings, 1 reply; 4+ messages in thread
From: John Robinson @ 2012-03-12 18:33 UTC (permalink / raw)
To: Carl Engstrom; +Cc: linux-raid
On 12/03/2012 17:38, Carl Engstrom wrote:
> resetting mdadm superblock
>
> --------------------------------------------------------------------------------
>
> Hey folks,
>
> I'm having some issues with my md array after upgrading to 11.04.
[...]
> Number Major Minor RaidDevice State
> this 1 8 17 1 active sync /dev/sdb1
>
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> --------
>
> the array will start with:
> mdadm -A --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
So it starts just fine if you specify the devices...
> Anyone know what's going on?
--update=super-minor is working fine; both devices have a preferred
minor device number of zero, as they should for the array to be /dev/md0.
What happens if you
mdadm --stop /dev/md0
mdadm --assemble --scan --verbose /dev/md0
?
Where do you want to mount /dev/md0?
What messages do you get during boot-up (dmesg) about why md0 isn't
being assembled?
What's in your /etc/mdadm.conf?
If /etc/mdadm.conf says sda1 and sdb1, fix it and do whatever you need
to do on Ubuntu to rebuild your initrd/initramfs (so that your edited
mdadm.conf goes into it), then reboot.
Hope something somewhere in amongst this lot helps...
Cheers,
John.
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: mdadm raid can't set proper devices in super-block
2012-03-12 18:33 ` John Robinson
@ 2012-03-14 17:04 ` Carl Engstrom
2012-03-16 23:37 ` FW: " Carl Engstrom
0 siblings, 1 reply; 4+ messages in thread
From: Carl Engstrom @ 2012-03-14 17:04 UTC (permalink / raw)
To: 'John Robinson'; +Cc: linux-raid
...
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> --------
>
> the array will start with:
> mdadm -A --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
Q: So it starts just fine if you specify the devices...
A: Yes the array starts fine when I put the parameters in. There is also
an issue where the expected /dev/md0 shows up as md_d0, but I can live with
that.
> Anyone know what's going on?
--update=super-minor is working fine; both devices have a preferred minor
device number of zero, as they should for the array to be /dev/md0.
Q: What happens if you
mdadm --stop /dev/md0
mdadm --assemble --scan --verbose /dev/md0 ?
A: The device isn't identified in the config file. I generally don't put
anything in the config file and it's always seemed to work.
Q: Where do you want to mount /dev/md0?
A: /backup
What messages do you get during boot-up (dmesg) about why md0 isn't being
assembled?
============
[ 0.481723] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x30a0 irq
14
[ 0.481730] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x30a8 irq
15
[ 0.806077] md: linear personality registered for level -1
[ 0.824006] md: multipath personality registered for level -4
[ 0.965715] md: raid0 personality registered for level 0
[ 0.993103] md: raid1 personality registered for level 1
[ 1.518611] mdadm: sending ioctl 1261 to a partition!
[ 1.518618] mdadm: sending ioctl 1261 to a partition!
[ 1.518830] mdadm: sending ioctl 1261 to a partition!
[ 1.518835] mdadm: sending ioctl 1261 to a partition!
[ 1.519733] mdadm: sending ioctl 1261 to a partition!
[ 1.519738] mdadm: sending ioctl 1261 to a partition!
[ 1.522247] mdadm: sending ioctl 1261 to a partition!
[ 1.522254] mdadm: sending ioctl 1261 to a partition!
[ 1.523580] mdadm: sending ioctl 1261 to a partition!
[ 1.523587] mdadm: sending ioctl 1261 to a partition!
[ 1.524944] mdadm: sending ioctl 1261 to a partition!
[ 1.524949] mdadm: sending ioctl 1261 to a partition!
[ 1.525971] mdadm: sending ioctl 1261 to a partition!
[ 1.525978] mdadm: sending ioctl 1261 to a partition!
[ 2.080886] md: raid6 personality registered for level 6
[ 2.080892] md: raid5 personality registered for level 5
[ 2.080897] md: raid4 personality registered for level 4
[ 2.092484] md: raid10 personality registered for level 10
[ 16.430546] mdadm: sending ioctl 1261 to a partition!
[ 16.430551] mdadm: sending ioctl 1261 to a partition!
[ 16.440763] mdadm: sending ioctl 1261 to a partition!
[ 16.440769] mdadm: sending ioctl 1261 to a partition!
[ 16.441262] mdadm: sending ioctl 1261 to a partition!
[ 16.441267] mdadm: sending ioctl 1261 to a partition!
[ 16.442125] mdadm: sending ioctl 1261 to a partition!
[ 16.442130] mdadm: sending ioctl 1261 to a partition!
[ 16.442710] mdadm: sending ioctl 1261 to a partition!
[ 16.442715] mdadm: sending ioctl 1261 to a partition!
[ 16.442915] mdadm: sending ioctl 1261 to a partition!
[ 16.442919] mdadm: sending ioctl 1261 to a partition!
[ 16.443693] mdadm: sending ioctl 1261 to a partition!
[ 16.443709] mdadm: sending ioctl 1261 to a partition!
[ 16.458427] md: bind<sdc1>
[ 16.458843] mdadm: sending ioctl 1261 to a partition!
[ 16.458848] mdadm: sending ioctl 1261 to a partition!
[ 16.465101] mdadm: sending ioctl 1261 to a partition!
[ 16.465107] mdadm: sending ioctl 1261 to a partition!
[ 16.465621] mdadm: sending ioctl 1261 to a partition!
[ 16.465627] mdadm: sending ioctl 1261 to a partition!
[ 16.466434] mdadm: sending ioctl 1261 to a partition!
[ 16.466439] mdadm: sending ioctl 1261 to a partition!
[ 16.467033] mdadm: sending ioctl 1261 to a partition!
[ 16.467037] mdadm: sending ioctl 1261 to a partition!
[ 16.468037] mdadm: sending ioctl 1261 to a partition!
[ 16.468043] mdadm: sending ioctl 1261 to a partition!
[ 16.468447] mdadm: sending ioctl 1261 to a partition!
[ 16.468463] mdadm: sending ioctl 1261 to a partition!
[ 16.474276] mdadm: sending ioctl 1261 to a partition!
[ 16.474282] mdadm: sending ioctl 1261 to a partition!
[ 16.475038] mdadm: sending ioctl 1261 to a partition!
[ 16.475043] mdadm: sending ioctl 1261 to a partition!
[ 16.476065] mdadm: sending ioctl 1261 to a partition!
[ 16.476070] mdadm: sending ioctl 1261 to a partition!
[ 16.476843] mdadm: sending ioctl 1261 to a partition!
[ 16.476848] mdadm: sending ioctl 1261 to a partition!
[ 16.478447] mdadm: sending ioctl 1261 to a partition!
[ 16.478453] mdadm: sending ioctl 1261 to a partition!
[ 16.478865] mdadm: sending ioctl 1261 to a partition!
[ 16.478869] mdadm: sending ioctl 1261 to a partition!
[ 3885.067642] mdadm: sending ioctl 1261 to a partition!
[ 3885.067648] mdadm: sending ioctl 1261 to a partition!
[ 3885.068683] mdadm: sending ioctl 1261 to a partition!
[ 3885.068687] mdadm: sending ioctl 1261 to a partition!
[ 3885.088444] mdadm: sending ioctl 1261 to a partition!
[ 3885.088450] mdadm: sending ioctl 1261 to a partition!
[ 3886.446271] mdadm: sending ioctl 1261 to a partition!
[ 3886.446277] mdadm: sending ioctl 1261 to a partition!
[ 3886.470887] mdadm: sending ioctl 1261 to a partition!
[ 3886.470893] mdadm: sending ioctl 1261 to a partition!
[ 3886.473206] mdadm: sending ioctl 1261 to a partition!
========================
Q: What's in your /etc/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 partitions
# 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
# This file was auto-generated on Fri, 03 Oct 2008 07:40:26 -0700
# by mkconf $Id$
==================
If /etc/mdadm.conf says sda1 and sdb1, fix it and do whatever you need to do
on Ubuntu to rebuild your initrd/initramfs (so that your edited mdadm.conf
goes into it), then reboot.
I'll look up mdadm.conf and figure out how to add the lines that aren't
there.
Hope something somewhere in amongst this lot helps...
Cheers,
John.
^ permalink raw reply [flat|nested] 4+ messages in thread
* FW: mdadm raid can't set proper devices in super-block
2012-03-14 17:04 ` Carl Engstrom
@ 2012-03-16 23:37 ` Carl Engstrom
0 siblings, 0 replies; 4+ messages in thread
From: Carl Engstrom @ 2012-03-16 23:37 UTC (permalink / raw)
To: linux-raid
...
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> --------
>
> the array will start with:
> mdadm -A --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
Q: So it starts just fine if you specify the devices...
A: Yes the array starts fine when I put the parameters in. There is also
an issue where the expected /dev/md0 shows up as md_d0, but I can live with
that.
> Anyone know what's going on?
--update=super-minor is working fine; both devices have a preferred minor
device number of zero, as they should for the array to be /dev/md0.
Q: What happens if you
mdadm --stop /dev/md0
mdadm --assemble --scan --verbose /dev/md0 ?
A: The device isn't identified in the config file. I generally don't put
anything in the config file and it's always seemed to work.
Q: Where do you want to mount /dev/md0?
A: /backup
What messages do you get during boot-up (dmesg) about why md0 isn't being
assembled?
============
[ 0.481723] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x30a0 irq
14
[ 0.481730] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x30a8 irq
15
[ 0.806077] md: linear personality registered for level -1
[ 0.824006] md: multipath personality registered for level -4
[ 0.965715] md: raid0 personality registered for level 0
[ 0.993103] md: raid1 personality registered for level 1
[ 1.518611] mdadm: sending ioctl 1261 to a partition!
[ 1.518618] mdadm: sending ioctl 1261 to a partition!
[ 1.518830] mdadm: sending ioctl 1261 to a partition!
[ 1.518835] mdadm: sending ioctl 1261 to a partition!
[ 1.519733] mdadm: sending ioctl 1261 to a partition!
[ 1.519738] mdadm: sending ioctl 1261 to a partition!
[ 1.522247] mdadm: sending ioctl 1261 to a partition!
[ 1.522254] mdadm: sending ioctl 1261 to a partition!
[ 1.523580] mdadm: sending ioctl 1261 to a partition!
[ 1.523587] mdadm: sending ioctl 1261 to a partition!
[ 1.524944] mdadm: sending ioctl 1261 to a partition!
[ 1.524949] mdadm: sending ioctl 1261 to a partition!
[ 1.525971] mdadm: sending ioctl 1261 to a partition!
[ 1.525978] mdadm: sending ioctl 1261 to a partition!
[ 2.080886] md: raid6 personality registered for level 6
[ 2.080892] md: raid5 personality registered for level 5
[ 2.080897] md: raid4 personality registered for level 4
[ 2.092484] md: raid10 personality registered for level 10
[ 16.430546] mdadm: sending ioctl 1261 to a partition!
[ 16.430551] mdadm: sending ioctl 1261 to a partition!
[ 16.440763] mdadm: sending ioctl 1261 to a partition!
[ 16.440769] mdadm: sending ioctl 1261 to a partition!
[ 16.441262] mdadm: sending ioctl 1261 to a partition!
[ 16.441267] mdadm: sending ioctl 1261 to a partition!
[ 16.442125] mdadm: sending ioctl 1261 to a partition!
[ 16.442130] mdadm: sending ioctl 1261 to a partition!
[ 16.442710] mdadm: sending ioctl 1261 to a partition!
[ 16.442715] mdadm: sending ioctl 1261 to a partition!
[ 16.442915] mdadm: sending ioctl 1261 to a partition!
[ 16.442919] mdadm: sending ioctl 1261 to a partition!
[ 16.443693] mdadm: sending ioctl 1261 to a partition!
[ 16.443709] mdadm: sending ioctl 1261 to a partition!
[ 16.458427] md: bind<sdc1>
[ 16.458843] mdadm: sending ioctl 1261 to a partition!
[ 16.458848] mdadm: sending ioctl 1261 to a partition!
[ 16.465101] mdadm: sending ioctl 1261 to a partition!
[ 16.465107] mdadm: sending ioctl 1261 to a partition!
[ 16.465621] mdadm: sending ioctl 1261 to a partition!
[ 16.465627] mdadm: sending ioctl 1261 to a partition!
[ 16.466434] mdadm: sending ioctl 1261 to a partition!
[ 16.466439] mdadm: sending ioctl 1261 to a partition!
[ 16.467033] mdadm: sending ioctl 1261 to a partition!
[ 16.467037] mdadm: sending ioctl 1261 to a partition!
[ 16.468037] mdadm: sending ioctl 1261 to a partition!
[ 16.468043] mdadm: sending ioctl 1261 to a partition!
[ 16.468447] mdadm: sending ioctl 1261 to a partition!
[ 16.468463] mdadm: sending ioctl 1261 to a partition!
[ 16.474276] mdadm: sending ioctl 1261 to a partition!
[ 16.474282] mdadm: sending ioctl 1261 to a partition!
[ 16.475038] mdadm: sending ioctl 1261 to a partition!
[ 16.475043] mdadm: sending ioctl 1261 to a partition!
[ 16.476065] mdadm: sending ioctl 1261 to a partition!
[ 16.476070] mdadm: sending ioctl 1261 to a partition!
[ 16.476843] mdadm: sending ioctl 1261 to a partition!
[ 16.476848] mdadm: sending ioctl 1261 to a partition!
[ 16.478447] mdadm: sending ioctl 1261 to a partition!
[ 16.478453] mdadm: sending ioctl 1261 to a partition!
[ 16.478865] mdadm: sending ioctl 1261 to a partition!
[ 16.478869] mdadm: sending ioctl 1261 to a partition!
[ 3885.067642] mdadm: sending ioctl 1261 to a partition!
[ 3885.067648] mdadm: sending ioctl 1261 to a partition!
[ 3885.068683] mdadm: sending ioctl 1261 to a partition!
[ 3885.068687] mdadm: sending ioctl 1261 to a partition!
[ 3885.088444] mdadm: sending ioctl 1261 to a partition!
[ 3885.088450] mdadm: sending ioctl 1261 to a partition!
[ 3886.446271] mdadm: sending ioctl 1261 to a partition!
[ 3886.446277] mdadm: sending ioctl 1261 to a partition!
[ 3886.470887] mdadm: sending ioctl 1261 to a partition!
[ 3886.470893] mdadm: sending ioctl 1261 to a partition!
[ 3886.473206] mdadm: sending ioctl 1261 to a partition!
========================
Q: What's in your /etc/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 partitions
# 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
# This file was auto-generated on Fri, 03 Oct 2008 07:40:26 -0700 # by
mkconf $Id$ ==================
If /etc/mdadm.conf says sda1 and sdb1, fix it and do whatever you need to do
on Ubuntu to rebuild your initrd/initramfs (so that your edited mdadm.conf
goes into it), then reboot.
I'll look up mdadm.conf and figure out how to add the lines that aren't
there.
Hope something somewhere in amongst this lot helps...
Cheers,
John.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-03-16 23:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-12 17:38 mdadm raid can't set proper devices in super-block Carl Engstrom
2012-03-12 18:33 ` John Robinson
2012-03-14 17:04 ` Carl Engstrom
2012-03-16 23:37 ` FW: " Carl Engstrom
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).