MatzeHali Posted January 2, 2022 Share Posted January 2, 2022 Hi guys and gals, I've have the situation that I have a 5 data, 2 parity disk UNRAID configuration, and one data disk had been not working, so I took a fresh disk, precleared it, then stopped the array, replaced the faulty disk with the newly precleared one, started the array again and it started to rebuild. Now the rebuild has finished and it shows valid parity, but the disk in question is shown as unmountable. As far as I can say, the array is not missing any data, and I can access everything. So, is that disk not used in the array, now, and is simulated? How is that possible after a rebuild? What would be my next step to make sure that everything is actually in order? Thanks, M Quote Link to comment
Squid Posted January 2, 2022 Share Posted January 2, 2022 Post your diagnostics Quote Link to comment
MatzeHali Posted January 2, 2022 Author Share Posted January 2, 2022 Hi, yes of course. Totally wanted to attach it before, but forgot. :D mhions-storage-diagnostics-20220102-1656.zip Quote Link to comment
Squid Posted January 2, 2022 Share Posted January 2, 2022 Nothing relevant in the logs as it's nothing but Jan 1 22:24:16 mhions-storage smbd[16660]: [2022/01/01 22:24:16.254604, 0] ../../source3/lib/sysquotas.c:565(sys_get_quota) Jan 1 22:24:16 mhions-storage smbd[16660]: sys_path_to_bdev() failed for path [.]! over and over (and over) again. Not sure what that's about. But, so far as the disk is concerned, run the check filesystem against it 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.