February 2, 20233 yr I've just migrated to a new server (an Optiplex 7060 Micro). All has gone well so far in terms of getting Unraid booted up, but I can't run Docker. When I look in Docker settings, I'm seeing "Path does not exist" for /mnt/user/appdata/ and /mnt/user/system/docker/docker/. I'm wondering if its an issue with the Flash drive, though I can see its online. Any ideas? server-diagnostics-20230202-1342.zip
February 2, 20233 yr Community Expert 9 minutes ago, Nuuki said: /mnt/user/system/docker/docker/ This is not a valid image path, browse for it, possibly /mnt/user/system/docker/docker.img
February 2, 20233 yr Author So it looks like my cache drive isn't showing up. I previously had a RAID1 pool made up to dual SATA SSDs - I split that pool (as I only have a single SATA in the 7060) and confirmed it was booting fine in the old server - I intended to recreate the pool using an M.2 drive as the secondary. I'll check whether I'm seeing the SATA SSD in the BIOS, though I'm pretty sure I was. If that's the case, not sure why Unraid isn't seeing it now.
February 2, 20233 yr Author OK - some progress. It loosk like the SATA drive wasn't deated properly. I've done that, though now it won't auto boot via USB. I'll come back to that as I can manually select USB. Unraid is now showing me the original SATA cache drive, but its not mounting it, and it says "Add existing data on this device will be overwritten when array is Started". Is there a way I can have it mount it as the existing cache without touching it?
February 2, 20233 yr Community Expert Solution It's a single pool device now? If yes, unassign all pool devices, start array, stop array, re-assign the pool device, there will be no "data is going to be deleted" warning now, start array, if there's a valid pool there it will be imported.
February 2, 20233 yr Author From what I can tell its a 0 device pool now - I split the RAID1 cache pool on the old server and confirmed it was working on the single drive, but for some reason having moved everything over the cache pool isn't coming up and its instead offering to let me add the original drive back, but wiping it in the process. Worst case maybe I could mount it as an Unassigned device and copy everything over to a newly created pool using the new M.2 drive, but that seems like it might add some complexity, so if there's a way to re-add the old drive without wiping it that would be my preference.
February 2, 20233 yr Author I realised I hadn't tried your solution - I've just done so and it worked perfectly - many thanks!
February 2, 20233 yr Author @JorgeBLooks like I may have spoken too soon... It looks like when I added the second drive, it added it as RAID0 - I should have double checked that. I stopped the array and now its staying "Unmountable: too many missing/misplaced drives". Seeing a response you provided in another thread I stopped the array, removed both drives from the pool, restarted the array to clear the pool config, then stopped it, added the drives back and restarted it, but no luck. I see you can usually convert from RAID0 to RAID1, so if I can get the pool back then I can do that. Worst case if its not salvageable I can fall back on the manual copy.
February 2, 20233 yr Community Expert 17 minutes ago, Nuuki said: It looks like when I added the second drive, it added it as RAID0 2nd device is always added as raid1 by default, please post diags.
February 2, 20233 yr Author Understood - its been a while since I created the original pool so don't recall how I got it to run as RAID1, but I should have double checked. Anyway I've tried adding them back in, and then generated the attach diags. server-diagnostics-20230202-1645.zip
February 2, 20233 yr Community Expert The Samsung 870 EVO appears to be failing, run an extended SMART test and post new diags, at that time also post output of btrfs fi show 2 hours ago, Nuuki said: I previously had a RAID1 pool made up to dual SATA SSDs - I split that pool (as I only have a single SATA in the 7060) Was the other device you are trying to add now part of the pool or a new device you are adding now?
February 2, 20233 yr Author Find attached the updated diags. The output from the command is: Label: none uuid: 6ce62ad6-66d5-4b0e-b758-9dcf26483095 Total devices 1 FS bytes used 1.29GiB devid 1 size 28.64GiB used 2.52GiB path /dev/md1 warning, device 2 is missing Label: none uuid: b5041f3c-3118-401e-8673-8b11b6547171 Total devices 3 FS bytes used 179.74GiB devid 1 size 465.76GiB used 184.03GiB path /dev/sdc1 *** Some devices missing The Samsung 870 is only about 18 months old so annoying if its failed, but I guess they're cheap enough. To clarify, I previously had a RAID1 cache pool made up of two SATA SSDs. I broke the pool and removed the older drive (a Samsung 850), leaving just 1 (the Samsung 870). I migrated that to the new server and installed a new M.2 drive (Lexar), which I intended to add to the pool to get it back to RAID1. If the 870 looks to be failing I'd be happy to just use the Lexar for now, and to pickup a new SATA SSD. server-diagnostics-20230202-1709.zip
February 2, 20233 yr Community Expert SMART test failed so that SSD needs to be replaced, and because of that it's not going to be easy to recover the pool, do you have a backup, or when you removed the other pool device did you disconnect it form the server or just unassigned and started the array?
February 2, 20233 yr Author 22 minutes ago, JorgeB said: SMART test failed so that SSD needs to be replaced, and because of that it's not going to be easy to recover the pool, do you have a backup, or when you removed the other pool device did you disconnect it form the server or just unassigned and started the array? Thanks for confirming. I'll go order a new SATA drive... I unassigned the 850, following the instructions here. I've not touched it since , so if that will still have the cache data on it I could swap that in any try again? I do have my appdata folder fully backed up so if I do end up losing both drives I should be able to recover, though obviously be ideal not to have to go that route. Edited February 2, 20233 yr by Nuuki
February 2, 20233 yr Community Expert 42 minutes ago, Nuuki said: I unassigned the 850, following the instructions here. I've not touched it since This wipes the superblock on the removed device, but if it has remained untouched since it's usually easy to recover, I can post the instructions later if you want.
February 2, 20233 yr Community Expert Connect the old ssd to the server, best to disconnect the other pool devices for now, post new diags at that time.
February 2, 20233 yr Author OK - the 850 is conected but unassigned. I realise I left the M.2 in (also unassigned) - if you need me to remove it I can do so. server-diagnostics-20230202-2032.zip
February 3, 20233 yr Community Expert Post the output of: btrfs-select-super -s 1 /dev/sdc1 and then btrfs fi show
February 3, 20233 yr Author warning, device 1 is missing using SB copy 1, bytenr 67108864 Label: none uuid: 6ce62ad6-66d5-4b0e-b758-9dcf26483095 Total devices 1 FS bytes used 1.29GiB devid 1 size 28.64GiB used 2.52GiB path /dev/md1 warning, device 1 is missing Label: none uuid: b5041f3c-3118-401e-8673-8b11b6547171 Total devices 2 FS bytes used 179.86GiB devid 2 size 465.76GiB used 238.03GiB path /dev/sdc1 *** Some devices missing To confirm, the 850 and (new) Lexar are both installed, but neither are added to the pool - both show up under Unnassigned devices.
February 3, 20233 yr Community Expert Now add the 850 to a pool by itself, leave the Lexar device unassigned for now, pool should have at least two slots and be a new pool, i.e., there should be no "all data on this device will be deleted" warning in front of the device after it has been added, then start the array and post new diags.
February 3, 20233 yr Author Done. I created a new pool with the 850, so the old pool is still listed (though empty). I did get a SMART warning when I added the 850, so fingers crossed its useable enough to get he data onto the new Lexar. EDIT: My Docker containers have all fired up, so it seems to have read the pool data without issue... server-diagnostics-20230203-0924.zip Edited February 3, 20233 yr by Nuuki
February 3, 20233 yr Community Expert Wait for the balance to single device to finish, hopefully it finishes without errors, there was some previous corruption detected on that filesystem: Feb 3 09:23:23 Server kernel: BTRFS info (device sdc1): bdev (efault) errs: wr 0, rd 22, flush 0, corrupt 90, gen 0 Feb 3 09:23:23 Server kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 49, gen 0 Once the balance is done run a scrub, if no errors are found you can then add the Lexar device to the pool.
February 3, 20233 yr Author OK I'm running the scrub now. So I can add the Lexar to the pool - do I need to do anything to enable redundancy on the pool, as that's what I'm after rather than pooled capacity. Also a replacement SATA drive should be with me in the next couple of hours. I assume that once the Lexar is in the pool and mirrored, that I can then simply remove the 850 from the pool, swap the drives and add the new drive? EDIT: OK I've added the drive, and though it initially showed a 1Tb pool that has now dropped to 500Gb, so I assume it is indeed RAID1. The balance is running, so I was planning to let that finish, and then remove the 850 from the pool, freeing up space for the new SATA. If that's not correct let me know, but feels like I'm almost there... Edited February 3, 20233 yr by Nuuki
February 3, 20233 yr Community Expert 24 minutes ago, Nuuki said: EDIT: OK I've added the drive, and though it initially showed a 1Tb pool that has now dropped to 500Gb, so I assume it is indeed RAID1. Yes, by default it will always create a raid1 pool.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.