<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 30, 2015 at 12:52 AM, William Park <span dir="ltr"><<a href="mailto:opengeometry@yahoo.ca" target="_blank">opengeometry@yahoo.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Sat, Aug 29, 2015 at 10:34:24PM -0500, o1bigtenor wrote:<br>
> On Sat, Aug 29, 2015 at 9:30 PM, Lennart Sorensen <<br>
> <a href="mailto:lsorense@csclub.uwaterloo.ca">lsorense@csclub.uwaterloo.ca</a>> wrote:<br>
</span><span class="">> > What entry do you have for your raid stuff in /etc/fstab?<br>
</span>...<br>
<span class="">> nothing listed for md0 or md/0<br>
<br>
</span>You can always add it. But, if manual mounting doesn't work, then<br>
/etc/fstab won't work either.<br>
<span class=""><br>
> > And as already said, software raid does NOT use /dev/dm devices, it uses<br>
> > /dev/md devices. dm is for device mapper, which you will see if you use<br>
> > dmraid (which I think most people have fortunately stopped doing), or lvm<br>
> > (which many people are using) or encrypted disks (which some people use).<br>
> ><br>
> > What does fdisk -l /dev/md0 show? Did you partition the raid or is the<br>
> > filesystem on the full raid?<br>
> ><br>
><br>
><br>
> # fdisk -l /dev/md0<br>
> Disk /dev/md0: 1.8 TiB, 2000403038208 bytes, 3907037184 sectors<br>
> Units: sectors of 1 * 512 = 512 bytes<br>
> Sector size (logical/physical): 512 bytes / 4096 bytes<br>
> I/O size (minimum/optimal): 524288 bytes / 1048576 bytes<br>
> Disklabel type: gpt<br>
> Disk identifier: 1EB47793-0CDF-4E16-AE84-33EC825AC448<br>
<br>
</span><span class="">> sdb<br>
> ??????sdb1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3<br>
> ??????md0<br>
> sdc<br>
> ??????sdc1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3<br>
> ??????md0<br>
> sde<br>
> ??????sde1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3<br>
> ??????md0<br>
> sdf<br>
> ??????sdf1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3<br>
> ??????md0<br>
<br>
</span>There is no filesystem on /dev/md0. It seems that it has GPT table with<br>
no partitions. If you do<br>
gdisk -l /dev/md0<br>
you'll probably get similar result as 'fdisk -l'.<br></blockquote><div><br># gdisk -l /dev/md0<br>GPT fdisk (gdisk) version 1.0.0<br><br>Partition table scan:<br> MBR: protective<br> BSD: not present<br> APM: not present<br> GPT: present<br><br>Found valid GPT with protective MBR; using GPT.<br>Disk /dev/md0: 3907037184 sectors, 1.8 TiB<br>Logical sector size: 512 bytes<br>Disk identifier (GUID): 1EB47793-0CDF-4E16-AE84-33EC825AC448<br>Partition table holds up to 128 entries<br>First usable sector is 34, last usable sector is 3907037150<br>Partitions will be aligned on 2048-sector boundaries<br>Total free space is 3907037117 sectors (1.8 TiB)<br><br>Number Start (sector) End (sector) Size Code Name<br><br></div><div>What is very interesting is that <br><br># lsblk -f<br>NAME FSTYPE LABEL UUID MOUNTPOINT<br>sda <br>├─sda1 vfat 8642-E734 /boot/efi<br>├─sda2 <br>├─sda3 ext4 a3fbea19-5b7d-47af-b06c-08c49171211b /<br>├─sda4 swap 354a6e33-5743-4c97-bfb9-fd6f9d4521e6 [SWAP]<br>└─sda5 ext4 b36dbfc6-6897-4311-aa87-9a958ccad072 /home<br>sdb <br>└─sdb1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3 <br> └─md0 <br>sdc <br>└─sdc1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3 <br> └─md0 <br>sdd <br>├─sdd1 ext2 a0ce336b-35cd-4413-a1c7-e77a1a4e91a6 <br>├─sdd4 <br>├─sdd5 ext4 bbe77e50-0eaa-4048-934e-9f1b72b157ff <br>├─sdd6 ext4 533f504b-30a6-4cf6-86e9-56772c87bae3 <br>├─sdd7 ext4 ff6bcbe9-f25f-4738-ba6b-5ea3c2fe0b70 <br>├─sdd8 ext4 2d0d1953-dae6-4e33-8d04-cc685e2e36fb <br>├─sdd9 ext4 df754d9a-3dcf-470f-8e26-d38ef6f82df0 <br>└─sdd10 swap 04daef55-ff1b-4fe5-a897-ebe397a145b6 [SWAP]<br>sde <br>└─sde1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3 <br> └─md0 <br>sdf <br>└─sdf1 linux_raid_member debianbase:0 79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3 <br> └─md0 <br>sr0 <br><br><br></div><div>shows that I have two different identifiers for the array<br><br># blkid<br>/dev/sda1: UUID="8642-E734" TYPE="vfat" PARTUUID="50750607-76d9-49ea-9319-25b4dc3325f2"<br>/dev/sda2: PARTLABEL="/boot" PARTUUID="784e5c57-6df4-4942-9eef-99c2c707c6e2" <br>/dev/sda3: UUID="a3fbea19-5b7d-47af-b06c-08c49171211b" TYPE="ext4" PARTLABEL="/" PARTUUID="0c2154c4-ccf8-44a8-a80a-8b27d9dd1da8" <br>/dev/sda4: UUID="354a6e33-5743-4c97-bfb9-fd6f9d4521e6" TYPE="swap" PARTLABEL="swap" PARTUUID="58495d3d-e71a-4412-bc8d-99710c326e5c" <br>/dev/sda5: UUID="b36dbfc6-6897-4311-aa87-9a958ccad072" TYPE="ext4" PARTUUID="b321042f-127c-4a29-b3a4-89ac3291093f" <br>/dev/sdb1: UUID="79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3" UUID_SUB="a80c76db-eaea-61af-bcb9-cbbbac99e467" LABEL="debianbase:0" TYPE="linux_raid_member" PARTUUID="000e4ced-01" <br>/dev/md0: PTUUID="1eb47793-0cdf-4e16-ae84-33ec825ac448" PTTYPE="gpt" <br>/dev/sdc1: UUID="79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3" UUID_SUB="840fc99d-6f60-7ea8-9a4a-9b0aa965c85c" LABEL="debianbase:0" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="a79c809a-0333-41d7-918a-e340febddcf4" <br>/dev/sdd1: UUID="a0ce336b-35cd-4413-a1c7-e77a1a4e91a6" TYPE="ext2" PARTUUID="000c9868-01" <br>/dev/sdd5: UUID="bbe77e50-0eaa-4048-934e-9f1b72b157ff" TYPE="ext4" PARTUUID="000c9868-05" <br>/dev/sdd6: UUID="533f504b-30a6-4cf6-86e9-56772c87bae3" TYPE="ext4" PARTUUID="000c9868-06" <br>/dev/sdd7: UUID="ff6bcbe9-f25f-4738-ba6b-5ea3c2fe0b70" TYPE="ext4" PARTUUID="000c9868-07" <br>/dev/sdd8: UUID="2d0d1953-dae6-4e33-8d04-cc685e2e36fb" TYPE="ext4" PARTUUID="000c9868-08" <br>/dev/sdd9: UUID="df754d9a-3dcf-470f-8e26-d38ef6f82df0" TYPE="ext4" PARTUUID="000c9868-09" <br>/dev/sdd10: UUID="04daef55-ff1b-4fe5-a897-ebe397a145b6" TYPE="swap" PARTUUID="000c9868-0a"<br>/dev/sde1: UUID="79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3" UUID_SUB="cb37e722-d3a9-8f88-1343-9de2bdad9d2b" LABEL="debianbase:0" TYPE="linux_raid_member" PARTUUID="000dc7e1-01"<br>/dev/sdf1: UUID="79baaa2f-0aa2-b9fa-18e2-ea6b6e2846b3" UUID_SUB="9e749fa9-a0ef-e791-ea09-d2e272b99f6c" LABEL="debianbase:0" TYPE="linux_raid_member" PARTUUID="0002d71f-01"<br><br><br></div><div>here it is even not a UUID its a PTUUID<br><br></div><div>Not sure what that means.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
In that case, you have to follow through and create partitions on<br>
/dev/md0. This is similar to regular harddisk /dev/sda with empty MBR<br>
table, where you have to follow through and create partitions /dev/sda1,<br>
etc.<br>
<br></blockquote><div>It already has partitions. (Been running the array long enough to have disc failure.)<br><br></div><div>Talking you for your ideas and assistance.<br><br></div><div>Dee<br></div></div></div></div>