NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RNDU4000 Stuck in safe mode
Hello.
Recently my ReadyNAS Ultra 4 hung again (it hangs approx. each week, I reboot it and it works fine for a week after that) and after reboot it started in Safe Mode. There seem to be no way to exit it now.
What I tried:
1) Boot Menu/Test Disks. It does seem to check the discs and after it reaches 100% the device just continues to flash the HDD light and show "Testing Disks". Doesn't seem to do anything beyond that.
2) Boot Menu/OS Reinstall. Gets stuck right after the start at "Checking root FS..". I waited for a couple of hours and then decided that it's not going to work eirther.
3) Updating firmware via web-interface - just uploading new (or old) firmware results in "Unknown application error". Might be caused by the safe mode. Doesn't work anyway.
4) Updating firmware to the latest beta - almost worked, the package has been successfully downloaded, but it ended up booting the old firmware in the same Safe Mode again.
5) I did try to check the disks with btrfsck via SSH - it found some errors on /dev/md127, which I tried to repair, but unfortunately the device doesn't have enough memory for that and brtfsck has been killed by OOM killer.
No idea how to check the root FS via SSH, though, as it requires mounting it..
I tried to run some tests with smartctl, but they were unable to find any errors on any disks.
Any ideas what could have caused it and how to fix it?
Configuration:
ReadyNAS Ultra 4 with 4 3Tb disks (HGST HDN724030ALE640)
ReadyNAS OS 6.9.4 Hotfix 1
If I remember correctly, I chose to format them with X-RAID and followed the standard installation procedure after that.
4 Replies
Replies have been turned off for this discussion
A bit of logs (I hope it's relevant).\
-------------
Oct 30 06:57:45 nas-26-CB-3C kernel: scsi 6:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: Attached scsi generic sg4 type 0
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: Embedded Enclosure Device
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: Wrong diagnostic page; asked for 1 got 0
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: Failed to get diagnostic page 0xffffffea
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: Failed to bind enclosure -19
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] 244736 512-byte logical blocks: (125 MB/120 MiB)
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] Write Protect is off
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] Mode Sense: 43 00 00 00
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] No Caching mode page found
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] Assuming drive cache: write through
Oct 30 06:57:45 nas-26-CB-3C kernel: random: nonblocking pool is initialized
Oct 30 06:57:45 nas-26-CB-3C kernel: sde: sde1
Oct 30 06:57:45 nas-26-CB-3C kernel: sd 6:0:0:0: [sde] Attached SCSI removable disk
Oct 30 06:57:45 nas-26-CB-3C kernel: md: md0 stopped.
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdb1>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdc1>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdd1>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sda1>
Oct 30 06:57:45 nas-26-CB-3C kernel: md/raid1:md0: active with 4 out of 4 mirrors
Oct 30 06:57:45 nas-26-CB-3C kernel: md0: detected capacity change from 0 to 4290772992
Oct 30 06:57:45 nas-26-CB-3C kernel: md: md1 stopped.
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdb2>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdc2>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sdd2>
Oct 30 06:57:45 nas-26-CB-3C kernel: md: bind<sda2>
Oct 30 06:57:45 nas-26-CB-3C kernel: md/raid10:md1: active with 4 out of 4 devices
Oct 30 06:57:45 nas-26-CB-3C kernel: md1: detected capacity change from 0 to 1071644672
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS: device label 5e26cb3c:root devid 1 transid 752956 /dev/md0
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS critical (device md0): corrupt node, bad key order: block=3660038144, root=1, slot=60
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS critical (device md0): corrupt node, bad key order: block=3660038144, root=1, slot=60
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS error (device md0): open_ctree failed
Oct 30 06:57:45 nas-26-CB-3C kernel: EXT4-fs (md0): VFS: Can't find ext4 filesystem
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS critical (device md0): corrupt node, bad key order: block=3660038144, root=1, slot=60
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS critical (device md0): corrupt node, bad key order: block=3660038144, root=1, slot=60
Oct 30 06:57:45 nas-26-CB-3C kernel: BTRFS error (device md0): open_ctree failed
-------------Well, it does look like the root FS has failed, but it's not clear how to fix it if all the recommended solutions don't really work..
Running btrfsck on the data volume isn't advisable if you don't know what you're doing. You should always try to have a backup first before doing a btrfsck --repair.
The 4GB root volume on md0 could potentially be wiped, but that contains the log files. If there's a problem with the data volume then wiping the 4GB root volume would be wiping information that may be important.Ok, let me clarify it. Do you recommend to wipe md0 or do you mean that could have caused the issue?
I'd like to force OS reinstall, cause it looks like OS partition is broken, is there any way to do it except for the ones listed in my original post?
Resetting it to factory default would be an option, of course, but I would really like to avoid it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
