December 8, 20196 yr Yes, just do a Tools - New Config, and reassign the drives accordingly on the Main Tab
December 8, 20196 yr Author 1 minute ago, Squid said: Yes, just do a Tools - New Config, and reassign the drives accordingly on the Main Tab I just select Keep Data to keep my data?
December 8, 20196 yr New config doesn't actually do anything other than let you re-assign your drives. Your data will be safe on everything (except of course whatever you assign to the parity slot)
December 8, 20196 yr Author Just now, Squid said: New config doesn't actually do anything other than let you re-assign your drives. Your data will be safe on everything (except of course whatever you assign to the parity slot) I selected keep data last time and all my docker disappeared could that be cos it was stored on my cache? Edited December 8, 20196 yr by louij2 aaa
December 8, 20196 yr Author 1 hour ago, Squid said: If you didn't reassign your cache drive, then yeah that will happen. Hi it now says that the parity is invalid I added one 4TB drive do I need more and that my drives are unmountable and that I need to wipe them to add???
December 8, 20196 yr 8 minutes ago, louij2 said: Hi it now says that the parity is invalid Yeah, you didn't have a parity disk to begin with and since it hasn't been built yet from the data drives still remaining, then it is invalid. 9 minutes ago, louij2 said: that my drives are unmountable and that I need to wipe them to add??? Post a screen shot
December 8, 20196 yr Author Just now, Squid said: Yeah, you didn't have a parity disk to begin with and since it hasn't been built yet from the data drives still remaining, then it is invalid. Post a screen shot
December 8, 20196 yr Author Just now, Squid said: Post your diagnostics before you do anything tower-diagnostics-20191208-1653.zip
December 8, 20196 yr Dec 8 07:34:58 Tower kernel: XFS (md5): Filesystem has duplicate UUID a129fa57-6a2f-4e07-b89d-9c5a5c68e54a - can't mount Wait for @johnnie.black to look at this. Don't touch anything
December 8, 20196 yr Author 2 minutes ago, Squid said: Dec 8 07:34:58 Tower kernel: XFS (md5): Filesystem has duplicate UUID a129fa57-6a2f-4e07-b89d-9c5a5c68e54a - can't mount Wait for @johnnie.black to look at this. Don't touch anything Cheers
December 8, 20196 yr Author 2 hours ago, Squid said: Dec 8 07:34:58 Tower kernel: XFS (md5): Filesystem has duplicate UUID a129fa57-6a2f-4e07-b89d-9c5a5c68e54a - can't mount Wait for @johnnie.black to look at this. Don't touch anything Same post
December 8, 20196 yr Author Just now, louij2 said: Same post Can I backup files I need then just wipe everything? or should I follow that
December 8, 20196 yr Except that you didn't do a rebuild and then attempt to mount the old drive. You issued a new config, and every drive now thinks it has a duplicate UUID, and is now unmountable. Due to the potential of loss of data, I'm bowing out until the filesystem expert can have a gander at this and advise accordingly. A new config in and by itself should not make every disk unmountable.
December 8, 20196 yr Author 2 minutes ago, Squid said: Except that you didn't do a rebuild and then attempt to mount the old drive. You issued a new config, and every drive now thinks it has a duplicate UUID, and is now unmountable. Due to the potential of loss of data, I'm bowing out until the filesystem expert can have a gander at this and advise accordingly. A new config in and by itself should not make every disk unmountable. Okay thanks
December 8, 20196 yr Author 51 minutes ago, Squid said: Except that you didn't do a rebuild and then attempt to mount the old drive. You issued a new config, and every drive now thinks it has a duplicate UUID, and is now unmountable. Due to the potential of loss of data, I'm bowing out until the filesystem expert can have a gander at this and advise accordingly. A new config in and by itself should not make every disk unmountable. Can I just shut the NAS down?
December 9, 20196 yr Author 14 hours ago, Squid said: Sure. That won't make a difference either way. 3 hours ago, johnnie.black said: Rebooting should fix it, if it doesn't please post new diags. Thanks for your help I think it is Rebuilding parity now. Edited December 9, 20196 yr by louij2
Archived
This topic is now archived and is closed to further replies.