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...
Sounds like if possible backing up the data would be the next step. Assuming the data volume is fine this should be straightforward.
I'm sorry, I didn't want to be so pushy.
I've tried that. While running all the tests, my NAS was connected with PSU that came in the box (this one was in use for few days only so I assume it should be fully functional).
Some other of my thoughts/observations:
- The boot process seems completly normal: fans spinning up to max at the beginning and then down after a short time. However, the HDD LEDs not being lit up at all. Anyway, I can hear drives working (sometimes louder than when on standby, like during read operations). During the HDD test, drive LEDs blinking and corresponding sound (read/write operations) could be heard;
- RAIDar still works perfectly, saying that everything is completly OK. However, trying to restart the unit within RAIDar does nothing and both SSH and HTTP refusing connections;
- While reading the logs again, I've noticed that some of services are being fired up (like Apache, but only at 443 and raidar daemon - which is obvious since RAIDar is working). Admin page accessed over SSL opens up, asks for credentials and after long wait at progress bar page it says that "Admin Page is offline".
I think it's time to poke around with tech support mode and/or USB recovery ;-)
Now, some heavier details:
Unit working in tech support mode now. All filesystems mount without problems. smartctl not giving any error other than 1 tick in UDMA_CRC_Error_Count on one drive.
I did scrub of root fs - every time (scrubbing ran 3 times) it reports an error and says it's been corrected.
dmesg gives me the same as we seen in logs:
BTRFS: bdev /dev/md/0 errs: wr 2, rd 386, flush 0, corrupt 0, gen 0
BUT, there is also one more thing in there:
BTRFS: i/o error at logical 3377745920 on dev /dev/md/0, sector 7032488, root 5, inode 140793, offset 0, length 4096, links 1 (path: var/log/journal/17c5a086e9eb417ea121e4464ee323f9/system.journal
Ofcourse, trying to cat this file gives me i/o error.
# hdparm --read-sector 7032488 on sda and sdb (matrix members) gives no error at all.
After that I finally did # btrfsck --repair /dev/md0 - no errors. Scrubbing after that reported an error again.
I'm lacking ideas for now...
Sounds like if possible backing up the data would be the next step. Assuming the data volume is fine this should be straightforward.
Yep, I've heard that btrfs isn't really mature fs and that it can even loose a partition without a certain reason but didn't expect to experience such problems.
Data partition is all right (according to scrub), so I assume I will hit the road toward this direction. Lot of copying over 100Base to my old NASes ahead of me :/
Thanx mdgm for your advice and patience for my laziness ;-)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
