October 7, 20169 yr Hi, I've test driven unRAID 6.2 for two weeks and find it's amazing, so I've just bought my Pro license. I had a small issue while trying to expand my array: I wanted to rearrange the disk order and to add a new disk at the same time. So I moved an array disk from slot 9 to slot 10, then put a new disk into slot 9, when I restarted, the array disk in slot 10 is now marked as 'unmountable', the new disk (in slot 9) was detected correctly though and clearing in progress. So I put the array disk back into slot 9, and put the new disk into slot 10, now everything's fine. Is this a feature or a bug?
October 7, 20169 yr Author All disks are formatted as xfs. Attached is the diag info. unraid-48t-diagnostics-20161007-1920.zip
October 7, 20169 yr All disks are formatted as xfs. Attached is the diag info. Its because of this: Oct 7 19:14:33 unRAID-48T kernel: XFS (md6): Filesystem has duplicate UUID 92d7744c-ae83-4670-b844-7f4d7796722a - can't mount That happens when rearranging the disks.
October 7, 20169 yr Author All disks are formatted as xfs. Attached is the diag info. Its because of this: Oct 7 19:14:33 unRAID-48T kernel: XFS (md6): Filesystem has duplicate UUID 92d7744c-ae83-4670-b844-7f4d7796722a - can't mount That happens when rearranging the disks. Well, AFAIK, unRAID can detect disk rearrangement, I actually tested this by several times before purchasing my pro license. Why did it not work when I added a new disk? Sent from my iPad using Tapatalk
October 7, 20169 yr Disk rearrangement won't cause a duplicate UUID, something else happened. Was the new disk previously used in the array?
October 8, 20169 yr Author Disk rearrangement won't cause a duplicate UUID, something else happened. Was the new disk previously used in the array? Yeah, this reminded me that I did add the new disk into array earlier (into the empty slot 10), while the clearing process started, I somehow decided to stop it, and then swapped the disk in slot 9 with the disk in slot 10. When I started the array again, the 'unmountable' thing happened. Is it possible the cancelled clearing process the cause of unmountable issue ?
Archived
This topic is now archived and is closed to further replies.