Endy

Members
  • Posts

    212
  • Joined

  • Last visited

About Endy

  • Birthday January 25

Converted

  • Gender
    Male
  • Location
    Pea Ridge, AR

Recent Profile Visitors

2608 profile views

Endy's Achievements

Explorer

Explorer (4/14)

17

Reputation

  1. 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
  2. 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
  3. 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?
  4. 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?
  5. 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
  6. New diagnostics turtle-diagnostics-20231213-1125.zip
  7. 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.
  8. 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
  9. 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
  10. 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
  11. 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:
  12. 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:
  13. 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:
  14. 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
  15. 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