I inherited a ReadyNAS 104 from my office that I have been using as a Plex Media Server. It was working fine last night but we have a bad storm and I think we have had a few power surges over night and I am now having issues with the server.
I am getting an error that says "Remove inactive volumes to use the disk. Disk #1,2,3,4. I have tried:
Rrebooting the server.
Turning the server off, unplugging it from the power soruce, letting it sit for a couple hours, reseating the drives, then rebooting
Logs below. Any help would be appreciated.
[21/10/23 00:00:04 PDT] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1634972402 was successfully created for share or LUN readydrop. [21/10/24 00:00:13 PDT] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1635058812 was successfully created for share or LUN readydrop. [21/10/24 00:56:53 PDT] info:snapshot:LOGMSG_SMART_SNAPSHOT_DELETE_INFO Snapshot prune worker successfully deleted snapshot 2021_09_26__00_00_19 from share or LUN readydrop. [21/10/24 04:48:21 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000DM003-1ER162 Serial:Z4Y1Q64N was removed from Channel 1 of the head unit. [21/10/24 04:48:21 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000DM003-1ER162 Serial:Z4Y0FNB6 was removed from Channel 3 of the head unit. [21/10/24 04:48:25 PDT] warning:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Dead. [21/10/24 04:49:31 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was removed from Channel 4 of the head unit. [21/10/24 05:01:01 PDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was added to Channel 4 of the head unit. [21/10/24 05:02:39 PDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE. [21/10/24 05:12:01 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was removed from Channel 4 of the head unit. [21/10/24 05:16:48 PDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was added to Channel 4 of the head unit. [21/10/24 05:18:29 PDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE. [21/10/24 05:19:09 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was removed from Channel 4 of the head unit. [21/10/24 05:25:11 PDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST1000DM003-1ER162 Serial:Z4Y0FNB6 was added to Channel 3 of the head unit. [21/10/24 05:25:54 PDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was added to Channel 4 of the head unit. [21/10/24 05:28:26 PDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE. [21/10/24 05:51:05 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000NM0033-9ZM173 Serial:Z1W617PR was removed from Channel 4 of the head unit. [21/10/24 09:03:41 PDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted. [21/10/24 09:03:49 PDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. [21/10/24 09:07:21 PDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE. [21/10/24 09:11:01 PDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down. [21/10/24 09:44:02 PDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. [21/10/24 13:05:17 PDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down. [21/10/24 16:33:44 PDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[21/10/24 04:48:21 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000DM003-1ER162 Serial:Z4Y1Q64N was removed from Channel 1 of the head unit. [21/10/24 04:48:21 PDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST1000DM003-1ER162 Serial:Z4Y0FNB6 was removed from Channel 3 of the head unit. [21/10/24 04:48:25 PDT] warning:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Dead.
This appears to have done the damage, though there appear to be a lot of similar remove/add errors on disk 4. Nothing suggesting that disk 1 was re-added.
The only time I removed/reinserted drives was when it was totally powered off. I just removed and reseated them. It had been turned off and unplugged from power for a few hours at that point.
Those errors show up around 5am. I was sleeping at the time but I think we had a weather related power surge around then, although the server is plugged into a surge protector but I can't think of what else it would be. It was working fine when I went to sleep and was not working the next day.
ReclaiMe could probably recover all the data, but it would be expensive (and you'd need a way to connect all the drives to a Windows PC).
It's also possible that you could forcibly mount the data volume in the NA - that would require reasonable knowledge of the linux command line. There's no definitive guide, so it is difficult to help in the forum. Still, @rn_enthusiast has taken it on from time to time, so if you want to pursue that, you might try sending him a private message (PM) using the envelope link in the upper right of the forum page.
If that's more work than the data is worth, then the next step is to try and verify that the chassis and disks weren't damaged by whatever happened. I'd do a factory default with just one disk inserted, and then make sure the system works with that disk in each bay (running it for a couple of hours in bay 4, which seems to be misbehaving more than the others).
I'd also test the disks in a Windows PC with vendor tools - Seatools for Seagate, Lifeguard or Dashboard for Western Digital. I'd run the long diagnostic at least, and perhaps follow up with the full erase.
If all looks good, then try factory default with all disks in place.
Those errors show up around 5am. I was sleeping at the time but I think we had a weather related power surge around then, although the server is plugged into a surge protector but I can't think of what else it would be.
I'd expect to see the NAS reboot if the power failed even briefly - but we are not seeing that in your logs. So the cause is a bit of a mystery. The full log zip might have some more info, so perhaps download it before starting over.
FWIW, I always suggest getting a UPS for NAS. Then if the power fails, the NAS will shut down gracefully.
Though I'd suggest that you consider putting a backup plan in place for the NAS (likely using USB drives). That's a higher priority for me than UPS protection.
It sounds like you had some brown outs and/or multiple intermittent power losses, which are never a good thing with computers not protected by an UPS. Shutting down again during a power-up can result in corrupted volumes, which is hopefully all you have (though that's still a pretty unpleasant situation). @StephenB has given you the best path forward. If testing the chassis seems to indicate it's at least a part of the problem, there is the possibility that it's the power brick. The only way to really tell, though, is to try another one.
If that's more work than the data is worth, then the next step is to try and verify that the chassis and disks weren't damaged by whatever happened. I'd do a factory default with just one disk inserted, and then make sure the system works with that disk in each bay (running it for a couple of hours in bay 4, which seems to be misbehaving more than the others).
Finally getting back to this.To do this I need to basically remove all drives except 1 and perform the factory reset? When I move the drive to a new bay do I perform the reset again or just shut down the server and move the drive?
I am not too concern on the data. I have everything it was just file renaming I will loose.
@VVitch wrote: >Finally getting back to this.To do this I need to basically remove all drives except 1 and perform the factory reset? When I move the drive to a new bay do I perform the reset again or just shut down the server and move the drive?
Do the reset with one disk installed. Then power down and move the drive, so you test all slots. No need to do the reset each time.
