Hi,I've had the same problem as mentioned here:http://www.readynas.com/forum/viewtopic.php?f=160&t=81294readynas ultra 4os 6.2.4 (as I recall)After a while ssh was not accessible.I also had the only option to unsafe power off the device.Only that now it keeps saying: bootingfollowed by boot failed, retry boot.I've already tried the boot mem check which resulted in no errors.Raidar only shows "system starting up..."ssh, web, ... are not accessible.I'm a little careful on what to do next.Should I try the boot os install?

update:after the mem check, again rebooted and waited.Raidar reports: management service is offline.So It boots again, but probably cpu is again so high that admin and shh are not accessible. (or were for a short time)downloading logs, ... failed.

could download logs. can pm on request.First look:systemd-journal.logJun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238Jun 19 01:02:16 bigdisk kernel: btrfs: corrupt leaf, slot offset bad: block=2306986344448,root=1, slot=238

Can you run the memory test boot menu option?: http://kb.netgear.com/app/answers/detail/a_id/21104Run at least a few passes of this test.If the memory passes then run the disk test boot menu optionPlease send me the logs you have downloaded (there is an email address mentioned on the page linked to by the Sending Logs link in my sig)

Hi!logs sent.Memory test was run, but running again now.Will run the disk test after that.And keep you posted.Thanks!

Thanks for the update.Looking at your logs one of your disks has 6 ATA error, but those errors were back in April. So I don't think that is the problem here though that disk might be failing.Will be interested to hear the result of the memory test.Do you have a backup?

6.2.4 high cpu => lockup => reboot => boot failed

14 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jun 20, 2015
/dev/md0 is the OS partition, not the data partition.

On my RN102 (which is jbod) /dev/md126 and /dev/md127 are the two data partitions.
mdgm-ntgr
NETGEAR Employee Retired
Jun 22, 2015
Would not suggest running commands randomly when you are not familiar with them especially destructive ones.

Cloning your disks before doing something destructive would be recommended.

If you are going to use btrfs restore you would do e.g.

# btrfs restore /dev/md127 /mnt/restore

If a USB disk is mounted at /mnt

You can if you like run it verbosely and send the data nowhere just to test if it can find anything

btrfs restore -v /dev/md127 /dev/null
kheno
Aspirant
Jun 22, 2015
recovering! :D

Had some errors while writing files.
Thought it would be an incompatibility with the ntfs file system, so I formatted the external disk in ext4
Problems solved.

The only question I have, and could nowhere find a hint:

My destination disks are too small to fit 5TB, can I recover/split over multiple destination drives?
When a drive is full I suspect recovery will end with an error and just stop.

Any idea?

Btw, thanks for your help!
mdgm-ntgr
NETGEAR Employee Retired
Jun 22, 2015
Sent you a PM. If you recall your directory structure there should be a way to do this.

Forum Discussion

6.2.4 high cpu => lockup => reboot => boot failed

14 Replies

Related Content

R6400v2 reboot loop - firmware fail

RBE971 reboots

Orbi 970 Constant Reboots

SSD disk failed

Firmware update failed

NETGEAR Academy

ProSupport for Business