July 8Jul 8 I have a zfs raidz1 pool with 3x6TB drives. I shut the server down. I removed one drive that had bad sectors. Right before I clicked Start Array, I got to the three boxes in the UI that showed two drives and an empty space, and I added the new drive there. I clicked Start Array. After the array started, I saw a message that the array was in a degraded state and it started rebuilding. After the rebuilding was completed, instead of working normally, it showed the message:status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J.I tried to run the following commands:root@Olympus:~# zpool status -v nervpool: nervstate: DEGRADEDstatus: One or more devices could not be used because the label is missing orinvalid. Sufficient replicas exist for the pool to continuefunctioning in a degraded state.action: Replace the device using 'zpool replace'.see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4Jscan: resilvered 1.21T in 02:05:50 with 0 errors on Wed Jul 8 15:57:37 2026config:NAME STATE READ WRITE CKSUMnerv DEGRADED 0 0 0raidz1-0 DEGRADED 0 0 022961051357565640 FAULTED 0 0 0 was /dev/sdd1sdd1 ONLINE 0 0 0sdf ONLINE 0 0 0errors: No known data errorsroot@Olympus:~# zpool detach nerv 22961051357565640cannot detach 22961051357565640: only applicable to mirror and replacing vdevsFor more information, look at the images and the diagnostics.What caused this problem? And how can I fix it without losing my data? Everything else seems to be working normally.The same thing happened the last time I tried to replace a drive. Back then, I thought it could be a weird software glitch, so I restarted the server. When I tried to start the pools, I got an error that said "nerv is in an invalid pool configuration". I tried to delete that pool and make it again, but every time I added the three drives, the same error appeared. That time I had a spare drive to dump all my data and format, but now I don't have this luxury. olympus-diagnostics-20260708-1646.zip
July 8Jul 8 Community Expert There's a known bug with 7.3.0 and zfs replacements, upgrade to 7.3.1 and try again.You may need to reimport the pool degraded first; I can post the steps if needed.
July 8Jul 8 Author Just now, JorgeB said:There's a known bug with 7.3.0 and zfs replacements, upgrade to 7.3.1 and try again.You may need to reimport the pool degraded first; I can post the steps if needed.I would really appreciate it if you could post the steps, please.
July 8Jul 8 Community Expert Solution Fist updatye to 7.3.1, then 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 2 slotsassign the pool device good pool devices from zfs status (look at the device IDs, sdd and sdf, no the previous assignments, and if you rebooted, these ids can change), leave the filesystem set to autostart the array to import the pool, it should be imported degradedIf yes, you can then stop the array and assign the new device.
July 8Jul 8 Author 3 hours ago, JorgeB said:Fist updatye to 7.3.1, thenon 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 2 slotsassign the pool device good pool devices from zfs status (look at the device IDs, sdd and sdf, no the previous assignments, and if you rebooted, these ids can change), leave the filesystem set to autostart the array to import the pool, it should be imported degradedIf yes, you can then stop the array and assign the new device.Thank you so much, it worked.
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.