josephsiu

Thank you so much, @JorgeB! You saved me so many many hours.

root@Delta:~# btrfs rescue zero-log /dev/sdb1 Clearing log on /dev/sdb1, previous log_root 2961845878784, level 0 It is back! I'm going to copy the data out now! Should I reset and format the pool and basically start over? What is the usual cause of log tree issues? I'm going to run SMART test on these SSDs as well. For my learning, in which file did you see the log tree error in the diagnostic?

Here is the new diagnotics delta-diagnostics-20230823-1041.zip

Didn't work. It says Auto which I thought might have been a problem but it is grayed out so I cannot change it.

Here it is! ---------------- root@Delta:~# sfdisk /dev/nvme0n1 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/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 970 EVO Plus 2TB 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 0x2340b07d. Created a new partition 1 of type 'Linux' and of size 1.8 TiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: N /dev/nvme0n1p1 : 2048 3907029167 (1.8T) Linux /dev/nvme0n1p2: write New situation: Disklabel type: dos Disk identifier: 0x2340b07d Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 3907029167 3907027120 1.8T 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@Delta:~# btrfs fi show Label: none uuid: f2eaaf1e-021f-4d72-9fb1-39333caf8e61 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/md1p1 Label: none uuid: 6c8567c5-6e83-4044-86fc-b0f9aa64bc33 Total devices 1 FS bytes used 9.08TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md2p1 Label: none uuid: 74f12617-8f88-45ea-8e43-1977b282e953 Total devices 1 FS bytes used 9.06TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md3p1 Label: none uuid: 406ed446-dc92-4112-b9d9-a7bad4b7cc10 Total devices 1 FS bytes used 99.79GiB devid 1 size 3.64TiB used 106.02GiB path /dev/sdf1 Label: none uuid: ea9eeecc-e314-48dc-970e-90bd2449db01 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/sdd1 Label: none uuid: 829aff6c-8b5e-4387-a2b1-c0c3d81f185c Total devices 1 FS bytes used 532.47GiB devid 1 size 1.36TiB used 593.24GiB path /dev/sdc1 Label: none uuid: 167d508b-3822-4e67-8cf8-3e2ea48529e5 Total devices 2 FS bytes used 768.59GiB devid 2 size 1.82TiB used 774.03GiB path /dev/sdb1 devid 4 size 1.82TiB used 774.03GiB path /dev/nvme0n1p1 ----------------

Here are the results: -------------- root@Delta:~# sfdisk /dev/sdb 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/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 870 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 0x6ea176be. Created a new partition 1 of type 'Linux' and of size 1.8 TiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: N /dev/sdb1 : 2048 3907029167 (1.8T) Linux /dev/sdb2: write New situation: Disklabel type: dos Disk identifier: 0x6ea176be Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 3907029167 3907027120 1.8T 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@Delta:~# btrfs fi show Label: none uuid: f2eaaf1e-021f-4d72-9fb1-39333caf8e61 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/md1p1 Label: none uuid: 6c8567c5-6e83-4044-86fc-b0f9aa64bc33 Total devices 1 FS bytes used 9.08TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md2p1 Label: none uuid: 74f12617-8f88-45ea-8e43-1977b282e953 Total devices 1 FS bytes used 9.06TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md3p1 warning, device 4 is missing Label: none uuid: 406ed446-dc92-4112-b9d9-a7bad4b7cc10 Total devices 1 FS bytes used 99.79GiB devid 1 size 3.64TiB used 106.02GiB path /dev/sdf1 Label: none uuid: ea9eeecc-e314-48dc-970e-90bd2449db01 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/sdd1 Label: none uuid: 829aff6c-8b5e-4387-a2b1-c0c3d81f185c Total devices 1 FS bytes used 532.47GiB devid 1 size 1.36TiB used 593.24GiB path /dev/sdc1 Label: none uuid: 167d508b-3822-4e67-8cf8-3e2ea48529e5 Total devices 2 FS bytes used 768.59GiB devid 2 size 1.82TiB used 774.03GiB path /dev/sdb1 *** Some devices missing -------------- I see sdb now in the last command! Is there hope? In the unassigned devices it looks like it is mountable but I'll wait for guidance. Am I correct to assume that I can mount it and copy the data out?

Here are the results; I said no for now: root@Delta:~# sfdisk /dev/sdb 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/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 870 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 0xdd4dbb34. Created a new partition 1 of type 'Linux' and of size 1.8 TiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:

I didn't actively trigger the wipe on the drive, but maybe a moot point now. Here is the output: root@Delta:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 970 EVO Plus 2TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The unassigned drive that was part of the pool was "sdb" (Samsung SSD 870 2TB). I tried to add it back to the pool but of course I was warned that it would be wiped if I tried.

Label: none uuid: f2eaaf1e-021f-4d72-9fb1-39333caf8e61 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/md1p1 Label: none uuid: 6c8567c5-6e83-4044-86fc-b0f9aa64bc33 Total devices 1 FS bytes used 9.08TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md2p1 Label: none uuid: 74f12617-8f88-45ea-8e43-1977b282e953 Total devices 1 FS bytes used 9.06TiB devid 1 size 9.09TiB used 9.09TiB path /dev/md3p1 Label: none uuid: 406ed446-dc92-4112-b9d9-a7bad4b7cc10 Total devices 1 FS bytes used 99.79GiB devid 1 size 3.64TiB used 106.02GiB path /dev/sdf1 Label: none uuid: ea9eeecc-e314-48dc-970e-90bd2449db01 Total devices 1 FS bytes used 12.71TiB devid 1 size 12.73TiB used 12.73TiB path /dev/sdd1 Label: none uuid: 829aff6c-8b5e-4387-a2b1-c0c3d81f185c Total devices 1 FS bytes used 532.47GiB devid 1 size 1.36TiB used 593.24GiB path /dev/sdc1

Hi folks, I was wondering if I could get some help recovering my "appdata" folder from my cache pool. I had 2 SDD (one NVME and one 2.5") in a RAID1. Everything was working fine but then my dockers went offline so I rebooted and my cache pool was showing unmountable. The file system is BTRFS. I unassigned one of the drives (not sure why in retrospect) and restarted the array and now I get this: I'm attaching my diagnostic and tried a bunch of commands from various topic but not really sure what I'm doing. Here are some of the errors I get back. ----------- root@Delta:~# mount -o rescue=all,ro /dev/nvme0n1 /temp mount: /temp: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. ----------- root@Delta:~# btrfs rescue zero-log /dev/nvme0n1 No valid Btrfs found on /dev/nvme0n1 ERROR: could not open ctree ----------- root@Delta:~# btrfs restore -v /dev/nvme0n1 /mnt/disks/WD-WCAZA9724880/restore No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super ----------- Any chance I might be able to save the folder data so I don't have to reconfigure it all? I did not backup as a very poor decision which has led me to this particular place. I appreciate your help! delta-diagnostics-20230820-2319.zip

Hi All, I am a newbie to this and Radarr has been working fine for a while. In fact, it looks like it still might be working? However, I am not able to access WebUI. I'd like to post some logs here for diagnosis, but how do I go about doing that? I saw one person here with the same problem, but not sure if it is. When I try to load the WebUI, the browser just says it is taking too long. I haven't done much to Radarr; it does its thing via Overseerr so I haven't paid any attention to it. Thank you!

Did anyone managed to get SUDO_PASSWORD_HASH working? I'm using the same instruction as HASHED_PASSWORD (different password). The hashed password worked but I was not able to sudo. It kept saying my password was wrong. Method: echo -n "thisismypassword" | npx argon2-cli -e I was able to set a sudo password plaintext by using SUDO_PASSWORD but I would like to hash it.