NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Guide

Oct 29, 2021

ReadyNAS 426 stuck on booting..

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...

Guide

Oct 29, 2021

Radair:

Successfully completed diagnostics

System

Disk 2 has 52 Reallocated Sectors
Disk 2 has 32 Reallocation Events
Disk 2 has 3 Current Pending Sectors
Volume data is inactive
Volume data-0 is inactive

Logs

2021-10-29 20:10:35: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 20:03:14: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:59:03: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:54:27: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:46:44: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:37:18: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:27:00: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:12:53: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:09:24: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2
2021-10-29 19:05:14: md/raid:md126: raid level 5 active with 2 out of 3 devices, algorithm 2

Guru - Experienced User

Oct 29, 2021

Not sure what happened with the firmware update, but the log does suggest that the resync had finished before the reboot/firmware install.

Do you have 3 disks in the NAS?

Are you able to access the data in read-only mode? If so, I suggest backing it up (if you don't have an up-to-date backup already).

The errors on disk 2 are concerning. 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.

Supercows
Guide
Oct 29, 2021
Thanks for your reply!
I have 3 disks in the readynas. I added 1 today.

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=PENDING

md127 : 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: <none>
/dev/md/0:
Version : 1.2
Creation Time : Wed Mar 16 08:41:11 2016
Raid Level : raid1
Array Size : 4190208 (4.00 GiB 4.29 GB)
Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Fri Oct 29 21:23:29 2021
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Consistency Policy : unknown
Name : 0a4510d0:0 (local to host 0a4510d0)
UUID : 4858ca72:1e8ebe2a:dcbdda0a:4c08b023
Events : 1139
Number Major Minor RaidDevice State
3 8 1 0 active sync /dev/sda1
2 8 17 1 active sync /dev/sdb1
4 8 33 2 active sync /dev/sdc1
/dev/md/data-0:
Version : 1.2
Creation Time : Wed Mar 16 08:41:11 2016
Raid Level : raid5
Array Size : 2925416800 (2789.89 GiB 2995.63 GB)
Used Dev Size : 2925416800 (2789.89 GiB 2995.63 GB)
Raid Devices : 3
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Fri Oct 29 20:03:16 2021
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 32K
Consistency Policy : unknown
Delta Devices : 1, (2->3)
Name : 0a4510d0:data-0 (local to host 0a4510d0)
UUID : 35e58e71:f4df1a57:38243e16:1e8a5376
Events : 122055
Number Major Minor RaidDevice State
3 8 3 0 active sync /dev/sda3
2 8 19 1 active sync /dev/sdb3
- 0 0 2 removed
/dev/md/data-1:
Version : 1.2
Creation Time : Fri Oct 29 16:59:31 2021
Raid Level : raid1
Array Size : 976619904 (931.38 GiB 1000.06 GB)
Used Dev Size : 976619904 (931.38 GiB 1000.06 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Fri Oct 29 16:59:32 2021
State : clean, resyncing (PENDING)
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Consistency Policy : unknown
Name : 0a4510d0:data-1 (local to host 0a4510d0)
UUID : 135af482:d759e7bd:2ad1f59b:8ea3bb81
Events : 1
Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 36 1 active sync /dev/sdc4

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?
- StephenB
  Guru - Experienced User
  Oct 29, 2021
  The resync pending isn't something I've seen before.
  
  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. It could make things worse.
  
  What sizes are the disks? What disk did you add? Was it smaller than the others?
  - Sandshark
    Sensei
    Oct 30, 2021
    There is no way the added drive did a RAID sync of the data volume in two minutes. The only things that could have completed sync in that time are the OS and swap partitions. I have seen that erroneous message at that time before (and, I think, I reported it here). It can make you erroneously believe that it is OK to go on with using the NAS as normal, but it's not. Consequently, it appears the system was re-booted and did an OS update while a sync was taking place, which can be bad. Resync pending is what you would see for md126 when md127 is still doing a sync. You have these two because you at one point had smaller drives, so you have two stacked RAIDs. 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.
    
    You are seeing two volumes because BTRFS does not recognize that the two RAID layers go together. So, it has mounted one as data-0 (the name of the first MDADM RAID layer) and the other as data. But since neither is valid stand-alone, you have no access to the files.
    
    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. It's possible that making md127 read/write will start it re-syncing. 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. Or maybe re-booting without the new drive is the best move. md127 will come up as degraded, but maybe not read-only.
    
    If you have no backup, so a factory reset is not an acceptable alternate if nothing works to fix it, you are best off leaving it to ReadyNAS support.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.