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)!
I think it is more efficient if you can read the log :)
https://www.dropbox.com/s/h2ubk4tldk0po4e/systemd-journal.log?dl=0
But please let me know if I should look for anything specific
Started well:
Mar 13 19:26:03 Ultra kernel: md: bind<sdb3> Mar 13 19:26:03 Ultra systemd[1]: Mounted POSIX Message Queue File System. Mar 13 19:26:03 Ultra kernel: md: bind<sdc3> Mar 13 19:26:03 Ultra kernel: md: bind<sdd3> Mar 13 19:26:03 Ultra kernel: md: bind<sda3> Mar 13 19:26:03 Ultra kernel: md/raid:md127: device sda3 operational as raid disk 0 Mar 13 19:26:03 Ultra kernel: md/raid:md127: device sdd3 operational as raid disk 3 Mar 13 19:26:03 Ultra kernel: md/raid:md127: device sdc3 operational as raid disk 2 Mar 13 19:26:03 Ultra kernel: md/raid:md127: device sdb3 operational as raid disk 1 Mar 13 19:26:03 Ultra kernel: md/raid:md127: allocated 4354kB Mar 13 19:26:03 Ultra kernel: md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2 Mar 13 19:26:03 Ultra kernel: RAID conf printout: Mar 13 19:26:03 Ultra kernel: --- level:5 rd:4 wd:4 Mar 13 19:26:03 Ultra kernel: disk 0, o:1, dev:sda3 Mar 13 19:26:03 Ultra kernel: disk 1, o:1, dev:sdb3 Mar 13 19:26:03 Ultra kernel: disk 2, o:1, dev:sdc3 Mar 13 19:26:03 Ultra kernel: disk 3, o:1, dev:sdd3 Mar 13 19:26:03 Ultra kernel: md127: detected capacity change from 0 to 5986292072448
But then... Ouch... I don't want to stress you, but that is not very good.
Mar 13 19:30:40 Ultra kernel: md: md126 stopped.
Mar 13 19:30:40 Ultra kernel: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-hwdb:1338]
Mar 13 19:30:40 Ultra kernel: Modules linked in: vpd(PO)
Mar 13 19:30:42 Ultra kernel: CPU: 0 PID: 1338 Comm: systemd-hwdb Tainted: P O 4.1.30.x86_64.1 #1
Mar 13 19:30:42 Ultra kernel: Hardware name: NETGEAR ReadyNAS/ReadyNAS , BIOS 080016 08/23/2011
Mar 13 19:30:42 Ultra kernel: task: ffff88007bea6e40 ti: ffff880078594000 task.ti: ffff880078594000
Mar 13 19:30:42 Ultra kernel: RIP: 0010:[<ffffffff883d8529>] [<ffffffff883d8529>] _find_next_bit.part.0+0x69/0x70
Mar 13 19:30:42 Ultra kernel: RSP: 0018:ffff8800785975a0 EFLAGS: 00000216
Mar 13 19:30:42 Ultra kernel: RAX: 0000000000004612 RBX: 0000000000000001 RCX: 0000000000000012
Mar 13 19:30:42 Ultra kernel: RDX: 0000000000004612 RSI: fffffffffffc0000 RDI: ffff880078647000
Mar 13 19:30:42 Ultra kernel: RBP: ffff8800785975a8 R08: 800f3cd6de653800 R09: 0000000000000000
Mar 13 19:30:42 Ultra kernel: R10: 0000000000000001 R11: ffff88007c4019c0 R12: 0000000000000001
Mar 13 19:30:42 Ultra kernel: R13: ffff880078597598 R14: 0000000000080000 R15: ffff8800785975f8
Mar 13 19:30:42 Ultra kernel: FS: 00007ff340138740(0000) GS:ffff88007f000000(0000) knlGS:0000000000000000
Mar 13 19:30:42 Ultra kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 13 19:30:42 Ultra kernel: CR2: 00007f3ba07291f8 CR3: 000000007869c000 CR4: 00000000000006f0
Mar 13 19:30:42 Ultra kernel: Stack:
Mar 13 19:30:42 Ultra kernel: ffffffff883d8548 ffff880078597608 ffffffff8832dba1 ffff88007ba94ab2
Mar 13 19:30:42 Ultra kernel: ffff88007c341518 ffff880078597640 ffff880078597638 ffff880078597608
Mar 13 19:30:42 Ultra kernel: 000000000049c000 0000000000001000 ffff88007b852f00 ffff880078597720
Mar 13 19:30:42 Ultra kernel: Call Trace:
Mar 13 19:30:42 Ultra kernel: [<ffffffff883d8548>] ? find_next_bit+0x18/0x20
Mar 13 19:30:42 Ultra kernel: [<ffffffff8832dba1>] search_bitmap.isra.32+0x91/0x120
Mar 13 19:30:42 Ultra kernel: [<ffffffff8833077c>] btrfs_find_space_for_alloc+0xec/0x250
Mar 13 19:30:42 Ultra kernel: [<ffffffff882d403d>] find_free_extent.isra.90+0x35d/0xb20
Mar 13 19:30:42 Ultra kernel: [<ffffffff882d48b3>] btrfs_reserve_extent+0xb3/0x150
Mar 13 19:30:42 Ultra kernel: [<ffffffff882ee5bc>] cow_file_range+0x14c/0x4c0
Mar 13 19:30:42 Ultra kernel: [<ffffffff882ef86a>] run_delalloc_range+0x36a/0x3f0
Mar 13 19:30:42 Ultra kernel: [<ffffffff8830656c>] writepage_delalloc.isra.42+0xec/0x160
Mar 13 19:30:42 Ultra kernel: [<ffffffff88308d2f>] __extent_writepage+0xaf/0x260
Mar 13 19:30:42 Ultra kernel: [<ffffffff88309212>] extent_write_cache_pages.isra.36.constprop.53+0x332/0x400
Mar 13 19:30:42 Ultra kernel: [<ffffffff883097a8>] extent_writepages+0x48/0x60
Mar 13 19:30:42 Ultra kernel: [<ffffffff882eb190>] ? btrfs_update_inode_item+0x120/0x120
Mar 13 19:30:42 Ultra kernel: [<ffffffff882e9b03>] btrfs_writepages+0x23/0x30
Mar 13 19:30:42 Ultra kernel: [<ffffffff880f6929>] do_writepages+0x19/0x40
Mar 13 19:30:42 Ultra kernel: [<ffffffff880edb31>] __filemap_fdatawrite_range+0x51/0x60
Mar 13 19:30:42 Ultra kernel: [<ffffffff880edbd7>] filemap_flush+0x17/0x20
Mar 13 19:30:42 Ultra kernel: [<ffffffff882f5a1c>] btrfs_rename2+0x30c/0x6d0
Mar 13 19:30:42 Ultra kernel: [<ffffffff883757b7>] ? security_inode_permission+0x17/0x20
Mar 13 19:30:42 Ultra kernel: [<ffffffff88137cfa>] vfs_rename+0x53a/0x7e0
Mar 13 19:30:42 Ultra kernel: [<ffffffff8813c941>] SyS_renameat2+0x4c1/0x560
Mar 13 19:30:42 Ultra kernel: [<ffffffff88112c89>] ? vma_rb_erase+0x129/0x230
Mar 13 19:30:42 Ultra kernel: [<ffffffff8813ca09>] SyS_rename+0x19/0x20
Mar 13 19:30:42 Ultra kernel: [<ffffffff88a520d7>] system_call_fastpath+0x12/0x6a
Mar 13 19:30:42 Ultra kernel: Code: 66 90 48 83 c2 40 48 39 c2 73 1f 49 89 d0 4c 89 c9 49 c1 e8 06 4a 33 0c c7 74 e7 f3 48 0f bc c9 48 01 ca 48 39 d0 48 0f 47 c2 5d <c3> 66 0f 1f 44 00 00 48 39 d6 48 89 f0 76 11 48 85 f6 74 0c 55
Mar 13 19:30:42 Ultra kernel: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-hwdb:1338]
Mar 13 19:30:42 Ultra kernel: Modules linked in: vpd(PO)
Mar 13 19:30:43 Ultra kernel: CPU: 0 PID: 1338 Comm: systemd-hwdb Tainted: P O L 4.1.30.x86_64.1 #1
Mar 13 19:30:43 Ultra kernel: Hardware name: NETGEAR ReadyNAS/ReadyNAS , BIOS 080016 08/23/2011
Mar 13 19:30:43 Ultra kernel: task: ffff88007bea6e40 ti: ffff880078594000 task.ti: ffff880078594000
Mar 13 19:30:43 Ultra kernel: RIP: 0010:[<ffffffff883d8529>] [<ffffffff883d8529>] _find_next_bit.part.0+0x69/0x70
Mar 13 19:30:43 Ultra kernel: RSP: 0018:ffff8800785975a0 EFLAGS: 00000202
Mar 13 19:30:43 Ultra kernel: RAX: 00000000000030f0 RBX: 0000000000000001 RCX: 0000000000000030
Mar 13 19:30:43 Ultra kernel: RDX: 00000000000030f0 RSI: fffffe0000000000 RDI: ffff880078643000
Mar 13 19:30:43 Ultra kernel: RBP: ffff8800785975a8 R08: 000f00f000000000 R09: 0000000000000000
Mar 13 19:30:43 Ultra kernel: R10: 0000000000000001 R11: ffff88007c4019c0 R12: 0000000000000001
Mar 13 19:30:43 Ultra kernel: R13: ffff880078597598 R14: 0000000000080000 R15: ffff8800785975f8
Mar 13 19:30:43 Ultra kernel: FS: 00007ff340138740(0000) GS:ffff88007f000000(0000) knlGS:0000000000000000
Mar 13 19:30:43 Ultra kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 13 19:30:43 Ultra kernel: CR2: 00007f3ba07291f8 CR3: 000000007869c000 CR4: 00000000000006f0
Mar 13 19:30:43 Ultra kernel: Stack:
Mar 13 19:30:43 Ultra kernel: ffffffff883d8548 ffff880078597608 ffffffff8832dba1 ffff88007ba94ab2
Mar 13 19:30:43 Ultra kernel: ffff88007c345618 ffff880078597640 ffff880078597638 ffff880078597608
Mar 13 19:30:43 Ultra kernel: 000000000049c000 0000000000001000 ffff88007b852280 ffff880078597720
Mar 13 19:30:43 Ultra kernel: Call Trace:
Mar 13 19:30:43 Ultra kernel: [<ffffffff883d8548>] ? find_next_bit+0x18/0x20
Mar 13 19:30:43 Ultra kernel: [<ffffffff8832dba1>] search_bitmap.isra.32+0x91/0x120
Mar 13 19:30:43 Ultra kernel: [<ffffffff8833077c>] btrfs_find_space_for_alloc+0xec/0x250
Mar 13 19:30:43 Ultra kernel: [<ffffffff882ca8da>] ? btrfs_put_block_group+0x1a/0x70
Mar 13 19:30:43 Ultra kernel: [<ffffffff882d403d>] find_free_extent.isra.90+0x35d/0xb20
Mar 13 19:30:43 Ultra kernel: [<ffffffff882d48b3>] btrfs_reserve_extent+0xb3/0x150
Mar 13 19:30:43 Ultra kernel: [<ffffffff882ee5bc>] cow_file_range+0x14c/0x4c0
Mar 13 19:30:43 Ultra kernel: [<ffffffff882ef86a>] run_delalloc_range+0x36a/0x3f0
Mar 13 19:30:43 Ultra kernel: [<ffffffff8830656c>] writepage_delalloc.isra.42+0xec/0x160
Mar 13 19:30:43 Ultra kernel: [<ffffffff88308d2f>] __extent_writepage+0xaf/0x260
Mar 13 19:30:43 Ultra kernel: [<ffffffff88309212>] extent_write_cache_pages.isra.36.constprop.53+0x332/0x400
Mar 13 19:30:43 Ultra kernel: [<ffffffff883097a8>] extent_writepages+0x48/0x60
Mar 13 19:30:43 Ultra kernel: [<ffffffff882eb190>] ? btrfs_update_inode_item+0x120/0x120
Mar 13 19:30:43 Ultra kernel: [<ffffffff882e9b03>] btrfs_writepages+0x23/0x30
Mar 13 19:30:43 Ultra kernel: [<ffffffff880f6929>] do_writepages+0x19/0x40
Mar 13 19:30:43 Ultra kernel: [<ffffffff880edb31>] __filemap_fdatawrite_range+0x51/0x60
Mar 13 19:30:43 Ultra kernel: [<ffffffff880edbd7>] filemap_flush+0x17/0x20
Mar 13 19:30:43 Ultra kernel: [<ffffffff882f5a1c>] btrfs_rename2+0x30c/0x6d0
Mar 13 19:30:43 Ultra kernel: [<ffffffff883757b7>] ? security_inode_permission+0x17/0x20
Mar 13 19:30:43 Ultra kernel: [<ffffffff88137cfa>] vfs_rename+0x53a/0x7e0
Mar 13 19:30:43 Ultra kernel: [<ffffffff8813c941>] SyS_renameat2+0x4c1/0x560
Mar 13 19:30:43 Ultra kernel: [<ffffffff88112c89>] ? vma_rb_erase+0x129/0x230
Mar 13 19:30:43 Ultra kernel: [<ffffffff8813ca09>] SyS_rename+0x19/0x20
Mar 13 19:30:43 Ultra kernel: [<ffffffff88a520d7>] system_call_fastpath+0x12/0x6a
Mar 13 19:30:43 Ultra kernel: Code: 66 90 48 83 c2 40 48 39 c2 73 1f 49 89 d0 4c 89 c9 49 c1 e8 06 4a 33 0c c7 74 e7 f3 48 0f bc c9 48 01 ca 48 39 d0 48 0f 47 c2 5d <c3> 66 0f 1f 44 00 00 48 39 d6 48 89 f0 76 11 48 85 f6 74 0c 55
Mar 13 19:30:43 Ultra kernel: INFO: rcu_sched self-detected stall on CPU { 0} (t=60000 jiffies g=1100 c=1099 q=3948)
[snip]
Mar 13 19:30:52 Ultra kernel: Code: 0f 1f 84 00 00 00 00 00 48 89 d0 48 8b 50 10 48 85 d2 75 f4 5d c3 66 90 48 8b 10 48 89 c7 48 89 d0 48 83 e0 fc 74 ed 48 3b 78 08 <74> eb 5d c3 31 c0 5d c3 0f 1f 44 00 00 55 48 8b 17 48 89 e5 48
Mar 13 19:30:52 Ultra systemd[1]: systemd-hwdb-update.service: Processes still around after final SIGKILL. Entering failed mode.
Mar 13 19:30:52 Ultra systemd[1]: Failed to start Rebuild Hardware Database.Full extract: http://pastebin.com/wfS7EcmX
I honestly don't know how you can proceed without the help of NETGEAR Support (or how to help you to safely proceed further).
Ok, that doesn´t sound to good :( Thanks for looking into it at least
I´ll wait and see it mdgm-ntgr answer my pm.
Since this issue is something that seems to have increased in the later FW Netgear might have a clue.
I hope that this is not a bug in their FW, then my next NAS will be another brand for sure....
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
