NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Missing volume after power failure
I had a power failure that lasted too long so my UPS shut down my Ultra 4 (OS 6.6.1) When booting it up again I had this screen: I am missing my Volume and ofc my shares too and it seems th...
F_L_ wrote:Then I get:
root@Ultra:/# mount --bind / /mnt root@Ultra:/# du -h --max-depth=1 /mnt 1.8G /mnt/data
There's your issue... /mnt/data should be empty.
Do you have replicate jobs running? It's common that it pushes data to /data even though the data volume is not mounted, filling up the OS volume.
Then, once the data volume is mounted on /data, you can no longer see what was in the folder itself but the OS volume is still full.
As you have temporarily mounted the OS volume back to /mnt, you should check what's in /mnt/data and clear it to free up space on your OS volume. WARNING: Be careful what you're doing, you want to clear /mnt/data, NOT /data (where your actual data volume is mounted)!
Then I get:
root@Ultra:/# mount --bind / /mnt root@Ultra:/# du -h --max-depth=1 /mnt 7.7M /mnt/bin 0 /mnt/boot 24K /mnt/dev 13M /mnt/etc 0 /mnt/home 37M /mnt/lib 4.0K /mnt/lib64 0 /mnt/media 0 /mnt/mnt 22M /mnt/opt 0 /mnt/proc 117M /mnt/root 0 /mnt/run 11M /mnt/sbin 0 /mnt/selinux 0 /mnt/srv 0 /mnt/sys 0 /mnt/tmp 1.1G /mnt/usr 278M /mnt/var 1.8G /mnt/data 0 /mnt/apps 8.8M /mnt/c 44K /mnt/~ 44K /mnt/.sabnzbd 0 /mnt/logs 29M /mnt/frontview 3.4G /mnt root@Ultra:/#
F_L_ wrote:Then I get:
root@Ultra:/# mount --bind / /mnt root@Ultra:/# du -h --max-depth=1 /mnt 1.8G /mnt/data
There's your issue... /mnt/data should be empty.
Do you have replicate jobs running? It's common that it pushes data to /data even though the data volume is not mounted, filling up the OS volume.
Then, once the data volume is mounted on /data, you can no longer see what was in the folder itself but the OS volume is still full.
As you have temporarily mounted the OS volume back to /mnt, you should check what's in /mnt/data and clear it to free up space on your OS volume. WARNING: Be careful what you're doing, you want to clear /mnt/data, NOT /data (where your actual data volume is mounted)!
jak0lantash wrote:
F_L_ wrote:Then I get:
root@Ultra:/# mount --bind / /mnt root@Ultra:/# du -h --max-depth=1 /mnt 1.8G /mnt/data
There's your issue... /mnt/data should be empty.
Do you have replicate jobs running? It's common that it pushes data to /data even though the data volume is not mounted, filling up the OS volume.
Then, once the data volume is mounted on /data, you can no longer see what was in the folder itself but the OS volume is still full.
As you have temporarily mounted the OS volume back to /mnt, you should check what's in /mnt/data and clear it to free up space on your OS volume. WARNING: Be careful what you're doing, you want to clear /mnt/data, NOT /data (where your actual data volume is mounted)!
Thanks!
All good now, I deleted the files in /mnt/data and unmounted it again.
OS is now back to 49% full.
It turned out to be a download from usenet that was triggered when the raid was down.
Next step will be to have a lifeguard check on disk3
Device: sdc Controller: 0 Channel: 2 Model: WDC WD30EFRX-68AX9N0 Serial: WD-WMC1T1298310 Firmware: 80.00A80 Class: SATA Sectors: 5860533168 Pool: data PoolType: RAID 5 PoolState: 5 PoolHostId: 5e26b5f2 Health data ATA Error Count: 0 Reallocated Sectors: 514 Reallocation Events: 337 Spin Retry Count: 0 Current Pending Sector Count: 74 Uncorrectable Sector Count: 0 Temperature: 17 Start/Stop Count: 46 Power-On Hours: 34909 Power Cycle Count: 46 Load Cycle Count: 22
F_L_ wrote:Next step will be to have a lifeguard check on disk3
Device: sdc Controller: 0 Channel: 2 Model: WDC WD30EFRX-68AX9N0 Serial: WD-WMC1T1298310 Firmware: 80.00A80 Class: SATA Sectors: 5860533168 Pool: data PoolType: RAID 5 PoolState: 5 PoolHostId: 5e26b5f2 Health data ATA Error Count: 0 Reallocated Sectors: 514 Reallocation Events: 337 Spin Retry Count: 0 Current Pending Sector Count: 74 Uncorrectable Sector Count: 0 Temperature: 17 Start/Stop Count: 46 Power-On Hours: 34909 Power Cycle Count: 46 Load Cycle Count: 22
"Lifeguard check"?
35 thousand hours, 514 reallocated sectors, 74 pending sectors. No need to check it, it needs to be replaced. It's unfortunate I know, and it's $100, but it's time ^^
True true, will buy a new one tomorrow :)
Someone marked this as a solved which I guess is fine.
However, I'm still a bit concerned about the original error message and the increase of posts in the forum with this message.
It seems to me that this error has been posted a lot more since after FW 6.6.0.
Is this just a coincidence or has anything been found by Netgear in the FW related to this?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
