CLOSED: Disk Wizard using mount points more than once
Posted: Sun Nov 01, 2015 12:23 am
I am rebuilding my server after upgrading to Amahi 8. After a clean Amahi 8 install, the greyhole rebuild did not go well so I've been copying files from the old disks to the HDA. Due to capacity limitations, I have to do this a couple disks at a time. After two disks are copied, they get added to the HDA as additional storage.
I used the new Disk Wizard app to add the disks, but there seems to be a problem. The wizard mounted new disks to existing mount points. As a result I had two sdb1 and sdc1 drives. The drives already installed are 5TB, but now they show as 4TB with 100% free to match the new drives when they should be half full. The text below is my /etc/fstab/ file which shows clearly the duplicates.
#
# /etc/fstab
# Created by anaconda on Sat Oct 17 22:14:23 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0d0e9507-ceba-45f0-82d7-fa69cb1fbef6 / ext4 defaults 1 1
UUID=42e055e9-dda5-48cd-b6d7-123bf67c6552 /boot ext4 defaults 1 2
UUID=55c11082-8b70-472d-b4f4-3fbaeccbc2e3 swap swap defaults 0 0
UUID=d0e757b5-8971-4d1c-9e03-d380301f008c /var/hda/files/drives/disklz auto auto,rw,exec 0 0
UUID=6d1a051d-5b38-43af-8ec4-145314df2deb /var/hda/files/drives/sdb1 auto auto,rw,exec 0 0
UUID=df8dcaf6-16cf-4ad8-9fd3-b322d4174836 /var/hda/files/drives/sdc1 auto auto,rw,exec 0 0
UUID=bef849d5-7d7f-4e46-a159-d54b0f17fc9f /var/hda/files/drives/sdd1 auto auto,rw,exec 0 0
UUID=de0c31de-88c2-4ae1-a19b-cbb9603c397b /var/hda/files/drives/sdb1 auto auto,rw,exec 0 0
UUID=334650e5-9a0b-4d9e-9f98-bb4508eed006 /var/hda/files/drives/sdc1 auto auto,rw,exec 0 0
I have also attached a screenshot that shows the presence of multiple drives with the same location. Fortunately, since I am familiar with the old manual method of adding drives, I was able to solve the problem by editing the /etc/fstab/ file. I changed the mount points on the new drives to e & f, respectively. After I rebooted, the results inside amahi looked as they should.
It is fixable, but it seems this shouldn't have happened in the first place.
It seem this may be caused, at least in part, by the order that the hardware sees the drives. As you can see by the after screenshot below, the new drives at the top are tagged as partition sdb1 and sdc1. The disk wizard mounted these as sdb1 and sdc1 even though these mount points were already in use.
I used the new Disk Wizard app to add the disks, but there seems to be a problem. The wizard mounted new disks to existing mount points. As a result I had two sdb1 and sdc1 drives. The drives already installed are 5TB, but now they show as 4TB with 100% free to match the new drives when they should be half full. The text below is my /etc/fstab/ file which shows clearly the duplicates.
#
# /etc/fstab
# Created by anaconda on Sat Oct 17 22:14:23 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0d0e9507-ceba-45f0-82d7-fa69cb1fbef6 / ext4 defaults 1 1
UUID=42e055e9-dda5-48cd-b6d7-123bf67c6552 /boot ext4 defaults 1 2
UUID=55c11082-8b70-472d-b4f4-3fbaeccbc2e3 swap swap defaults 0 0
UUID=d0e757b5-8971-4d1c-9e03-d380301f008c /var/hda/files/drives/disklz auto auto,rw,exec 0 0
UUID=6d1a051d-5b38-43af-8ec4-145314df2deb /var/hda/files/drives/sdb1 auto auto,rw,exec 0 0
UUID=df8dcaf6-16cf-4ad8-9fd3-b322d4174836 /var/hda/files/drives/sdc1 auto auto,rw,exec 0 0
UUID=bef849d5-7d7f-4e46-a159-d54b0f17fc9f /var/hda/files/drives/sdd1 auto auto,rw,exec 0 0
UUID=de0c31de-88c2-4ae1-a19b-cbb9603c397b /var/hda/files/drives/sdb1 auto auto,rw,exec 0 0
UUID=334650e5-9a0b-4d9e-9f98-bb4508eed006 /var/hda/files/drives/sdc1 auto auto,rw,exec 0 0
I have also attached a screenshot that shows the presence of multiple drives with the same location. Fortunately, since I am familiar with the old manual method of adding drives, I was able to solve the problem by editing the /etc/fstab/ file. I changed the mount points on the new drives to e & f, respectively. After I rebooted, the results inside amahi looked as they should.
It is fixable, but it seems this shouldn't have happened in the first place.
It seem this may be caused, at least in part, by the order that the hardware sees the drives. As you can see by the after screenshot below, the new drives at the top are tagged as partition sdb1 and sdc1. The disk wizard mounted these as sdb1 and sdc1 even though these mount points were already in use.