Quantcast

Help, my RAID won't start

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Help, my RAID won't start

Kevin O'Gorman
I've been fooling with this for a while.  Some things are fixed, but the darned thing still isn't right.

I've been following advice from a combination of sources, because nothing I've found is complete, but that makes it harder to be sure I'm on the right track.

So here it is: a core i-7, 32GB RAM, 6 internal hard drives, 4 of which are 4 TB.  Three of those four are for my RAID, which I want to set up as RAID5.  I have them partitioned, so that the raid will be on the collection of /dev/sdd1, /dev/sde1 and /dev/sdf1.

As things now stand, /proc/mdstat contains
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active (auto-read-only) raid5 sdf1[3] sde1[1] sdd1[0]
      7813771264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      bitmap: 0/30 pages [0KB], 65536KB chunk

unused devices: <none>

and lsblk says (in part)
sdd             8:48   0   3.7T  0 disk 
└─sdd1          8:49   0   3.7T  0 part 
  └─md127       9:127  0   7.3T  0 raid5
    └─md127p1 259:0    0   7.3T  0 md   
sde             8:64   0   3.7T  0 disk 
└─sde1          8:65   0   3.7T  0 part 
  └─md127       9:127  0   7.3T  0 raid5
    └─md127p1 259:0    0   7.3T  0 md   
sdf             8:80   0   3.7T  0 disk 
└─sdf1          8:81   0   3.7T  0 part 
  └─md127       9:127  0   7.3T  0 raid5
    └─md127p1 259:0    0   7.3T  0 md

and blkid says
/dev/md127p1/dev/md127p1: UUID="a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9" TYPE="ext4" PARTLABEL="RAID5-3" PARTUUID="525e3db6-c683-4a98-b503-c2615f717ee2"

/dev/md127: PTUUID="23697ce2-b48f-44b4-8af9-de37e0b77a58" PTTYPE="gpt": UUID="a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9" TYPE="ext4" PARTLABEL="RAID5-3" PARTUUID="525e3db6-c683-4a98-b503-c2615f717ee2"
/dev/md127: PTUUID="23697ce2-b48f-44b4-8af9-de37e0b77a58" PTTYPE="gpt"

and I created /dev/md3p1 with the command
mkfs.ext4 -m .01 -b 4096 -E stride-32,stripe-width-64 /dev/md3p1

/etc/mdadm/mdadm.conf has the line
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

/etc/fstab has the line
/dev/md3p1      /raid3        ext4    defaults,nofail  0       0

But when I start up the system, there is no /raid3 mounted.  Moreover, /var/log/syslog contains
the cryptic
Apr  3 20:59:27 camelot-x systemd[1]: dev-md3p1.device: Job dev-md3p1.device/start timed out.
Apr  3 20:59:27 camelot-x systemd[1]: Timed out waiting for device dev-md3p1.device.
Apr  3 20:59:27 camelot-x systemd[1]: Dependency failed for /raid3.
Apr  3 20:59:27 camelot-x systemd[1]: raid3.mount: Job raid3.mount/start failed with result 'dependency'.
Apr  3 20:59:27 camelot-x systemd[1]: Startup finished in 2.942s (kernel) + 1min 31.660s (userspace) = 1min 34.603s.
Apr  3 20:59:27 camelot-x systemd[1]: dev-md3p1.device: Job dev-md3p1.device/start failed with result 'timeout'.

And I have no idea what the "dependency" is about.
It does much the same if I say "sudo mount /raid3" --- and the command seems to complete okay, but still nothing is mounted.

Help!
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Rashkae-2
On 17-04-04 12:17 AM, Kevin O'Gorman wrote:
> I've been fooling with this for a while.  Some things are fixed, but the
> darned thing still isn't right.
>

It looks like you've partitioned your RAID device itself.  I'm not too
sure how that's supposed to look, as I've never set them up that way.
(I partition the physical devices, as you've done, then create a raid
array, and create my FS directly on that array.)

That's not to say what you have here is wrong, just that I'm not sure
how to interpret the blkid output.

But actually fixing your current situation is probably going to be
simple.. *Don't* use device names in your fstab.. put in the UUID

Example:


UUID=a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9 /raid3        ext4   defaults
  0    2

(Note the removal of nofail, and changing the last field to 2)


You might also want to update your mdadm.conf

Check the device name of your running array with cat /proc/mdstat

Assuming it's the same as you have in the original message, md127

mdadm --detail --scan /dev/md127

Use the output of that command to replace the ARRAY /dev/md3
metadata=1.2 name=camelot-x:3
UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed





--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Kevin O'Gorman


On Tue, Apr 4, 2017 at 6:50 AM, Rashkae <[hidden email]> wrote:
On 17-04-04 12:17 AM, Kevin O'Gorman wrote:
I've been fooling with this for a while.  Some things are fixed, but the
darned thing still isn't right.


It looks like you've partitioned your RAID device itself.  I'm not too sure how that's supposed to look, as I've never set them up that way.
(I partition the physical devices, as you've done, then create a raid array, and create my FS directly on that array.)

That's not to say what you have here is wrong, just that I'm not sure how to interpret the blkid output.

But actually fixing your current situation is probably going to be simple.. *Don't* use device names in your fstab.. put in the UUID

Example:


UUID=a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9 /raid3        ext4   defaults  0    2

(Note the removal of nofail, and changing the last field to 2)


You might also want to update your mdadm.conf

Check the device name of your running array with cat /proc/mdstat

Assuming it's the same as you have in the original message, md127

mdadm --detail --scan /dev/md127

Use the output of that command to replace the ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

Thanks...

I tried your entry in my /etc/fstab, and "mount /raid3", and while the mount finished without reporting an error, there
was no filesystem on /raid3, and /var/log/syslog now ends with

Apr  4 07:37:14 camelot-x wpa_supplicant[1553]: wlp7s0: WPA: Group rekeying completed with b4:75:0e:fc:84:9a [GTK=TKIP]
Apr  4 07:46:46 camelot-x kernel: [38933.017667] EXT4-fs (md127p1): mounted filesystem with ordered data mode. Opts: (null)
Apr  4 07:46:46 camelot-x systemd[1]: raid3.mount: Unit is bound to inactive unit dev-md3p1.device. Stopping, too.
Apr  4 07:46:46 camelot-x systemd[1]: Unmounting /raid3...
Apr  4 07:46:46 camelot-x systemd[1]: Unmounted /raid3.

All of this in spite of /proc/mdstat reporting an active RAID array....

So I tried putting the filesystem directly on the RAID, as you suggested, with
dd if=/dev/zero of=/dev/md127 bs=1024 count=1024
mdadm --stop /dev/md127
mdadm --remove /dev/md127
mdadm -A --scan /dev/md3
mkfs.ext4 -m .01 -b 4096 -E stride=32,stripe-width=64 /dev/md3

And was still unable to mount /raid3, but now I can see the syslog is complaining that /raid3 is still bound to the
non-existent partition /dev/md3p1.  So I mounted it on a new directory /raid3x.  It seems okay, in that it has
lost+found and lots of space.  But it did so last time too.

I'm going to stick with my /etc/fstab entry for now, because I want to be sure I get a warning if it ever gets assembled
as anything except /dev/md3.  The mdadm.conf entry is still correct, so I'm going to reboot to make sure everything gets
assembled correctly.  Back in a few.....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Kevin O'Gorman


On Tue, Apr 4, 2017 at 8:18 AM, Kevin O'Gorman <[hidden email]> wrote:


On Tue, Apr 4, 2017 at 6:50 AM, Rashkae <[hidden email]> wrote:
On 17-04-04 12:17 AM, Kevin O'Gorman wrote:
I've been fooling with this for a while.  Some things are fixed, but the
darned thing still isn't right.


It looks like you've partitioned your RAID device itself.  I'm not too sure how that's supposed to look, as I've never set them up that way.
(I partition the physical devices, as you've done, then create a raid array, and create my FS directly on that array.)

That's not to say what you have here is wrong, just that I'm not sure how to interpret the blkid output.

But actually fixing your current situation is probably going to be simple.. *Don't* use device names in your fstab.. put in the UUID

Example:


UUID=a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9 /raid3        ext4   defaults  0    2

(Note the removal of nofail, and changing the last field to 2)


You might also want to update your mdadm.conf

Check the device name of your running array with cat /proc/mdstat

Assuming it's the same as you have in the original message, md127

mdadm --detail --scan /dev/md127

Use the output of that command to replace the ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

Thanks...

I tried your entry in my /etc/fstab, and "mount /raid3", and while the mount finished without reporting an error, there
was no filesystem on /raid3, and /var/log/syslog now ends with

Apr  4 07:37:14 camelot-x wpa_supplicant[1553]: wlp7s0: WPA: Group rekeying completed with b4:75:0e:fc:84:9a [GTK=TKIP]
Apr  4 07:46:46 camelot-x kernel: [38933.017667] EXT4-fs (md127p1): mounted filesystem with ordered data mode. Opts: (null)
Apr  4 07:46:46 camelot-x systemd[1]: raid3.mount: Unit is bound to inactive unit dev-md3p1.device. Stopping, too.
Apr  4 07:46:46 camelot-x systemd[1]: Unmounting /raid3...
Apr  4 07:46:46 camelot-x systemd[1]: Unmounted /raid3.

All of this in spite of /proc/mdstat reporting an active RAID array....

So I tried putting the filesystem directly on the RAID, as you suggested, with
dd if=/dev/zero of=/dev/md127 bs=1024 count=1024
mdadm --stop /dev/md127
mdadm --remove /dev/md127
mdadm -A --scan /dev/md3
mkfs.ext4 -m .01 -b 4096 -E stride=32,stripe-width=64 /dev/md3

And was still unable to mount /raid3, but now I can see the syslog is complaining that /raid3 is still bound to the
non-existent partition /dev/md3p1.  So I mounted it on a new directory /raid3x.  It seems okay, in that it has
lost+found and lots of space.  But it did so last time too.

I'm going to stick with my /etc/fstab entry for now, because I want to be sure I get a warning if it ever gets assembled
as anything except /dev/md3.  The mdadm.conf entry is still correct, so I'm going to reboot to make sure everything gets
assembled correctly.  Back in a few.....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.

That did NOT work.  Not exactly, anyway.

There was nothing mounted on /raid3 after the reboot, and there was a /dev/md127 that I cannot get rid of in spite of multiple tries at
mdadm --stop /dev/md127
mdadm --remove /dev/md127

But it did not show up in /proc/mdstat any more so I reassembled it
mdadm -A --scan /dev/md3
And it was not only assembled but mounted too.

lsblk shows
sdd       8:48   0   3.7T  0 disk 
└─sdd1    8:49   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sde       8:64   0   3.7T  0 disk 
└─sde1    8:65   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sdf       8:80   0   3.7T  0 disk 
└─sdf1    8:81   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3

blkid shows
/dev/sdd1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="24275237-b493-169e-9e88-df0debaae551" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-a" PARTUUID="729558f8-fbcf-45c1-9d9b-c6bfe6ec4bf6"
/dev/sde1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="cf36e69a-c110-b0ae-b504-fcfeb2dea024" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-c" PARTUUID="654fc581-f6ef-43a4-b583-6f3cd7d52e61"
/dev/sdf1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="54fbf294-766f-c8eb-9663-02a39534003f" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-b" PARTUUID="f6a7ba77-278e-4b64-8f7e-16041b85f097"
and
/dev/md3: UUID="97309dc0-0f54-45d8-853f-af99dead3ed2" TYPE="ext4"

df -h shows
/dev/md3        7.3T   51M  7.3T   1% /raid3

QUESIONS:

So why is there still a /dev/md127, and why does the array not assemble as /dev/md3?
/etc/mdadm/mdadm.conf contains just the one array:
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
which is still what I get from
mdadm --detail --scan

mount and umount commands work as expected, both with my original /etc/fstab entry or with yours.  I'll leave yours in place and try a reboot....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Kevin O'Gorman
SUCCESS.  Sort of.  It raises another question.

On reboot, I had /raid3.  But it is mounted on /dev/md127.  It appears the system is ignoring the device in my mdadm.conf entry.  Here it is again:
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
And here's the output of mdadm --detail --scan
ARRAY /dev/md/camelot-x:3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

And indeed there is a /dev/camelot-x:3

On Tue, Apr 4, 2017 at 8:48 AM, Kevin O'Gorman <[hidden email]> wrote:


On Tue, Apr 4, 2017 at 8:18 AM, Kevin O'Gorman <[hidden email]> wrote:


On Tue, Apr 4, 2017 at 6:50 AM, Rashkae <[hidden email]> wrote:
On 17-04-04 12:17 AM, Kevin O'Gorman wrote:
I've been fooling with this for a while.  Some things are fixed, but the
darned thing still isn't right.


It looks like you've partitioned your RAID device itself.  I'm not too sure how that's supposed to look, as I've never set them up that way.
(I partition the physical devices, as you've done, then create a raid array, and create my FS directly on that array.)

That's not to say what you have here is wrong, just that I'm not sure how to interpret the blkid output.

But actually fixing your current situation is probably going to be simple.. *Don't* use device names in your fstab.. put in the UUID

Example:


UUID=a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9 /raid3        ext4   defaults  0    2

(Note the removal of nofail, and changing the last field to 2)


You might also want to update your mdadm.conf

Check the device name of your running array with cat /proc/mdstat

Assuming it's the same as you have in the original message, md127

mdadm --detail --scan /dev/md127

Use the output of that command to replace the ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

Thanks...

I tried your entry in my /etc/fstab, and "mount /raid3", and while the mount finished without reporting an error, there
was no filesystem on /raid3, and /var/log/syslog now ends with

Apr  4 07:37:14 camelot-x wpa_supplicant[1553]: wlp7s0: WPA: Group rekeying completed with b4:75:0e:fc:84:9a [GTK=TKIP]
Apr  4 07:46:46 camelot-x kernel: [38933.017667] EXT4-fs (md127p1): mounted filesystem with ordered data mode. Opts: (null)
Apr  4 07:46:46 camelot-x systemd[1]: raid3.mount: Unit is bound to inactive unit dev-md3p1.device. Stopping, too.
Apr  4 07:46:46 camelot-x systemd[1]: Unmounting /raid3...
Apr  4 07:46:46 camelot-x systemd[1]: Unmounted /raid3.

All of this in spite of /proc/mdstat reporting an active RAID array....

So I tried putting the filesystem directly on the RAID, as you suggested, with
dd if=/dev/zero of=/dev/md127 bs=1024 count=1024
mdadm --stop /dev/md127
mdadm --remove /dev/md127
mdadm -A --scan /dev/md3
mkfs.ext4 -m .01 -b 4096 -E stride=32,stripe-width=64 /dev/md3

And was still unable to mount /raid3, but now I can see the syslog is complaining that /raid3 is still bound to the
non-existent partition /dev/md3p1.  So I mounted it on a new directory /raid3x.  It seems okay, in that it has
lost+found and lots of space.  But it did so last time too.

I'm going to stick with my /etc/fstab entry for now, because I want to be sure I get a warning if it ever gets assembled
as anything except /dev/md3.  The mdadm.conf entry is still correct, so I'm going to reboot to make sure everything gets
assembled correctly.  Back in a few.....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.

That did NOT work.  Not exactly, anyway.

There was nothing mounted on /raid3 after the reboot, and there was a /dev/md127 that I cannot get rid of in spite of multiple tries at
mdadm --stop /dev/md127
mdadm --remove /dev/md127

But it did not show up in /proc/mdstat any more so I reassembled it
mdadm -A --scan /dev/md3
And it was not only assembled but mounted too.

lsblk shows
sdd       8:48   0   3.7T  0 disk 
└─sdd1    8:49   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sde       8:64   0   3.7T  0 disk 
└─sde1    8:65   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sdf       8:80   0   3.7T  0 disk 
└─sdf1    8:81   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3

blkid shows
/dev/sdd1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="24275237-b493-169e-9e88-df0debaae551" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-a" PARTUUID="729558f8-fbcf-45c1-9d9b-c6bfe6ec4bf6"
/dev/sde1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="cf36e69a-c110-b0ae-b504-fcfeb2dea024" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-c" PARTUUID="654fc581-f6ef-43a4-b583-6f3cd7d52e61"
/dev/sdf1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="54fbf294-766f-c8eb-9663-02a39534003f" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-b" PARTUUID="f6a7ba77-278e-4b64-8f7e-16041b85f097"
and
/dev/md3: UUID="97309dc0-0f54-45d8-853f-af99dead3ed2" TYPE="ext4"

df -h shows
/dev/md3        7.3T   51M  7.3T   1% /raid3

QUESIONS:

So why is there still a /dev/md127, and why does the array not assemble as /dev/md3?
/etc/mdadm/mdadm.conf contains just the one array:
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
which is still what I get from
mdadm --detail --scan

mount and umount commands work as expected, both with my original /etc/fstab entry or with yours.  I'll leave yours in place and try a reboot....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.




--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Kevin O'Gorman


On Tue, Apr 4, 2017 at 8:56 AM, Kevin O'Gorman <[hidden email]> wrote:
 

On Tue, Apr 4, 2017 at 8:48 AM, Kevin O'Gorman <[hidden email]> wrote:


On Tue, Apr 4, 2017 at 8:18 AM, Kevin O'Gorman <[hidden email]> wrote:


On Tue, Apr 4, 2017 at 6:50 AM, Rashkae <[hidden email]> wrote:
On 17-04-04 12:17 AM, Kevin O'Gorman wrote:
I've been fooling with this for a while.  Some things are fixed, but the
darned thing still isn't right.


It looks like you've partitioned your RAID device itself.  I'm not too sure how that's supposed to look, as I've never set them up that way.
(I partition the physical devices, as you've done, then create a raid array, and create my FS directly on that array.)

That's not to say what you have here is wrong, just that I'm not sure how to interpret the blkid output.

But actually fixing your current situation is probably going to be simple.. *Don't* use device names in your fstab.. put in the UUID

Example:


UUID=a6470f33-4709-4c96-8cf4-2fc0a4c2cdf9 /raid3        ext4   defaults  0    2

(Note the removal of nofail, and changing the last field to 2)


You might also want to update your mdadm.conf

Check the device name of your running array with cat /proc/mdstat

Assuming it's the same as you have in the original message, md127

mdadm --detail --scan /dev/md127

Use the output of that command to replace the ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

Thanks...

I tried your entry in my /etc/fstab, and "mount /raid3", and while the mount finished without reporting an error, there
was no filesystem on /raid3, and /var/log/syslog now ends with

Apr  4 07:37:14 camelot-x wpa_supplicant[1553]: wlp7s0: WPA: Group rekeying completed with b4:75:0e:fc:84:9a [GTK=TKIP]
Apr  4 07:46:46 camelot-x kernel: [38933.017667] EXT4-fs (md127p1): mounted filesystem with ordered data mode. Opts: (null)
Apr  4 07:46:46 camelot-x systemd[1]: raid3.mount: Unit is bound to inactive unit dev-md3p1.device. Stopping, too.
Apr  4 07:46:46 camelot-x systemd[1]: Unmounting /raid3...
Apr  4 07:46:46 camelot-x systemd[1]: Unmounted /raid3.

All of this in spite of /proc/mdstat reporting an active RAID array....

So I tried putting the filesystem directly on the RAID, as you suggested, with
dd if=/dev/zero of=/dev/md127 bs=1024 count=1024
mdadm --stop /dev/md127
mdadm --remove /dev/md127
mdadm -A --scan /dev/md3
mkfs.ext4 -m .01 -b 4096 -E stride=32,stripe-width=64 /dev/md3

And was still unable to mount /raid3, but now I can see the syslog is complaining that /raid3 is still bound to the
non-existent partition /dev/md3p1.  So I mounted it on a new directory /raid3x.  It seems okay, in that it has
lost+found and lots of space.  But it did so last time too.

I'm going to stick with my /etc/fstab entry for now, because I want to be sure I get a warning if it ever gets assembled
as anything except /dev/md3.  The mdadm.conf entry is still correct, so I'm going to reboot to make sure everything gets
assembled correctly.  Back in a few.....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.

That did NOT work.  Not exactly, anyway.

There was nothing mounted on /raid3 after the reboot, and there was a /dev/md127 that I cannot get rid of in spite of multiple tries at
mdadm --stop /dev/md127
mdadm --remove /dev/md127

But it did not show up in /proc/mdstat any more so I reassembled it
mdadm -A --scan /dev/md3
And it was not only assembled but mounted too.

lsblk shows
sdd       8:48   0   3.7T  0 disk 
└─sdd1    8:49   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sde       8:64   0   3.7T  0 disk 
└─sde1    8:65   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3
sdf       8:80   0   3.7T  0 disk 
└─sdf1    8:81   0   3.7T  0 part 
  └─md3   9:3    0   7.3T  0 raid5 /raid3

blkid shows
/dev/sdd1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="24275237-b493-169e-9e88-df0debaae551" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-a" PARTUUID="729558f8-fbcf-45c1-9d9b-c6bfe6ec4bf6"
/dev/sde1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="cf36e69a-c110-b0ae-b504-fcfeb2dea024" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-c" PARTUUID="654fc581-f6ef-43a4-b583-6f3cd7d52e61"
/dev/sdf1: UUID="07c3d55f-2c9b-1534-6b0d-5b78dd9856ed" UUID_SUB="54fbf294-766f-c8eb-9663-02a39534003f" LABEL="camelot-x:3" TYPE="linux_raid_member" PARTLABEL="cam-raid5-b" PARTUUID="f6a7ba77-278e-4b64-8f7e-16041b85f097"
and
/dev/md3: UUID="97309dc0-0f54-45d8-853f-af99dead3ed2" TYPE="ext4"

df -h shows
/dev/md3        7.3T   51M  7.3T   1% /raid3

QUESIONS:

So why is there still a /dev/md127, and why does the array not assemble as /dev/md3?
/etc/mdadm/mdadm.conf contains just the one array:
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
which is still what I get from
mdadm --detail --scan

mount and umount commands work as expected, both with my original /etc/fstab entry or with yours.  I'll leave yours in place and try a reboot....

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


SUCCESS.  Sort of.  It raises another question.

On reboot, I had /raid3.  But it is mounted on /dev/md127.  It appears the system is ignoring the device in my mdadm.conf entry.  Here it is again:
ARRAY /dev/md3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
And here's the output of mdadm --detail --scan
ARRAY /dev/md/camelot-x:3 metadata=1.2 name=camelot-x:3 UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

And indeed there is a /dev/camelot-x:3

Sorry, clicked before I got a chance to finish and make this a bottom-post.  Anyway, the above is a link to /dev/md127

So on startup, it's going to make its own choices of device...  And it then makes sense to use UUID in the /etc/fstab entry.

Yet another discrepancy with the docs I was using.

--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Liam Proven

On 4 April 2017 at 18:01, Kevin O'Gorman <[hidden email]> wrote:
Sorry, clicked before I got a chance to finish and make this a bottom-post.  Anyway, the above is a link to /dev/md127

Gmail bottom-posts just fine. Look, this is me doing it, in the web client.

Select the line you're replying to, hit Reply.

Suggestion:

Remove all traces of the RAID and its partitions.

Install Webmin.

Use Webmin's GUI to create it, format it, mount it, share it.

If desired, remove Webmin afterwards.



--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Liam Proven
In reply to this post by Rashkae-2
On 4 April 2017 at 15:50, Rashkae <[hidden email]> wrote:
> It looks like you've partitioned your RAID device itself.  I'm not too sure
> how that's supposed to look, as I've never set them up that way.
> (I partition the physical devices, as you've done, then create a raid array,
> and create my FS directly on that array.)


This is indeed the recommended way.

But as it is 2017 now, if it were me, I would not be using ext4 and
mdadm at all. I'd use ZFS, as it's in Ubuntu 16.04.


--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Rashkae-2
In reply to this post by Kevin O'Gorman
On 17-04-04 11:48 AM, Kevin O'Gorman wrote:

> QUESIONS:
>
> So why is there still a /dev/md127, and why does the array not assemble as
> /dev/md3?
> /etc/mdadm/mdadm.conf contains just the one array:
> ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
> UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed

This web page should have more details on how to manipulate the device
name of your array.

https://superuser.com/questions/346719/how-to-change-the-name-of-an-md-device-mdadm

I wouldn't sweat it though.  Device names tend to be pretty fluid these
days, for one reason or another.  Best to use UUID for finding filesystems.




--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Xen
Rashkae schreef op 04-04-2017 22:19:

> On 17-04-04 11:48 AM, Kevin O'Gorman wrote:
>
>> QUESIONS:
>>
>> So why is there still a /dev/md127, and why does the array not
>> assemble as
>> /dev/md3?
>> /etc/mdadm/mdadm.conf contains just the one array:
>> ARRAY /dev/md3 metadata=1.2 name=camelot-x:3
>> UUID=07c3d55f:2c9b1534:6b0d5b78:dd9856ed
>
> This web page should have more details on how to manipulate the device
> name of your array.
>
> https://superuser.com/questions/346719/how-to-change-the-name-of-an-md-device-mdadm
>
> I wouldn't sweat it though.  Device names tend to be pretty fluid
> these days, for one reason or another.  Best to use UUID for finding
> filesystems.

Personally I stay away from UUIDs and use filesystem labels instead (or
GPT partition labels if possible, but you wouldn't be able to use that
on a raid).

UUIDs lead to human error.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Rashkae-2
On 17-04-04 04:31 PM, Xen wrote:
> Rashkae schreef op 04-04-2017 22:19:

>
> Personally I stay away from UUIDs and use filesystem labels instead (or
> GPT partition labels if possible, but you wouldn't be able to use that
> on a raid).
>
> UUIDs lead to human error.
>

Copy/Paste.

Labels lead to human laziness.. (re-using labels, then forgetting to
check when moving disks/volumes between systems.)  But if you can avoid
that, they are a perfectly acceptable method to avoid device names.



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Xen
Rashkae schreef op 04-04-2017 22:39:

> On 17-04-04 04:31 PM, Xen wrote:
>> Rashkae schreef op 04-04-2017 22:19:
>
>>
>> Personally I stay away from UUIDs and use filesystem labels instead
>> (or
>> GPT partition labels if possible, but you wouldn't be able to use that
>> on a raid).
>>
>> UUIDs lead to human error.
>>
>
> Copy/Paste.

Not human error in copy/paste, but human error in not having a clue what
each UUID refers to in the end when you need to know this shit because
something stops working ;-).

> Labels lead to human laziness.. (re-using labels, then forgetting to
> check when moving disks/volumes between systems.)

I agree with that...

> But if you can
> avoid that, they are a perfectly acceptable method to avoid device
> names.

Yeah, but the worst thing that can usually happen is that you have 2
disks with the same label.

Apart from a short confusion that is easy enough to solve I guess.

At least, as long as systemd won't start to randomly mount/umount stuff
on a continuing basis because it gets confused as to the existence of
two labels... I seem to have a vague recollection of something ;-).
Anyway, bah.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Help, my RAID won't start

Xen
Xen schreef op 04-04-2017 22:45:

> At least, as long as systemd won't start to randomly mount/umount
> stuff on a continuing basis because it gets confused as to the
> existence of two labels... I seem to have a vague recollection of
> something ;-). Anyway, bah.

Oh yes, I had a Windows disk with a label on it ("Games") and a clone of
that on another disk.

I would have one of the two mounted and systemd would constantly umount
it and mount the other one. It was hell. In the end I removed it from
fstab so it wouldn't happen.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Loading...