Help, my RAID won't start
Kevin O'Gorman
kogorman at gmail.com
Tue Apr 4 04:17:16 UTC 2017
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170403/e3d6edbf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 441 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170403/e3d6edbf/attachment.gif>
More information about the ubuntu-users
mailing list