mason1171 Posted March 21, 2020 Share Posted March 21, 2020 (edited) My boot device failed today. I had to to restore an 2 month old boot backup to another usb drive so i could spin up my drives. I was foolishly storing my boot backups on the array. I then copied the config folder from a 7 day old backup to the new drive. After rebooting, my nas has lost the drive assignments. How would I go about using the info below to reassign the drives and fix this issue without losing data? Can someone please help me? Disk Assignments Disk: parity Device: WDC_WD80EMAZ-00WJTA0_7HK36D3N Status: DISK_OK Disk: disk1 Device: WDC_WD80EMAZ-00WJTA0_7HJV9A0F Status: DISK_OK Disk: disk2 Device: WDC_WD40EZRZ-22GXCB0_WD-WCC7K7HHHACN Status: DISK_OK Disk: parity2 Device: Status: DISK_NP_DSBL Disk: cache Device: Samsung_SSD_860_EVO_500GB_S598NE0MB07921E Status: DISK_OK Disk: cache2 Device: HP_SSD_EX900_500GB_HBSE39260100698 Status: DISK_OK Disk: flash Device: Cruzer_Fit Status: DISK_OK The HP drive is no longer relevant. It was removed between the backup and now. Edited March 21, 2020 by mason1171 Formatting fix Quote Link to comment
Squid Posted March 21, 2020 Share Posted March 21, 2020 Tools - New Config. Then from the Main Tab, assign the drives accordingly. Because you had a cache pool I'm not 100% sure of the ramifications of not assigning the second cache drive, but will say that if ANYTHING comes up as unmountable when you go to start the array to stop whatever you're doing and ask for help here. Quote Link to comment
mason1171 Posted March 21, 2020 Author Share Posted March 21, 2020 Thank you so much. I will try this right now. Quote Link to comment
mason1171 Posted March 21, 2020 Author Share Posted March 21, 2020 Squid, I feel like there's a problem. Will I lose the whole array or just the parity and have to rebuild? Quote Link to comment
trurl Posted March 21, 2020 Share Posted March 21, 2020 New Config will only (optionally) rebuild parity. If you think parity is already valid then you can check a box when you go to start the array telling it parity is valid and it won't even rebuild parity. No other disk will be changed in any case. The reason for the warning is because if someone has a data disk that needs to be rebuilt, then doing New Config makes it forget that data disk needs to be rebuilt. The main danger from New Config is accidentally assigning a data disk to the parity slot, thus overwriting that data with parity. 1 Quote Link to comment
mason1171 Posted March 21, 2020 Author Share Posted March 21, 2020 So you are saying as long as I assign the drives correctly, no data will be lost? Quote Link to comment
trurl Posted March 21, 2020 Share Posted March 21, 2020 yes, but 1 hour ago, Squid said: Because you had a cache pool I'm not 100% sure of the ramifications of not assigning the second cache drive, but will say that if ANYTHING comes up as unmountable when you go to start the array to stop whatever you're doing and ask for help here. Quote Link to comment
trurl Posted March 21, 2020 Share Posted March 21, 2020 Do you know how your cache pool was configured? Quote Link to comment
mason1171 Posted March 21, 2020 Author Share Posted March 21, 2020 Yes, but I no longer have the drive. If my cache is compromised, i have backups of appdata. I guess I would lose the docker.img file but I don’t think that’s a real problem. Please correct me if Im wrong. Quote Link to comment
mason1171 Posted March 21, 2020 Author Share Posted March 21, 2020 I pulled the trigger and spun up the server. No data has been lost including the cache. Thanks guys. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.