NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Volume lost on ReadyNas 104
Hello, I lost my volume on a ReadyNas 104. No errors have been logged according to the admin page, only a bunch of warnings around April this year. See output in attachment. I have not done a...
Markuzz wrote:
See attachment for output 1 of 2.
This should assemble, so I am puzzled by the earlier issue.
The event counters (13922, 13917, 13926, 13917) do show some lost writes - they should all be 13926.
Maybe try this variation:
mdadm --assemble --really-force /dev/md127 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
Hi StephenB,
Many thanks for your reply.
I've copied the status.log with the warnings hereunder. I have not removed any disks in the last years.
The NAS is in X-Raid mode. Also I 'suddenly' noticed that the volume seems to be there, but inactive. See attachment.
I am familiar with ssh and the command line. So any help as to try to reconnect the volume via a terminal is highly appreciated!
Kind regards,
Mark
-- STATUS.LOG
[23/02/12 14:05:43 CET] warning:disk:LOGMSG_DELETE_DISK Disk Model:Hitachi HDS5C3030ALA630 Serial:MJ1311YNG6YY5A was removed from Channel 4 of the head unit.
[23/02/12 14:05:45 CET] warning:volume:LOGMSG_HEALTH_VOLUME Volume MusicDrive health changed from Redundant to Degraded.
[23/02/12 14:13:21 CET] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[23/02/12 14:13:26 CET] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Degraded.
[23/02/12 14:13:26 CET] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[23/02/12 14:13:34 CET] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/02/12 14:13:38 CET] warning:system:LOGMSG_BOND_NETWORK_SLAVE_NIC_DOWN Bond interface bond0 has slave interface eth1 offline.
[23/02/12 14:13:53 CET] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume MusicDrive.
[23/02/12 14:14:36 CET] warning:volume:LOGMSG_READYTIER_REPLACE_MIXED_DISK It is not recommended to mix different disk types. Current volume is using SATA 7200 RPM drives. Please replace the disk in channel 4 (Internal) to match the rest of the disks on volume MusicDrive for best performance.
[23/02/12 15:32:39 CET] warning:volume:LOGMSG_READYTIER_REPLACE_MIXED_DISK It is not recommended to mix different disk types. Current volume is using SATA 7200 RPM drives. Please replace the disk in channel 4 (Internal) to match the rest of the disks on volume MusicDrive for best performance.
[23/02/13 01:00:54 CET] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Degraded.
[23/02/14 01:00:28 CET] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Degraded.
[23/02/15 01:00:28 CET] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Degraded.
[23/02/15 13:03:33 CET] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume MusicDrive is resynced.
[23/02/15 13:03:34 CET] notice:volume:LOGMSG_HEALTH_VOLUME Volume MusicDrive health changed from Degraded to Redundant.
[23/02/15 13:03:34 CET] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE.
[23/02/16 08:18:35 CET] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
[23/03/16 08:20:45 CET] warning:disk:LOGMSG_SMART_SPIN_RETRY_WARN Detected high spin retry count: [131073] on disk 2 (Internal) [TOSHIBA DT01ACA300, Y3RDZRKGS]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.
[23/03/16 08:20:48 CET] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/03/16 08:20:45 CET] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[23/03/16 08:21:03 CET] warning:system:LOGMSG_BOND_NETWORK_SLAVE_NIC_DOWN Bond interface bond0 has slave interface eth1 offline.
[23/03/16 11:46:49 CET] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
[23/04/16 12:48:51 CEST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/04/16 12:49:00 CEST] warning:system:LOGMSG_BOND_NETWORK_SLAVE_NIC_DOWN Bond interface bond0 has slave interface eth1 offline.
[23/04/16 12:49:00 CEST] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[23/04/17 08:16:48 CEST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[23/04/17 08:16:53 CEST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/04/17 08:17:01 CEST] warning:system:LOGMSG_BOND_NETWORK_SLAVE_NIC_DOWN Bond interface bond0 has slave interface eth1 offline.
[23/04/17 08:17:01 CEST] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[23/04/20 00:33:07 CEST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[23/04/20 00:33:13 CEST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/04/20 00:33:21 CEST] warning:system:LOGMSG_BOND_NETWORK_SLAVE_NIC_DOWN Bond interface bond0 has slave interface eth1 offline.
[23/04/20 00:33:21 CEST] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[23/04/20 00:49:25 CEST] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F47LTW was removed from Channel 1 of the head unit.
[23/04/20 00:49:25 CEST] warning:volume:LOGMSG_HEALTH_VOLUME Volume MusicDrive health changed from Redundant to Dead.
[23/04/20 00:49:27 CEST] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F4C9PX was removed from Channel 3 of the head unit.
[23/04/20 00:49:29 CEST] notice:disk:LOGMSG_ADD_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F47LTW was added to Channel 1 of the head unit.
[23/04/20 00:49:36 CEST] notice:disk:LOGMSG_ADD_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F4C9PX was added to Channel 3 of the head unit.
[23/04/20 00:51:11 CEST] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 1 (Internal) changed state from RESYNC to ONLINE.
[23/04/20 00:52:55 CEST] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 3 (Internal) changed state from RESYNC to ONLINE.
[23/04/20 01:00:28 CEST] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Dead.
[23/04/20 01:13:18 CEST] warning:disk:LOGMSG_SMART_SPIN_RETRY_WARN Detected high spin retry count: [327682] on disk 4 (Internal) [Hitachi HDS5C3030ALA630, MJ1311YNG6YY5A]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.
[23/04/20 01:15:09 CEST] warning:disk:LOGMSG_DELETE_DISK Disk Model:Hitachi HDS5C3030ALA630 Serial:MJ1311YNG6YY5A was removed from Channel 4 of the head unit.
[23/04/20 01:15:21 CEST] warning:disk:LOGMSG_SMART_SPIN_RETRY_WARN Detected high spin retry count: [1245187] on disk 2 (Internal) [TOSHIBA DT01ACA300, Y3RDZRKGS]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.
[23/04/20 05:34:22 CEST] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
Markuzz wrote:
The NAS is in X-Raid mode. Also I 'suddenly' noticed that the volume seems to be there, but inactive. See attachment.
[23/04/20 01:00:28 CEST] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume MusicDrive is Dead.
A little odd, since the volume name for X-RAID is always "data", and yours is "MusicDrive". So you must have started out in FlexRAID, and then switched before you did any expansion.
Markuzz wrote:
I am familiar with ssh and the command line. So any help as to try to reconnect the volume via a terminal is highly appreciated!
Is ssh enabled on the NAS? If it isn't then you'll need to boot into tech support mode and connect with telnet. We can give more detailed instructions if needed.
Given the dicey situation with the disks, I'd begin with running full non-destructive tests with smartctl, and then attempt to assemble/remount the volume. If successful, I strongly recommend that you back up the data before doing anything else.
Your problem may be power related -- not enough to spin the drives up properly. It could be the power brick or something internal to the NAS.
The best next step is to test the two "bad" drives in a PC with the drive vendor's tools. If they actually pass (except for the existing SMART errors), then that adds evidence that that is the issue.
BTW, you have your alert email set up wrong, which is why you didn't get any email warnings about this.
Hi StephenB ,
SSH is enabled on the NAS.
"Given the dicey situation with the disks, I'd begin with running full non-destructive tests with smartctl, and then attempt to assemble/remount the volume. If successful, I strongly recommend that you back up the data before doing anything else."
Could you please provide me with the correct commands? I am not familiar with these. I also may need the standard ssh login credentials 🙂
Cheers! Mark.
Ignore the credentials..... found the admin user to login via ssh 🙂
Markuzz wrote:
Ignore the credentials..... found the admin user to login via ssh 🙂
Use root as the username for this, using the NAS admin password.
For disk testing
smartctl -t long /dev/sdXwhere sdX is the disk you want to test. (Normally sda, sdb, sdc, or sdd).
You need to look back later to see the status.
smartctl -c /dev/sdX | grep executionwill let you see if the test is still in progress
smartctl -a /dev/sdX | grep offlinewill give you the test history (most recent test first).
You can attempt to forcibly assemble the volume useing
mdadm --assemble --scan --really-force /dev/md127If this works, you can attempt to mount the volume
btrfs device scan mount -o ro /dev/md127 /MusicDriveThe -o ro mounts it as read-only (which I think is the right thing to do intially). If you want to go directly to read/write, then leave that out.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
