April 3, 20251 yr Had a drive start spitting errors (sdj1) -- I was following the process to remove it but in the process I also changed the # of slots from 7 to 6. There was another unassigned device in the pool but it hasn't been there for 6-months so I had assumed it had already resilvered itself? Not sure. Diagnostics is attached. Here's my zpool import after a reboot: pool: tcache id: 7798822708951295056 state: DEGRADED status: One or more devices are offlined. action: The pool can be imported despite missing or damaged devices. The fault tolerance of the pool may be compromised if imported. config: tcache DEGRADED raidz1-0 DEGRADED sdl1 ONLINE sdj1 ONLINE sdm1 ONLINE sdo1 ONLINE sdn1 ONLINE sdk1 ONLINE 15645856880541475232 OFFLINE pool: shorty id: 2699110156999791362 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: shorty ONLINE raidz1-0 ONLINE sdb1 ONLINE sdc1 ONLINE sdf1 ONLINE sdg1 ONLINE hippo-diagnostics-20250403-0026.zip Edited April 3, 20251 yr by Fffrank
April 3, 20251 yr Community Expert Reimport the pool degraded and post new diags: on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and 6 slots assign the remaining pool devices, leave the filesystem set to auto start the array to import the pool
April 3, 20251 yr Author 26 minutes ago, JorgeB said: Reimport the pool degraded and post new diags: on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and 6 slots assign the remaining pool devices, leave the filesystem set to auto start the array to import the pool Pool reimported and now I see a 7th unassigned device there...... new diag attached. hippo-diagnostics-20250403-0026.zip
April 3, 20251 yr Author 4 hours ago, JorgeB said: Diags with array started, please. Sorry - attached the wrong file. Here you go! hippo-diagnostics-20250403-0902.zip
April 3, 20251 yr Community Expert You should now be able to assign a device to the empty slot to start a resilver, but note that the pool is detecting data errors, you should check that out when the resilver is done: zpool status -v tcache
April 3, 20251 yr Author 8 minutes ago, JorgeB said: You should now be able to assign a device to the empty slot to start a resilver, but note that the pool is detecting data errors, you should check that out when the resilver is done: zpool status -v tcache I'm trying to remove the drive that is failing (sdj1) altogether. It's an old scsi drive and I don't have another to slot in.
April 3, 20251 yr Community Expert Do you mean you want to remove that device from the pool? You cannot remove devices from a zfs raidz pool, you can replace it, or leave the pool degraded, of course, if another device fails while degraded the pool will be lost
April 3, 20251 yr Author 1 minute ago, JorgeB said: Do you mean you want to remove that device from the pool? You cannot remove devices from a zfs raidz pool, you can replace it, or leave the pool degraded, of course, if another device fails while degraded the pool will be lost Yes. I thought I could always remove a single device (in the event of failure) and then the pool would rebuild. In this instance do I need to move all data off this array, erase and then build a new array without this drive included?
April 3, 20251 yr Community Expert Solution 19 minutes ago, Fffrank said: In this instance do I need to move all data off this array, erase and then build a new array without this drive included? Correct.
April 3, 20251 yr Author 46 minutes ago, JorgeB said: Correct. Thanks. I'm working on that now. Any ideas why I'm not seeing any errors reported on the main screen? My log is full of critical medium errors and the SMART data is not looking good at all.
April 3, 20251 yr Community Expert Pools are not monitored on the GUI, see: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582
April 3, 20251 yr Author 5 minutes ago, JorgeB said: Pools are not monitored on the GUI, see: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582 Well that's a kick in the shorts! Bizarre to me that it's reporting errors in the GUI via the Scrub status but not rolling that back to the main page. I'm sure it will be an improvement in the future. Thanks for your help!
April 3, 20251 yr Community Expert 37 minutes ago, Fffrank said: I'm sure it will be an improvement in the future. Me too, I've been asking for that since 2016.
April 4, 20251 yr Author Just to close the loop in case anyone else ends up here. I was able to identify that I had a VM image that was corrupt and would not successfully copy off of the pool. I used ddrescue to copy it to a temporary dir on another array and it was able to fire up the VM and I used chkdsk inside of windows to repair it. I don't suspect I lost any data (and it probably explains why I've been having VM instability.) Erased and removed the pool, added a new pool with 5 slots instead of 6 and physically removed the failing drive. Array started back up without issues and errors are gone.
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.