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. What can I do? I stil can boot in readonly access. Normal boot gives a systemd-udev-settle.service when i press the power button.
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.
Model: RN426|ReadyNAS 426 – High-performance Business Data Storage - 6-Bays
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.
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.
There is no way the added drive did a RAID sync of the data volume in two minutes.
Agreed. I didn't look at the times as closely as I should have.
Normally with XRAID, md127 contains all the drives in the array. md126 often contains a subset (the larger drives).
At this point
md126 only has sda and sdc (with nothing shown as missing, but the pending resync)
md127 only contains sda and sdb with one drive shown as missing - which would be sdc.
It is possible that the system would show you the files if you reboot w/o the newly inserted drives. But if you try that, I suggest booting the NAS in read-only mode, in order to prevent any further damage.
If it works, the next step would be to make a backup. If disk 2 fails during the resync of the new drive (which is a real danger, given the errors), then you would lose data.
If it doesn't work (or you don't want to risk it), then I agree with @Sandshark that you should contact paid netgear support.
Device Start End Sectors Size Type /dev/sda1 64 8388671 8388608 4G Linux RAID /dev/sda2 8388672 9437247 1048576 512M Linux RAID /dev/sda3 9437248 5860533103 5851095856 2.7T Linux RAID /dev/sda4 5860533104 7814037119 1953504016 931.5G Linux RAID
root@NAS:/# mdadm --assemble --scan --verbose mdadm: looking for devices for further assembly mdadm: no recogniseable superblock on /dev/md1 mdadm: no recogniseable superblock on /dev/md/data-1 mdadm: no recogniseable superblock on /dev/md/data-0 mdadm: no recogniseable superblock on /dev/md/0 mdadm: /dev/sdc4 is busy - skipping mdadm: /dev/sdc3 is busy - skipping mdadm: /dev/sdc2 is busy - skipping mdadm: /dev/sdc1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sdc mdadm: /dev/sdb3 is busy - skipping mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdb1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sdb mdadm: /dev/sda4 is busy - skipping mdadm: /dev/sda3 is busy - skipping mdadm: /dev/sda2 is busy - skipping mdadm: /dev/sda1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sda mdadm: No arrays found in config file or automatically
I already explained what you already have. md126 and md127 are already mounted (they show as active), though they are not properly sync'ed. More importantly, the BTRFS file system that is supposed to encompass them both doesn't see them as being linked. You can't just go mounting additional partitions that are supposed to be a part of an MDADM RAID and BTRFS volume independently. If it were to work, you'd do more harm that good.
I have my documents etc in a azure backup. Series and movies are gone. I am going to reset the system and start over. In the last 15 years and three readynas further never had issues like this before. I am very disappointed. It is what it is
