Schulmeister

I have Seagate Exos drives, some are close to 10 yrs old. Things I always do: 1st check if internal cache is enabled 2nd set sleepmode to NEVER 3rd keep the server in a dry, preferably cool environment. My cabinet in the basement is max. 31'C in August and humidity is always betwenn 40 and 45% 4th have a good online UPS, I have lost many devices over faulty power, I buy cyberpower, 40% over the power I need, change the batteries every three years and the device every nine years This way my servers last years without failure.

Conclusion to this topic. Dear Friends, I have been struggeling with that issue for some time and it happened a few times. I thought it was a hardware issue and changed it - same issue after some time. Now I am back on my old hardware, set up a Proxmox Virtualizer and keep Unraid running as follows: 16 Cores, 32GB RAM, a virtual Disk as cachedrive and Flashdrive (Unraid USB Stick) and HDDs passthrough. Unraid - with it's genius Harddrive management is my NAS and my Docker machine. If I need VMs that's where Proxmox has the advantage. That combination runs now without any issues for months and I am very happy. I hope that this helps.

I just tried something else, and as far as I can tell - it worked. I copied the files via SMB on another computer and opened the Images with no problems ? So my pressing needs are solved and I thank you very much for you help. I now am on the task to find out why !!! Why the heck does this happen ? It should not happen, I have ECC Rams, two SSDs (not cheap ones) in a Raid1 and still this errors ? Any ideas ? What shal I do to test my hardware ?

For this do I need to unmount the pool ? How do I do that ?

I was able to copy the contents of the img-file, thanks to this wonderful forum. I figured it out. I needed to specify the byte offset of where the partition begins. For anyone who might have the same question in the future, here is what I did. From the unRAID command console, display partition information of the vdisk: fdisk -l /mnt/disks/Windows/vdisk1.img I was after the values in red. The output will looks something like this: [pre]Disk vdisk1.img: 20 GiB, 21474836480 bytes, 41943040 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xda00352d Device Boot Start End Sectors Size Id Type vdisk1.img1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT vdisk1.img2 206848 41940991 41734144 19.9G 7 HPFS/NTFS/exFAT[/pre] To find the offset in bytes, multiply the sector start value by the sector size to get the offset in bytes. In this case, I wanted to mount vdisk1.img2. 206848 * 512 = 105906176 Final command to mount the vdisk NTFS partition as read-only: mount -r -t ntfs -o loop,offset=105906176 /mnt/disks/Windows/vdisk1.img /mnt/test ********************* I still need to copy the .img-files regardless of errors - is that possible ?

After long hours I found out that the Backup did not work either for quite some time 😞 It is very important that I read the contents of that image ! Can I open it regardless of the errors ? I need these files - sadly

Nov 10 11:04:02 CHUnraidBIG ool www[45170]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '' Nov 10 11:04:02 CHUnraidBIG kernel: BTRFS info (device sdc1): scrub: started on devid 1 Nov 10 11:04:02 CHUnraidBIG kernel: BTRFS info (device sdc1): scrub: started on devid 2 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 445373927424 on dev /dev/sdc1, physical 445373927424, root 5, inode 271, offset 18753646592, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk1.img) Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 445373927424 on dev /dev/sdd1, physical 445352955904, root 5, inode 271, offset 18753646592, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk1.img) Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 20924, gen 0 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 20924, gen 0 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 445373927424 on dev /dev/sdc1 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 445373927424 on dev /dev/sdd1 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 445373931520 on dev /dev/sdc1, physical 445373931520, root 5, inode 271, offset 18753650688, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk1.img) Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 20925, gen 0 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 445373931520 on dev /dev/sdd1, physical 445352960000, root 5, inode 271, offset 18753650688, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk1.img) Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 20925, gen 0 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 445373931520 on dev /dev/sdc1 Nov 10 11:19:26 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 445373931520 on dev /dev/sdd1 Nov 10 11:53:33 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 1475972390912 on dev /dev/sdc1, physical 1475972390912, root 5, inode 272, offset 993067491328, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk2.img) Nov 10 11:53:33 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 20926, gen 0 Nov 10 11:53:33 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 1475972390912 on dev /dev/sdc1 Nov 10 11:55:01 CHUnraidBIG kernel: BTRFS warning (device sdc1): checksum error at logical 1475972390912 on dev /dev/sdd1, physical 1475951419392, root 5, inode 272, offset 993067491328, length 4096, links 1 (path: domains/Windows Server 2019DC/vdisk2.img) Nov 10 11:55:01 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 20926, gen 0 Nov 10 11:55:01 CHUnraidBIG kernel: BTRFS error (device sdc1): unable to fixup (regular) error at logical 1475972390912 on dev /dev/sdd1 Nov 10 12:22:39 CHUnraidBIG kernel: BTRFS info (device sdc1): scrub: finished on devid 1 with status: 0 Nov 10 12:25:27 CHUnraidBIG kernel: BTRFS info (device sdc1): scrub: finished on devid 2 with status: 0

Hi you guys, I have a problem - my VM Disk Images are on the Cachepool. Since yesterday I cannot copy these files to the Array, I get Errors. Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS warning (device sdc1): csum failed root 5 ino 271 off 18753646592 csum 0xcf84ebed expected csum 0x909f2020 mirror 2 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 20910, gen 0 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS warning (device sdc1): csum failed root 5 ino 271 off 18753650688 csum 0xa6f629f1 expected csum 0x8188ffff mirror 2 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 20911, gen 0 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS warning (device sdc1): csum failed root 5 ino 271 off 18753646592 csum 0xcf84ebed expected csum 0x909f2020 mirror 1 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 20910, gen 0 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS warning (device sdc1): csum failed root 5 ino 271 off 18753650688 csum 0xa6f629f1 expected csum 0x8188ffff mirror 1 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS error (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 20911, gen 0 Nov 9 23:25:39 CHUnraidBIG kernel: BTRFS warning (device sdc1): csum failed root 5 ino 271 off 18753646592 csum 0xcf84ebed expected csum 0x909f2020 mirror 2 What shall I do to recover my files ? Diagnostics are attached. Thanks in advance Hanns chunraidbig-diagnostics-20241109-2343.zip

Is there a best practice for CachePools ? I would like to have one very fast cachepool but I need a backup every day. Is the fs important ? My idea is as follows: 1) 4TB m2.nvme as Cachepool (no Raid) (there will be Appdata, System, faster OS-Disks for the VMs and fast cache for Handbrake, Lancache, etc.) 2) 4TB m2.nvme mounted as unassigned device for the nightly backup of that Cachedrive 3) a folder on the Array for a weekly backup of the second (Backup)nvme 4) the important stuff an the Array (these folders included) will be copied an a NAS every Sunday after 3) is finished. I would create a cronjob in the VMs that they will shut down at let's say 2 AM. I would create a userscript that backups all VM-Disks, system and the fastcache folders from nvme1 to nvme2 and restarts the VMs I am using the Plugin Appdata Backup from Robin Kluth for the Backup of the Appdata. Is that a good way to go ? What will be the preferable fs for this operation ? Is there a good backup tool for unraid so that maybe I don't have to undergo all the hassle myself ? How do I setup unraid that the Cachefolders are truly fast (10GB Network speed) I know this is a lot and I have searched the forum multiple times but I never found like a walkthrough for a fast and reliable setup like this. Thanks a lot. PS: If you think it is a good idea to create a new Forumstopic of this question, please feel free to copy this...

That did it - I think. I did as you told me, took every HDD out of that Cachepool (deleting the Cachepool) and put the HDDs in Unassigned Devices - thankfully all files were readable and I copied everything to the array. I had this Cachepool of two HDDs (16TB each) only to speed up read/write operations - it is not the way it's intended, i know. Is there a way to have a Disk/Raid/Pool that can speed up things ? Anyway, as always I am very grateful for the help you provide here - it really makes unraid stand out.

root@RD6:~# sgdisk -o -a 8 -n 1:32K:0 /dev/sdi Creating new GPT entries in memory. The operation has completed successfully. root@RD6:~# btrfs fi show Label: none uuid: 431bb516-355f-42bf-9966-f4413b80ad33 Total devices 2 FS bytes used 1.21TiB devid 1 size 3.64TiB used 1.26TiB path /dev/nvme0n1p1 devid 2 size 3.64TiB used 1.26TiB path /dev/nvme1n1p1 Label: none uuid: c9259cf9-d19a-47b4-987e-42b0f5f82617 Total devices 2 FS bytes used 4.82TiB devid 1 size 14.55TiB used 6.22TiB path /dev/sdc1 devid 2 size 14.55TiB used 6.22TiB path /dev/sdi1 Label: none uuid: e474e21e-688b-4eda-8e90-9177c495d366 Total devices 1 FS bytes used 12.08GiB devid 1 size 894.25GiB used 16.02GiB path /dev/sdh1

I will try this tonite, thanks

Is there any way to get to the Data ?

Hi Jorge, I tried to change the raid1 to single to remove the second drive - well that seemed to cause a problem. It is not that bad as far as there's not very important data on it. The second drive ZL22EVWC is still intact and connected. The PS you wrote is very disturbing: P.S. btrfs is detecting data corruption in multiple pools, xfs also detecting metadata corruption, suggesting you may have an underlying issue: What should i do ?

Hi all, I have a Problem - as usual 🙂 I have a Cachepool with two HDDs running on btrfs, raid1. Usually /mnt/data After an error in the second disk I tried to replace the disk - now everything ist unmountable I tried: root@RD6:~# btrfs rescue super-recover -v /dev/sdc1 All Devices: Device: id = 1, name = /dev/sdc1 Before Recovering: [All good supers]: device name = /dev/sdc1 superblock bytenr = 65536 device name = /dev/sdc1 superblock bytenr = 67108864 device name = /dev/sdc1 superblock bytenr = 274877906944 [All bad supers]: All supers are valid, no need to recover ---------------- root@RD6:~# btrfs check --readonly --force /dev/sdc1 Opening filesystem to check... bad tree block 8152159748096, bytenr mismatch, want=8152159748096, have=0 Couldn't read tree root ERROR: cannot open file system -------------------- btrfs restore --dry-run -d /dev/sdc1 /mnt/disk7/restore/data/ bad tree block 8152159748096, bytenr mismatch, want=8152159748096, have=0 Couldn't read tree root Could not open root, trying backup super bad tree block 8152159748096, bytenr mismatch, want=8152159748096, have=0 Couldn't read tree root Could not open root, trying backup super bad tree block 8152159748096, bytenr mismatch, want=8152159748096, have=0 Couldn't read tree root Could not open root, trying backup super Nothing seems to work. that beeing my third time a "so called" raid filesystems (ZFS and btrfs) failed me I am very disappointed with these things. What is the sense of spending double the money on a security that does not do anything I shall buy myself a NAS and backup everything everyday and stop bothering with btrfs or zfs crap. Thank you all in advance for your time and support. rd6-diagnostics-20240117-1028.zip