NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Pro 6 volume loss after resync
I
1) I went on vacation from 2018-08-13 until 2018-08-25, upon my return, the (OS: 6.9.3, BIOS: Flame6-MB 2010-07-26) ReadyNAS Pro 6 NAS (protected by a 1500VA UPS) was inaccessible. Upon reboot the following log entry was found to be the last one:
| Tue Aug 14 2018 7:00:01 | Snapshot: Snapshot c_1534244400 was successfully created for share or LUN shared_files. |
so, it appears the NAS was locked up for about 10 days.
2) Then, resync occured
| Sun Aug 26 2018 4:15:09 | Volume: Volume data is resynced. | |
| Sun Aug 26 2018 0:35:09 | Backup: Error backup job A01 to rnduo Media: Source path cannot be accessed. | |
| Sun Aug 26 2018 0:34:58 | Backup: Successfully completed backup job A02 to rnduo data except Media. | |
| Sat Aug 25 2018 20:57:26 | System: Antivirus scanner definition file was updated to 58.24873. | |
| Sat Aug 25 2018 20:41:29 | System: ReadyNASOS background service started. |
| Sat Aug 25 2018 20:41:06 | Volume: Resyncing started for Volume data. |
| Sat Aug 25 2018 20:38:55 | System: The system is rebooting. | |
| Sat Aug 25 2018 20:34:47 | System: ReadyNASOS background service started. | |
| Sat Aug 25 2018 20:34:25 | Volume: Resyncing started for Volume data. | |
| Sat Aug 25 2018 20:34:21 | System: ReadyNASOS service or process was restarted. |
3) The resync was successful, but the previous shares are not visible, and it appears the data is gone, the backup schedule is not accessible. Each of the four disks show 0 ATA errors.
4) I downloaded the logs.
5) Did I have a backup? Yes, but it got overwritten. - job A01 was my Media files and job A02 was everything else backed up via rsync to a ReadyNAS Duo. A further problem is that during the resync period (Aug 25/26), job A02 completed (scheduled daily at 00:05), erasing my backup on the ReadyNAS Duo, so those files are gone on the healthy backup device. It would be good in future OS6 releases, if backup jobs were prevented from running during a resync.
Any advice would be appreciated.
3 Replies
Replies have been turned off for this discussion
Can you download your logs and send them in please (see the Sending Logs link in my sig)?
The logs have been sent.
This is a data recovery situation. From kernel.log we see.
Aug 28 15:06:47 rnpro kernel: Btrfs loaded, crc32c=crc32c-generic Aug 28 15:06:47 rnpro kernel: BTRFS: device label 540ed803:root devid 1 transid 1169013 /dev/md0 Aug 28 15:06:47 rnpro kernel: BTRFS info (device md0): has skinny extents Aug 28 15:06:49 rnpro kernel: BTRFS: device label 540ed803:data devid 1 transid 361746 /dev/md127 Aug 28 15:06:49 rnpro kernel: BTRFS info (device md127): has skinny extents Aug 28 15:06:49 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:06:49 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:06:49 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:06:49 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:06:49 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:06:49 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:06:49 rnpro kernel: BTRFS error (device md127): open_ctree failed Aug 28 15:11:06 rnpro kernel: BTRFS info (device md127): has skinny extents Aug 28 15:11:06 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:11:06 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:11:07 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:11:07 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:11:07 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:11:07 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:11:07 rnpro kernel: BTRFS error (device md127): open_ctree failed Aug 28 15:23:02 rnpro kernel: BTRFS info (device md127): has skinny extents Aug 28 15:23:02 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:23:02 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:23:02 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:23:03 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:23:03 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 28 15:23:03 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 28 15:23:03 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 28 15:23:03 rnpro kernel: BTRFS error (device md127): open_ctree failed Aug 29 09:36:23 rnpro kernel: Btrfs loaded, crc32c=crc32c-generic Aug 29 09:36:23 rnpro kernel: BTRFS: device label 540ed803:root devid 1 transid 1169102 /dev/md0 Aug 29 09:36:23 rnpro kernel: BTRFS info (device md0): has skinny extents Aug 29 09:36:24 rnpro kernel: BTRFS: device label 540ed803:data devid 1 transid 361746 /dev/md127 Aug 29 09:36:24 rnpro kernel: BTRFS info (device md127): has skinny extents Aug 29 09:36:25 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 29 09:36:25 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 29 09:36:25 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 29 09:36:25 rnpro kernel: BTRFS critical (device md127): corrupt node, bad key order: block=794230784, root=1, slot=309 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): failed to read block groups: -5 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793083904 wanted 361745 found 361747 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 793444352 wanted 361744 found 361747 Aug 29 09:36:25 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): parent transid verify failed on 792395776 wanted 361743 found 361745 Aug 29 09:36:25 rnpro kernel: BTRFS warning (device md127): failed to read tree root Aug 29 09:36:25 rnpro kernel: BTRFS error (device md127): open_ctree failed
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
