Endy

Done. It's passing, but I am concerned because that's 2 read errors (looks like in the same place?) within the last 2-3 weeks. I do not have a lot of experience analyzing smart data, though. Typically when a hard drive has failed for me it's an all at once thing where I just can't pull any data off it whatsoever and/or it's making an awful noise. turtle-smart-20240124-0844.zip

Just thought I should get another opinion, but am I correct that this drive is starting to fail? It would be the first in the array to do so from old age, but it is also probably the most frequently used. turtle-smart-20240122-0700.zip

Thanks again. The new cache pool seems to be working just like it should. There was only one file that couldn't make the move, but other than that, it went smoothly. I am gonna call this problem fixed. Now, can I buy you a beer or coffee or make a donation to your favorite charity to thank you?

Ok, so I am moving the files now. Once done then I can just delete the old pool and no need to worry about re-importing anymore and everything should be fixed?

Ok, new pool created and the array is started. New diagnostics. Do I need to run a balance on the new pool before I attempt to use it? To move the data from the old cache to the new cache, do I just edit each share that is using the old cache and set new cache as primary and old cache as secondary and then run mover? turtle-diagnostics-20231213-1207.zip

New diagnostics turtle-diagnostics-20231213-1125.zip

Hopefully small hiccup... I stopped the array and created a new pool for the 2 new drives and when I tried to start the array I got a message saying "Wrong Pool State cache - too many missing/wrong devices" I didn't touch the original cache pool. I tried deleting the new pool and same message.

Ok, it finished. If I am planning on removing the Crucial drive, do I want/need to add one of the new drives? Just want to make sure I don't mess up again. Also, thank you so much for your help JorgeB. While I wouldn't have lost any irreplaceable data, you have saved me from countless hours recreating and setting everything up. I truly appreciate it. turtle-diagnostics-20231213-0936.zip

It's alive! As far as I can tell, everything seems to be there. Docker started up and seems to be working. Am I out of the woods now? If so, because I plan on just using the 2 new drives for cache and removing the Crucial drive, next step would be to temporarily move all data off of the cache pool? Then delete and recreate the cache pool using just the 2 new drives and then move the data back? turtle-diagnostics-20231213-0735.zip

That worked. /dev/nvme2n1p2: write New situation: Disklabel type: dos Disk identifier: 0xe90b059d Device Boot Start End Sectors Size Id Type /dev/nvme2n1p1 64 1953525167 1953525104 931.5G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@Turtle:~# btrfs fi show Label: none uuid: 849f7ded-6fbb-4f5f-9627-fa781a175567 Total devices 2 FS bytes used 714.96GiB devid 1 size 931.51GiB used 826.48GiB path /dev/sdd1 devid 2 size 931.51GiB used 826.48GiB path /dev/sdb1 Label: none uuid: db14842a-e91c-4154-bdd8-fbe89dfc7ce3 Total devices 1 FS bytes used 340.00KiB devid 1 size 20.00GiB used 536.00MiB path /dev/loop2 Label: none uuid: 6331b51d-add2-421b-a015-22c674718eb5 Total devices 1 FS bytes used 412.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 warning, device 2 is missing Label: none uuid: 9bceeb35-e26e-47d8-9ef3-3534abbaa204 Total devices 2 FS bytes used 383.72GiB devid 1 size 931.51GiB used 884.05GiB path /dev/nvme2n1p1 *** Some devices missing *edited to show the part after 'write' as well

It's not letting me do the save part. Do you want to remove the signature? [Y]es/[N]o: N /dev/nvme2n1p1 : 64 1953525167 (931.5G) Linux /dev/nvme2n1p2: w unsupported command /dev/nvme2n1p2: W unsupported command /dev/nvme2n1p2:

root@Turtle:~# sfdisk /dev/nvme2n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme2n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000P1SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0xe90b059d. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:

root@Turtle:~# sfdisk /dev/nvme2n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme2n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000P1SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0xfc45e933. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme2n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme2n1p2:

root@Turtle:~# fdisk -l /dev/nvme2n1 Disk /dev/nvme2n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000P1SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Turtle:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: WD_BLACK SN850X 2000GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes

root@Turtle:~# fdisk -l nvme2n1 fdisk: cannot open nvme2n1: No such file or directory root@Turtle:~# fdisk -l nvme0n1 fdisk: cannot open nvme0n1: No such file or directory

Label: none uuid: 849f7ded-6fbb-4f5f-9627-fa781a175567 Total devices 2 FS bytes used 714.96GiB devid 1 size 931.51GiB used 826.48GiB path /dev/sdd1 devid 2 size 931.51GiB used 826.48GiB path /dev/sdb1 Label: none uuid: db14842a-e91c-4154-bdd8-fbe89dfc7ce3 Total devices 1 FS bytes used 340.00KiB devid 1 size 20.00GiB used 536.00MiB path /dev/loop2 Label: none uuid: 6331b51d-add2-421b-a015-22c674718eb5 Total devices 1 FS bytes used 412.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 sdd and sdb are part of another btrfs pool not having to do with cache. turtle-diagnostics-20231212-1040.zip

Generally I have a rule that I don't work on things when I am really tired so that I don't make stupid mistakes. Last night I was really tired and ignored that rule and now I am paying the price. I just swapped motherboard/processor/ram for my Unraid server yesterday and that went well. I also added 2 nvme drives to use for my cache pool to replace the 1 nvme drive I had been using so that I would have a little redundancy there. (I know it's not a proper backup, I am actually in the process of setting up a more proper backup system.) I added 1 of the new nvme drives to the cache pool and that seemed fine and it balanced it. This is where I should have stopped and waited until after I had slept. I was impatient and I thought it was a good idea to just swap the old nvme drive for the new one in the gui directly. Bad idea. Btrfs pool now gone. Turned off the server, went to bed, and now here I am the next day. I've tried the restore options in the FAQ up until the last option. Currently I have the original nvme drive and the one I added 1st yesterday in the cache pool like it was when it was working before I made the mistake. I have a feeling that I am screwed, but is there any way to restore from here?

I am leaning towards a supermicro bpn-sas2-846el1 for the backplane, which iirc is the same as what I have in my current server case. Probably only HDD's attached to it, so it should have enough bandwidth I think? Now to refresh my memory on SAS cards so I can find something that will work with this.

I'm looking at the backplane so that it handles the power and data as opposed to hooking up cables to each drive individually. Granted, it would be cheaper to do it in a similar manner to the way he did it in the video. And yes, there will be 3D printing involved.

I have this idea of making a custom case for my server. (Pretty much because the closet it lives in is small and a case made to fit the space can utilize the space so much better to get greater airflow. It might also be a fun project.) I really like the supermicro case and being able to fairly easily plug and unplug the hard drives so I thought using a backplane would be good idea. Not knowing a lot about them, I thought I would ask here for suggestions on what specific models to look at and what kinds of things to look for or avoid. (Such as older models maybe being slower.) Suggestions for a SAS card to go with it would be great too. You may wonder why I don't use the backplane in my current server, and that would be because I plan on using that as my backup server.

Nevermind... I am pretty sure I was going about this the wrong way.

Ok you are asking a lot of questions there and it doesn't really have anything to do with this guide. What I can suggest is that for help with getting your VM working, to post about the problems you are having with your VM xml in the VM help forum. You will get much better answers that way. For help with Duplicati, find the Duplicati docker topic in the Docker Container forum and describe your issues there and see if they can help you. For a torrent docker, there are plenty to choose from. I have no idea about rss support for them, though. I would highly recommend SpaceInvader One's or Ibracorp's youtube channels.

With any board revision, the hardware components can change and the bios can change. So similar either of those boards would be, I can't say.

I know it's been awhile, but I'll answer anyways. I am still running the 2.70 bios. I'm going with the 'if it ain't broke' option for the time being. Thank you for the picture showing the internal usb headers as well. So to your question #1, I can't really answer it because it is a pain to get into my server so I only do that if I really have to and usually if I have to, it means I am in a hurry and forget to check on things like the usb headers. For question #3, I believe that you can? It has been a long time since I have messed around with all of this. Sorry it has taken me so long to get back to you.

For the Bitwarden docker container it's using Custom:br0 with it's own ip and port 80. I have websockets set to true. I'm not sure how to concisely describe the HAProxy setup. The backend points to the ip and port of the bitwarden docker container, encrypt ssl and ssl checks are off. Health check method is http. Frontend is set so that if host starts with bitwarden (ie bitwarden.mydomain.com), it uses the bitwarden backend. It is exactly the same as my other docker containers, but it is the only one that doesn't work. Just error 522 from Cloudflare which apparently means that it's connecting but the request isn't finishing. It seems to be connecting on the local network just fine and I have not made any changes to the configuration inside of Bitwarden.