October 9, 20187 yr Post-fix edit: BTRFS cache drive corrupted. Read-only mounted, copied data to another disk, formatted, copied data back, shares etc work again. Just did an upgrade on my main system/array, was running 100% fine on 6.4.0 6.4.1 from memory, stopped array and ran upgrade to 6.6.1 from "Update OS" in tools, rebooted server and booted into 6.6.1 successfully, however there are now no user shares (shows "There are no exportable user shares"). The share folders and all data/files seems to still be available on the disks, all dockers and VMs still listed though most will not start. After looking at threads from others having same/similar problem, can confirm netstats plugin is not installed. Running XFS for array and BTRFS for single 500GB cache drive, 3x Ironwolf 10TB (1x parity), 1x Ironwolf 8TB, 1x Ironwolf 10TB unused (to preclear later and add to array). I did do a full unRAID flash drive image backup prior to upgrade so have that going for me.. but would rather just get 6.6.1 working if I can. Any help would be greatly appreciated. unnas-diagnostics-20181009-2020.zip Sys Specs: i5-8400 Gigabyte Z370M D3H 32GB DDR4 LSI 9211-8i in IT mode ROG Aerion 10GBase-T card (local 10Gb network to single workstation only) Edited October 9, 20187 yr by Virtike added specs
October 9, 20187 yr Community Expert Cache filesystem is corrupt, see here if you need help backing it up before reformatting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
October 9, 20187 yr Author 24 minutes ago, johnnie.black said: Cache filesystem is corrupt, see here if you need help backing it up before reformatting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 Thanks for the reply, upgrading could corrupt the cache drive? That's comforting. Would the corrupt cache cause the shares to not show up in unraid, or are there problems possibly further than this once fixed? Curiously, everything was fine before attempting the move to 6.6.1. Have managed to mount read-only and have started copying files to second disk, there's an entire share/folder that I can't access ("Input/output error"), which is annoying as contains configs/passwords for various things, and a couple other files in other shares too. Most important stuff backed up, but would be good to get it all back. Edited October 9, 20187 yr by Virtike
October 9, 20187 yr Community Expert 44 minutes ago, Virtike said: Thanks for the reply, upgrading could corrupt the cache drive? No.
October 9, 20187 yr Community Expert 45 minutes ago, Virtike said: there's an entire share/folder that I can't access ("Input/output error") Try the second option on the link I posted, btrfs restore.
October 9, 20187 yr Author 3 hours ago, johnnie.black said: Try the second option on the link I posted, btrfs restore. btrfs restore doesn't work, gets a little way through and seemingly hangs (pauses midway through filepath output), tried a couple times, doesn't stop on just one file in particular, though seems to always be in the appdata region. Anyway, was able to read-only mount & recover most data off the disk onto an external drive mounted with Unassigned Devices (plus spare copy on unused 10TB). Formatted the cache drive (with XFS this time, no trim but i'd rather not deal with corruption again so we'll see how it goes..), mounted in UD and copied everything back over from the external drive. Used cp -a to preserve appdata perms so hopefully that isn't an issue, but as it stands the array is back up and all the shares have reappeared again. Dockers/VMs all appear to work okay too. Cheers for the help, will be setting up cache backups from now on.. Edited October 9, 20187 yr by Virtike
October 9, 20187 yr Community Expert 1 minute ago, Virtike said: Cheers for the help You're welcome. 2 minutes ago, Virtike said: with XFS this time, no trim XFS also supports trim, only reiserfs doesn't.
October 9, 20187 yr Author 1 minute ago, johnnie.black said: XFS also supports trim, only reiserfs doesn't. Ahh, sweet. Even better.
Archived
This topic is now archived and is closed to further replies.