NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
After upgrading to 6.7.1 on RN214 no volumes can be loaded
Hello,
I just installed the new upgrade 6.7.1 on my RN214 and got the confusing message that my volumes can`t be loaded.
It`s the same problem others have:
ReadyNAS 516 just upgraded to 6.7.1 and data volume has not loaded
I don`t know what to do.
Best regards
Kalle
You could perhaps try ReadyNASOS 6.7.3-T283 (Beta 1)
There's a fix in there for one possible reason why a volume may not mount. I wonder if you ran into that.
36 Replies
Replies have been turned off for this discussion
Maybe you want to upvote this "idea": https://community.netgear.com/t5/Idea-Exchange-for-ReadyNAS/Change-the-incredibly-confusing-error-message-quot-remove/idi-p/1271658
Download the logs from the GUI, and look for md127 in dmesg.log.
Hi jak0lantash,
thanks for your reply.
I have downloaded the logs and in the dmesg.log bu there were no entries like "md127".My Netgear has four disks und is running a RAID 5.
Here a snippet from the volume.log:
RAID data-0: Device: sda3 HostID: 119c1bce UUID: 632ff5fd-6534-2524-9c97-98d780e47e94 Size: 23413000704 Component size: 7804333680 Level: 5 State: inactive Action: idle Flags 0x0 Members: 4 Pool: data-0 Disks: sda: HostID: 119c1bce Flags: 0x0 Size: 7814037168 (3726 GB) Free: 4062 Controller 0 Channel: 0 Model: WDC WD40EFRX-68WT0N0 Serial: WD-WCC4E2XEK9VE Firmware: 82.00A82 RPM: 5400 SMART data Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 25 Start/Stop Count: 6678 Power-On Hours: 2962 Power Cycle Count: 387 Load Cycle Count: 6647 Latest Self Test: Passed sdb: HostID: 119c1bce Flags: 0x0 Size: 7814037168 (3726 GB) Free: 4062 Controller 0 Channel: 1 Model: WDC WD40EFRX-68WT0N0 Serial: WD-WCC4E4CZPUVA Firmware: 82.00A82 RPM: 5400 SMART data Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 25 Start/Stop Count: 6745 Power-On Hours: 2961 Power Cycle Count: 386 Load Cycle Count: 6715 Latest Self Test: Passed sdc: HostID: 119c1bce Flags: 0x0 Size: 7814037168 (3726 GB) Free: 4062 Controller 0 Channel: 2 Model: WDC WD40EFRX-68WT0N0 Serial: WD-WCC4E3XCNPFF Firmware: 82.00A82 RPM: 5400 SMART data Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 25 Start/Stop Count: 6716 Power-On Hours: 2961 Power Cycle Count: 383 Load Cycle Count: 6688 Latest Self Test: Passed sdd: HostID: 119c1bce Flags: 0x0 Size: 7814037168 (3726 GB) Free: 4062 Controller 0 Channel: 3 Model: WDC WD40EFRX-68WT0N0 Serial: WD-WCC4E3JR81HF Firmware: 82.00A82 RPM: 5400 SMART data Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 25 Start/Stop Count: 6503 Power-On Hours: 2961 Power Cycle Count: 383 Load Cycle Count: 6476 Latest Self Test: Passed
Best regards
Kalle
- Check in dmesg.log again and look for sda3, sdb3, sdc3 and sdd3.
Hi,
I am not an expert with this but I guess sda is down and that's why it can't start.
Here is the snipped out of the dmesg log.scsi 0:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 0A82 PQ: 0 ANSI: 5 [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] 4096-byte physical blocks [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] Write Protect is off [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [Sun May 14 12:31:13 2017] ata5: SATA link down (SStatus 0 SControl 300) [Sun May 14 12:31:13 2017] sda: sda1 sda2 sda3 [Sun May 14 12:31:13 2017] sd 0:0:0:0: [sda] Attached SCSI disk [Sun May 14 12:31:13 2017] pci 0000:00:04.1: [1c36:8011] type 00 class 0x100000 [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.1: enabling device (0400 -> 0402) [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.1: al_crypto_pci_probe: Skipping alg/hash initialization, no allocated channels [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.1: crc/csum algorithms registered in /proc/crypto [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.0: algorithms registered in /proc/crypto [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.0: hash algorithms registered in /proc/crypto [Sun May 14 12:31:13 2017] al_crypto 0000:00:04.0: al_crypto_pci_probe: Skipping crc initialization, no allocated channels [Sun May 14 12:31:13 2017] usbcore: registered new interface driver usbhid [Sun May 14 12:31:13 2017] usbhid: USB HID core driver [Sun May 14 12:31:13 2017] ip_tables: (C) 2000-2006 Netfilter Core Team [Sun May 14 12:31:13 2017] NET: Registered protocol family 10 [Sun May 14 12:31:13 2017] NET: Registered protocol family 17 [Sun May 14 12:31:13 2017] 8021q: 802.1Q VLAN Support v1.8 [Sun May 14 12:31:13 2017] Key type dns_resolver registered [Sun May 14 12:31:13 2017] Registering SWP/SWPB emulation handler [Sun May 14 12:31:13 2017] registered taskstats version 1 [Sun May 14 12:31:13 2017] BTRFS: using crc32c-generic for crc32c [Sun May 14 12:31:13 2017] Btrfs loaded [Sun May 14 12:31:13 2017] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [Sun May 14 12:31:13 2017] rtc-ds1307 0-0068: setting system clock to 2017-05-14 10:31:13 UTC (1494757873) [Sun May 14 12:31:14 2017] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd [Sun May 14 12:31:14 2017] usb-storage 2-3:1.0: USB Mass Storage device detected [Sun May 14 12:31:14 2017] scsi host6: usb-storage 2-3:1.0 [Sun May 14 12:31:15 2017] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sun May 14 12:31:16 2017] ata4.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133 [Sun May 14 12:31:16 2017] ata4.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [Sun May 14 12:31:16 2017] ata4.00: configured for UDMA/133 [Sun May 14 12:31:16 2017] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sun May 14 12:31:16 2017] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sun May 14 12:31:16 2017] ata2.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133 [Sun May 14 12:31:16 2017] ata2.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [Sun May 14 12:31:16 2017] ata2.00: configured for UDMA/133 [Sun May 14 12:31:16 2017] scsi 1:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 0A82 PQ: 0 ANSI: 5 [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] 4096-byte physical blocks [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] Write Protect is off [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [Sun May 14 12:31:16 2017] ata3.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133 [Sun May 14 12:31:16 2017] ata3.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [Sun May 14 12:31:16 2017] ata3.00: configured for UDMA/133 [Sun May 14 12:31:16 2017] scsi 2:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 0A82 PQ: 0 ANSI: 5 [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] 4096-byte physical blocks [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] Write Protect is off [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [Sun May 14 12:31:16 2017] scsi 3:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 0A82 PQ: 0 ANSI: 5 [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] 4096-byte physical blocks [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] Write Protect is off [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [Sun May 14 12:31:16 2017] sdb: sdb1 sdb2 sdb3 [Sun May 14 12:31:16 2017] sd 1:0:0:0: [sdb] Attached SCSI disk [Sun May 14 12:31:16 2017] sdd: sdd1 sdd2 sdd3 [Sun May 14 12:31:16 2017] sd 3:0:0:0: [sdd] Attached SCSI disk [Sun May 14 12:31:16 2017] sdc: sdc1 sdc2 sdc3 [Sun May 14 12:31:16 2017] sd 2:0:0:0: [sdc] Attached SCSI disk [Sun May 14 12:31:16 2017] ata6: SATA link down (SStatus 0 SControl 300)
Best regards
KalleYou should have further mentions of sda3, and md127 lower than that in dmesg.log.
If you don't, at the end volume.log, there is a section "=== df -h ===", check the line:
/dev/md0 4.0G 517M 3.3G 14% /
Is it 100% full?
You can also search systemd-journal.log and mdstat.log for mentions of md127.
How many HDDs do you have in the NAS?
- Not necessarily, no.
Let's wait for mdgm's feedback.What do you mean?
I don't want to argue with you I am only curios.
Best regards
KalleI'm not arguing either :smileywink:
There are multiple reasons for the volume to appear "inactive", some of the most common:
- Full root: the volume dedicated to the system is completely full, preventing it from booting properly. In your case, it could be related to the process of updating the F/W (any F/W). Or some add-on that filled the volume and the consequence appeared after the reboot, as part of the update process.
- Corrupt system: often due to the previous condition, but also rarely occur without full root.
- Multiple disk failure: your drives could have been slowly dying but seemlessly "working", or suddenly died, or a mix. Updating a firmware implies writing to the drives which can trigger failure(s).
- Erroring disk: a disk can be flapping and cause the NAS to be enable to mount the volume.
- BTRFS corruption: any operation on the volume, even mount/unmount can lead to filesystem corruption if an unexpected event occur (at FS or HW level). It happens.
Etc.
It's a shame that the NAS doesn't show why is the volume inactive, in the GUI. It would reasonably easy to integrate it and really useful for anyone running into the issue, hence the post in the "idea" section.
Hi,
yes I did it several months ago. I totaly forget about that. I did it because I do that on my other linux maschines, simple as that. That was not the smartest move. After this dist-upgrade I had big problems with the NAS and I had to do a Firmware reset. Seemingly there are also leftovers from this action. S h i t !
Best regards
Kalle
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
