NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Forced Power down results in Booting Checking FS
Yesterday, I force shut down my NAS using the power button(holding it for 5 seconds) on the front of it as streaming using Plex seemed to be failing for some reason. The NAS powered down with no problems but upon booting went through a FS check and emailed me what I posted below.
***** File system check performed at Fri Dec 7 19:08:37 EST 2012 ***** fsck 1.41.14 (22-Dec-2010)
/dev/c/c: Clearing orphaned inode 51544350 (uid=0, gid=0, mode=040366, size=32768)
/dev/c/c: Illegal inode 1354924574 in orphaned inode list.
/dev/c/c was not cleanly unmounted, check forced.
/dev/c/c: 205292/91185152 files (5.6% non-contiguous), 695053712/1458962432 blocks
It then resync the array (for hours) and emailed this below. I run the volume check and raid scrubbing every two weeks on a schedule so I didn't expect this type of behavior following a forced power down. I've powered the unit down before without issues in the same manner and therefore thought nothing of it until the unit ran through this procedure. My question here is this normal and should I be concerned with the results above? I have downloaded all my logs and can upload them if that would help confirm all is well. Just let me know which one is needed. Thanks!
RAID sync finished on volume C.
[Sat Dec 8 03:26:17 EST 2012]
***** File system check performed at Fri Dec 7 19:08:37 EST 2012 ***** fsck 1.41.14 (22-Dec-2010)
/dev/c/c: Clearing orphaned inode 51544350 (uid=0, gid=0, mode=040366, size=32768)
/dev/c/c: Illegal inode 1354924574 in orphaned inode list.
/dev/c/c was not cleanly unmounted, check forced.
/dev/c/c: 205292/91185152 files (5.6% non-contiguous), 695053712/1458962432 blocks
It then resync the array (for hours) and emailed this below. I run the volume check and raid scrubbing every two weeks on a schedule so I didn't expect this type of behavior following a forced power down. I've powered the unit down before without issues in the same manner and therefore thought nothing of it until the unit ran through this procedure. My question here is this normal and should I be concerned with the results above? I have downloaded all my logs and can upload them if that would help confirm all is well. Just let me know which one is needed. Thanks!
RAID sync finished on volume C.
[Sat Dec 8 03:26:17 EST 2012]
2 Replies
Replies have been turned off for this discussion
- I think it is normal, although the two inode issues suggest that a couple of file writes might not have completed. If there were some other files being updated on the NAS shortly before you did the forced shutdown, you might want to check them.
Did you try restarting with Frontview first? It's not a good idea to use the 5-second reset unless you are forced into it. StephenB wrote: I think it is normal, although the two inode issues suggest that a couple of file writes might not have completed. If there were some other files being updated on the NAS shortly before you did the forced shutdown, you might want to check them.
Did you try restarting with Frontview first? It's not a good idea to use the 5-second reset unless you are forced into it.
There was no files being written to the NAS. We were only steaming movies from it so I don't expect any files were corrupted. As for rebooting, I was being lazy but agree I should have used Frontview.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
