RN214 Volume gone after upgrade from 6.9.1 to 6.9.2

[bastelspezi]

Hi Forum Members,

I need your help.

yesterday I updated 2 of my 3 RN214 NAS to  the new firmware 6.9.2. and the one I had a RAID volume on it, cant build its volume no longer. I got 4 RED drives in die GUI now. the volume is gone. I tried rebooting and also went back to firmware 6.9.1 with no effect. the boot time seems also very slow. until I have access to the GUI it takes around 7minutes.

The drives seem all fine

the root isnt full

I cant find any btrfs failurs,

but about here ends my knowledge after reading thru the forum posts

I have a full log download, would love to send it to a specialist here.

the name "mdgm" keeps coming up, should I PM the log there?

Thanks guys!

Chris

[acraigl]

I had the same issue. For me it was a bad disk. You can read that thread here:

https://community.netgear.com/t5/New-to-ReadyNAS/Encountered-issue-with-6-9-2/m-p/1491598/highlight/...

While I was able to downgrade to 6.9.1 and see my shares again, the system remained in a degraded state. When I added a new drive (net new, 4th bay), and it completed syncing, it took the bad drive (bay 3) out of the mix (still installed, but no longer showed in the volumes page). Meaning that it must have identified it as bad and once there was enough storage present, removed it automatically. That actually kind of impressed me. I've since added another drive, and all 4 are now green.

I sugggest you download the logs, and see if there are any smart errors, as described in the thread, if you haven't already.

[bastelspezi]

thanks!

yeah, Ive actually read your thread ealier already, but all my drives seem fine, nothing like your one drive failing and also downgrading to 6.9.1. didnt bring the volume back. so its gotta be something else

[mdgm-ntgr]

You can send me your logs if you like (see the Sending Logs link in my sig).

[mdgm-ntgr]

bastelspezi your volume is encrypted. Is the USB key with the encryption key connected? The volume can't be mounted without this.

[bastelspezi]

yes of course. meanwhile I removed one of the harddrives just to see what would happen and it mounted the volume again. but obviously degraded. i backuped a few things off of it. and later installed a new harddrive in slot 4. then it resynced. it said it was successful, but the volume is messed up. I got now a lot of btrfs errors in the log files. it says the snapshots use 0GB of space but they are all there. but I cant delete them from the GUI. I think because the volume is apparently in read only. I also cant write onto it. I'm doing a scrub right now but i think thats making it all worse.

I have log files of every stage of the progress now.

I would really like to know how this all happend in the first place.

[Wed Jan 31 13:23:05 2018] BTRFS error (device dm-0): bad tree block start 17138530076113243935 17928296660992
[Wed Jan 31 13:23:05 2018] BTRFS error (device dm-0): bad tree block start 17138530076113243935 17928296660992
[Wed Jan 31 13:23:05 2018] BTRFS error (device dm-0): bad tree block start 17138530076113243935 17928296660992
[Wed Jan 31 13:23:18 2018] btree_readpage_end_io_hook: 14 callbacks suppressed
[Wed Jan 31 13:23:18 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:23:18 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:23:51 2018] md: requested-resync of RAID array md127
[Wed Jan 31 13:23:51 2018] md: minimum _guaranteed_ speed: 30000 KB/sec/disk.
[Wed Jan 31 13:23:51 2018] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for requested-resync.
[Wed Jan 31 13:23:51 2018] md: using 128k window, over a total of 5855672832k.
[Wed Jan 31 13:23:53 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:23:53 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:31 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:31 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:32 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:24:35 2018] nr_pdflush_threads exported in /proc is scheduled for removal
[Wed Jan 31 13:30:19 2018] btree_readpage_end_io_hook: 14 callbacks suppressed
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232
[Wed Jan 31 13:30:19 2018] BTRFS error (device dm-0): bad tree block start 5252102582698494194 17928298463232

[mdgm-ntgr]

Do you have logs downloaded from closer to when the problem started?

It does look like there's some fs corruption.

Do you have a backup?

smart_history.log and disk_info.log show command timeouts on a few of your disks.

[bastelspezi]

i've sent you the log file from right after the problem started (the one you have) I dont have anything from ealier since there was no problem.

i do have backup.

The timeouts  showed up ever since I set up the system, didnt seem to affect anything. I posted about this issue 2years ago, I was referred to the compatability list. yikes. the timeouts seemed to not increase anymore once I had set the disk sleeptime to at least 45min.

thanks so much for your effort!

I realize the volume is pretty full.

I never did any scrubbing or defragmenting.  I only ever did disk checks once a month

[bastelspezi]

so just as a follow up. I endend up doing  a factory reset. lost some data but hey what to do. at least it got me to now putting a better backup plan in place.

the data in the end was completly corrupted. nobody here could help me figur out what the problem was, how it came to be or how to fix it.

all HDDs were and are in good shape! so i dont know what it was.

for everyone out there. good luck to you!!