pthartung Posted January 29, 2021 Share Posted January 29, 2021 Hello, I recently upgraded my parity drive. When I brought the server online Disk 4 was unmountable. The parity drive has already finished rebuilding. I am attempting xfs_repair. If it can't repair, how viable is the parity disk? Can I put my old parity disk back in and attempt to rebuild the data on the bad disk? Thank you for any suggestions Quote Link to comment
JorgeB Posted January 29, 2021 Share Posted January 29, 2021 Were there any errors during the rebuild? Please post the diagnostics, ideally before rebooting: Tools -> Diagnostics Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 I might has messed this up before I really even realized there was a problem. I did stop and start the array several times. I don't remember any errors during the rebuild. syslog.txt Quote Link to comment
trurl Posted January 29, 2021 Share Posted January 29, 2021 That is not the diagnostics. 12 minutes ago, JorgeB said: Tools -> Diagnostics Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 I went to Tools -> Diagnostics. It goes me the option to download. Am I doing something wrong? Quote Link to comment
itimpi Posted January 29, 2021 Share Posted January 29, 2021 Under the bit shown in your screenshot there should be a Download button that will give you a zip file that can then be uploaded to the forum. Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 Oh, I pulled out the syslog.txt. Sorry, here is the whole zip file. plex-unraid-diagnostics-20210129-1323.zip Quote Link to comment
trurl Posted January 29, 2021 Share Posted January 29, 2021 39 minutes ago, pthartung said: I am attempting xfs_repair. What exactly, if anything, have you done with this? Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 I got bad primary superblock bad magic number. I read a post that suggested running with the /L switch. That is running now. Quote Link to comment
trurl Posted January 29, 2021 Share Posted January 29, 2021 Jan 29 09:43:42 Plex-UnRaid ool www[2169]: /usr/local/emhttp/plugins/dynamix/scripts/xfs_check 'start' '/dev/md4' 'ST4000DM000-1F2168_W3002Y0K' '-L' Be sure to capture the output so you can post it. Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 I didn't run it verbose. Should I stop and start over? Quote Link to comment
JorgeB Posted January 29, 2021 Share Posted January 29, 2021 See if the actual disk4 mounts with the UD plugin, you'll need to unassign it first and best to use the read-only mount option. Quote Link to comment
pthartung Posted January 29, 2021 Author Share Posted January 29, 2021 xfs_check has been running since roughly 9:45 am. Should I stop that to try the mount? It's just sitting. Doesn't look like it is doing anything. Quote Link to comment
JorgeB Posted January 30, 2021 Share Posted January 30, 2021 If it didn't find a secondary superblock and there's no progress you can stop. Quote Link to comment
pthartung Posted January 30, 2021 Author Share Posted January 30, 2021 There was no output from XFS_Check. Just a bunch of dots on the screen. The disk will mount with UD, and I can click the drive and see contents, but mount points made in UD will not mount. Quote Link to comment
JorgeB Posted January 30, 2021 Share Posted January 30, 2021 If the disk mounts with UD and contents look correct you can do a new config with it and re-sync parity. Quote Link to comment
pthartung Posted January 30, 2021 Author Share Posted January 30, 2021 How do I do a new config? When ever I assign the device to disk 4 it tells me there is no file system. Quote Link to comment
JorgeB Posted January 30, 2021 Share Posted January 30, 2021 1 minute ago, pthartung said: When ever I assign the device to disk 4 it tells me there is no file system. Careful with this, if you rebuild on top of the old disk it will delete the existing data, depending on what exactly you're doing. Quote Link to comment
pthartung Posted January 30, 2021 Author Share Posted January 30, 2021 I am assigning the drive back to the same disk assignment, and starting in maintenance mode. The drive still comes up with a red x. Quote Link to comment
JorgeB Posted January 30, 2021 Share Posted January 30, 2021 If you started the array without it and then re-assign it and start in normal mode it will overwrite that drive, so don't do that. Quote Link to comment
JorgeB Posted January 30, 2021 Share Posted January 30, 2021 New config is under Tools, select keep all assignments, re-assign that disk if needed, all disks should be in their original assignments, then start array to begin the parity sync, all disks should mount immediately and all the data be available. Quote Link to comment
pthartung Posted January 30, 2021 Author Share Posted January 30, 2021 I have never started the array without it. When I mounted it with UD, the array was offline. Quote Link to comment
pthartung Posted January 30, 2021 Author Share Posted January 30, 2021 Wow! Thanks. All disks are online and the parity is syncing. 1 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.