ReadyNAS 426 stuck on booting..

Question

HI,after axpanding a disk the rebuild was hanging on 0,28%. Now my readynas wont boot in normal mode.If i boot in read only the log says that the firmware was upgraded. I cannot remind giving the command to do that on the same moment.&nbsp;What can I do? I stil can boot in readonly access. Normal boot gives a&nbsp;systemd-udev-settle.service when i press the power button.&nbsp;&nbsp;Oct 29, 2021 20:10:53&nbsp;System: ReadyNASOS background service started.Oct 29, 2021 20:01:28&nbsp;System: The system is shutting down.Oct 29, 2021 19:59:24&nbsp;System: ReadyNASOS background service started.Oct 29, 2021 19:59:24&nbsp;System: Firmware was upgraded to 6.10.5.Oct 29, 2021 18:41:59&nbsp;System: The system is rebooting.Oct 29, 2021 17:02:56&nbsp;Disk: Disk in channel 3 (Internal) changed state from RESYNC to ONLINE.Oct 29, 2021 16:59:34&nbsp;Volume: Resyncing started for Volume data.Oct 29, 2021 16:59:27&nbsp;Disk: Disk Model:WDC WD60EFZX-68B3FN0 Serial:WD-C814B1SG was added to Channel 3 of the head unit.

Supercows · Answer

Radair:&nbsp;Successfully completed diagnosticsSystemDisk 2 has 52 Reallocated SectorsDisk 2 has 32 Reallocation EventsDisk 2 has 3 Current Pending SectorsVolume data is inactiveVolume data-0 is inactiveLogs2021-10-29 20:10:35: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 20:03:14: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:59:03: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:54:27: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:46:44: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:37:18: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:27:00: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:12:53: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:09:24: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 22021-10-29 19:05:14: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2

StephenB · Answer

Not sure what happened with the firmware update, but the log does suggest that the resync had finished before the reboot/firmware install.
&nbsp;
Do you have 3 disks in the NAS?
&nbsp;
Are you able to access the data in read-only mode?&nbsp; If so, I suggest backing it up (if you don't have an up-to-date backup already).
&nbsp;
The errors on disk 2 are concerning.&nbsp; It would be useful to download the log zip file (which RAIDar should be able to do), and then copy/paste the contents of mdstat.log.
&nbsp;
&nbsp;

Supercows · Answer

Thanks for your reply!I have 3 disks in the readynas. I added 1 today.&nbsp;Mdstat.log:Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]md1 : active raid1 sdc2[2] sdb2[1] sda2[0]523264 blocks super 1.2 [3/3] [UUU]md126 : active (read-only) raid1 sda4[0] sdc4[1]976619904 blocks super 1.2 [2/2] [UU]resync=PENDINGmd127 : active (read-only) raid5 sda3[3] sdb3[2]2925416800 blocks super 1.2 level 5, 32k chunk, algorithm 2 [3/2] [UU_]md0 : active raid1 sdc1[4] sda1[3] sdb1[2]4190208 blocks super 1.2 [3/3] [UUU]unused devices: &lt;none&gt;/dev/md/0:Version : 1.2Creation Time : Wed Mar 16 08:41:11 2016Raid Level : raid1Array Size : 4190208 (4.00 GiB 4.29 GB)Used Dev Size : 4190208 (4.00 GiB 4.29 GB)Raid Devices : 3Total Devices : 3Persistence : Superblock is persistentUpdate Time : Fri Oct 29 21:23:29 2021State : cleanActive Devices : 3Working Devices : 3Failed Devices : 0Spare Devices : 0Consistency Policy : unknownName : 0a4510d0:0 (local to host 0a4510d0)UUID : 4858ca72:1e8ebe2a:dcbdda0a:4c08b023Events : 1139Number Major Minor RaidDevice State3 8 1 0 active sync /dev/sda12 8 17 1 active sync /dev/sdb14 8 33 2 active sync /dev/sdc1/dev/md/data-0:Version : 1.2Creation Time : Wed Mar 16 08:41:11 2016Raid Level : raid5Array Size : 2925416800 (2789.89 GiB 2995.63 GB)Used Dev Size : 2925416800 (2789.89 GiB 2995.63 GB)Raid Devices : 3Total Devices : 2Persistence : Superblock is persistentUpdate Time : Fri Oct 29 20:03:16 2021State : clean, degradedActive Devices : 2Working Devices : 2Failed Devices : 0Spare Devices : 0Layout : left-symmetricChunk Size : 32KConsistency Policy : unknownDelta Devices : 1, (2-&gt;3)Name : 0a4510d0:data-0 (local to host 0a4510d0)UUID : 35e58e71:f4df1a57:38243e16:1e8a5376Events : 122055Number Major Minor RaidDevice State3 8 3 0 active sync /dev/sda32 8 19 1 active sync /dev/sdb3- 0 0 2 removed/dev/md/data-1:Version : 1.2Creation Time : Fri Oct 29 16:59:31 2021Raid Level : raid1Array Size : 976619904 (931.38 GiB 1000.06 GB)Used Dev Size : 976619904 (931.38 GiB 1000.06 GB)Raid Devices : 2Total Devices : 2Persistence : Superblock is persistentUpdate Time : Fri Oct 29 16:59:32 2021State : clean, resyncing (PENDING)Active Devices : 2Working Devices : 2Failed Devices : 0Spare Devices : 0Consistency Policy : unknownName : 0a4510d0:data-1 (local to host 0a4510d0)UUID : 135af482:d759e7bd:2ad1f59b:8ea3bb81Events : 1Number Major Minor RaidDevice State0 8 4 0 active sync /dev/sda41 8 36 1 active sync /dev/sdc4&nbsp;unfortunately I cannot access data in readonly mode. Can I do something on ssh to make that possible?Is there something I can do to fix this?&nbsp;

StephenB · Answer

The resync pending isn't something I've seen before.
&nbsp;
It is possible to set the volume to read/write with mdadm
mdadm --readwrite /dev/md127
But I really don't know what will happen if you try that.&nbsp; It could make things worse.
&nbsp;
What sizes are the disks? What disk did you add?&nbsp; Was it smaller than the others?
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;

Sandshark · Answer

There is no way the added drive did a RAID sync of the data volume in two minutes.&nbsp; The only things that could have completed sync in that time are the OS and swap partitions.&nbsp; I have seen that erroneous message at that time before (and, I think, I reported it here).&nbsp; It can make you erroneously believe that it is OK to go on with using the NAS as normal, but it's not.&nbsp; Consequently, it appears the system was re-booted and did an OS update while a sync was taking place, which can be bad.&nbsp; Resync pending is what you would see for md126 when md127 is still doing a sync.&nbsp; You have these two because you at one point had smaller drives, so you have two stacked RAIDs.&nbsp; But with something having gone wrong with the sync of md127 (because of the re-boot, I'm fairly certain), syncing has stopped on both.&nbsp;You are seeing two volumes because BTRFS does not recognize that the two RAID layers go together.&nbsp; So, it has mounted one as data-0 (the name of the first MDADM RAID layer) and the other as data.&nbsp; But since neither is valid stand-alone, you have no access to the files.&nbsp;While I recognize what you have, I've never seen them together, so also don't know your best next step beyond contacting Netgear support.&nbsp; It's possible that making md127 read/write will start it re-syncing.&nbsp; But then md126 will likely want to re-sync, and BTRFS may not recognize the file system properly until you re-boot after the both syncs complete.&nbsp; Or maybe re-booting without the new drive is the best move.&nbsp; md127 will come up as degraded, but maybe not read-only.&nbsp;If you have no backup, so a factory reset is not an acceptable alternate&nbsp;if nothing works to fix it, you are best off leaving it to ReadyNAS support.

Forum Discussion

ReadyNAS 426 stuck on booting..

10 Replies

Radair:

Successfully completed diagnostics

System

Logs

Related Content

ReadyNas NV+ v2 stuck on boot menu

ReadyNAS Ultra 6 - stuck at "ReadyNAS" boot

Readynas NV+ stuck on boot

Stuck booting. ReadyNAS NVX

ReadyNAS stuck on 'Booting 0%'

NETGEAR Academy

ProSupport for Business

Oct 29, 2021 20:10:53		System: ReadyNASOS background service started.
Oct 29, 2021 20:01:28		System: The system is shutting down.
Oct 29, 2021 19:59:24		System: ReadyNASOS background service started.
Oct 29, 2021 19:59:24		System: Firmware was upgraded to 6.10.5.
Oct 29, 2021 18:41:59		System: The system is rebooting.
Oct 29, 2021 17:02:56		Disk: Disk in channel 3 (Internal) changed state from RESYNC to ONLINE.
Oct 29, 2021 16:59:34		Volume: Resyncing started for Volume data.
Oct 29, 2021 16:59:27		Disk: Disk Model:WDC WD60EFZX-68B3FN0 Serial:WD-C814B1SG was added to Channel 3 of the head unit.