NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RNDU2000 Unit systemd-journald.service entered failed state
Hey guys,
I've got a problem with my RNDU2000. Today, out of sudden, I was unable to get to my shares and network traffic stopped (it served as a router between 2 networks). I wasn't able to shut it down gracefully, so I just forced it to do so.
After reboot it failed to boot: fans spinning properly, activity and power LEDs blinking as they should but both drive LEDs dead + connection refused on SSH/Telnet, admin page not accessible but pings flying all right. Being terribly exhausted today, I've rebooted the unit again with same method - twice (totally noobish of me).
After that I got enlightened: RAIDar. It says everything is all right, even system diagnostics. I was able to fetch logs and wasn't pleased to see lines like this inside dmesg.log:
[Fri Jan 27 01:01:13 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 167, flush 0, corrupt 0, gen 0 [Fri Jan 27 01:01:13 2017] systemd[1]: Unit systemd-journald.service entered failed state. [Fri Jan 27 01:01:13 2017] systemd[1]: systemd-journald.service start request repeated too quickly, refusing to start. [Fri Jan 27 01:01:14 2017] systemd[1243]: Failed at step STDOUT spawning /sbin/swapon: Connection refused [Fri Jan 27 01:01:14 2017] systemd[1]: dev-md1.swap swap process exited, code=exited status=209 [Fri Jan 27 01:01:14 2017] systemd[1]: Unit dev-md1.swap entered failed state. [Fri Jan 27 01:01:14 2017] systemd[1254]: Failed at step STDOUT spawning /bin/mount: Connection refused [Fri Jan 27 01:01:14 2017] systemd[1256]: Failed at step STDOUT spawning /sbin/udevadm: Connection refused [Fri Jan 27 01:01:14 2017] systemd[1]: VOL1.mount mount process exited, code=exited status=209 [Fri Jan 27 01:01:14 2017] systemd[1]: Job apps.mount/start failed with result 'dependency'. [Fri Jan 27 01:01:14 2017] systemd[1]: Job home.mount/start failed with result 'dependency'. [Fri Jan 27 01:01:14 2017] systemd[1]: Job local-fs.target/start failed with result 'dependency'. [Fri Jan 27 01:01:14 2017] systemd[1]: Unit VOL1.mount entered failed state. [Fri Jan 27 01:01:14 2017] systemd[1]: udev-trigger.service: main process exited, code=exited, status=209 [Fri Jan 27 01:01:14 2017] systemd[1]: Unit udev-trigger.service entered failed state. [Fri Jan 27 01:22:57 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 215, flush 0, corrupt 0, gen 0 [Fri Jan 27 01:22:57 2017] systemd[1]: Unit systemd-journald.service entered failed state. [Fri Jan 27 01:22:57 2017] systemd[1]: systemd-journald.service start request repeated too quickly, refusing to start. [Fri Jan 27 01:22:57 2017] systemd[1]: Unit systemd-journald.socket entered failed state. [Fri Jan 27 01:49:19 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 216, flush 0, corrupt 0, gen 0 [Fri Jan 27 01:49:42 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 217, flush 0, corrupt 0, gen 0 [Fri Jan 27 01:49:42 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 218, flush 0, corrupt 0, gen 0 [Fri Jan 27 01:49:42 2017] BTRFS: bdev /dev/md0 errs: wr 2, rd 219, flush 0, corrupt 0, gen 0
Ofc, these are only parts of the drama I saw inside :mansad:
My unit is running RNOS 6.5.1, stuffed with 2x WD30EFRX.
Is there any way I could try to fix these errors within my ReadyNAS? Or I shouldn't even bother, rig both drives to PC and start recovery process?
Sounds like if possible backing up the data would be the next step. Assuming the data volume is fine this should be straightforward.
10 Replies
Replies have been turned off for this discussion
You could send the logs zip file in (see the Sending Logs link in my sig).
Looks like there's problems wiht the 4GB root volume.
Are you seeing any SMART errors on the disks?Thanx for your reply. I've just sent the logs (minus bash_history - some sensitive data out there). I've searched all the logs for smart and got only few infos - no warns/errors at all. If you look in the logs, you will see alot of low voltage warnings - I'm aware of that but not sure if it could cause such errors.
I haven't tried USB recovery yet. Do you think it could help in this matter? For now, my unit is turned off to prevent any further disk corruption - if there could be any. I'm IT spec and did alot of data recoveries and had a failure once doing it with my data so I prefer to be cautious.
I really appreciate the great job you are doing for the community! :smileyhappy:
The disks look healthy.
You could try running the memory test boot menu option if you want.
I can see lots of errors about voltage being out of spec in the logs. This could suggest a possible PSU issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
