martinjuhasz

After every reboot, ZRAM fails to auto-create. The init script tries to reset /dev/zram0, but the kernel already created it when the zram module loaded. The device is empty (disksize=0, not in /proc/swaps), so the reset is unnecessary and fails: [INFO] Creating ZRAM: size=8G, algo=zstd, priority=100 [ERROR] Failed to create ZRAM device: zramctl: /dev/zram0: failed to reset: Device or resource busy Clicking "Create" in the dashboard works fine every time , only the boot-time init fails. When disksize=0 and the device isn't in /proc/swaps, the reset could be skipped. Alternatively zramctl --find would avoid the conflict. Unraid 7.1.3, plugin version 2026.06.17.01, 56 GB RAM. Reproducible on every reboot.

Interesting! What i wonder, how would you keep this updated? Is this a once run and forget here? Does changing nanoclaws code work?

@Holaf facefusion does not work anymore. they changed their entry point python file name and also parameters it seems

ok i replaced those. will monitor the situation

Hello, so my server started throwing CRC errors on different drives. The cache drive especially, where CRC Errors increase by the hour (currently 15). Also i get different kernel warnings in my logs: ata5.00: failed command: READ FPDMA QUEUED ata5: hard resetting link and btrfs errors: BTRFS info (device dm-3): read error corrected: ino 4173238 off 1912832 (dev /dev/mapper/sdg1 sector 314771312) i have no idea what is happening. it doesnt seem like the disk is the problem? What might be the case? Any help greatly appreciated winston-diagnostics-20230905-1058.zip

i've run the board for years in another desktop computer without problems. I'll get some new SATA first and hope for the best. If not, i'll grab another PSU (uhg). We are talking about the SATA Cables (for data), not the power connector to the PSU right? Thanks again for your awesome support Edit: Since both drives failed already at some point, it might be the PSU, damn

@JorgeB sure, thanks! winston-diagnostics-20230322-1210.zip

I've put my disks on different rails on my PSU and also changed connectors just to make sure. Today it happened again. @JorgeB does this look again like a power isse? If it is so, it seems i might need to replace the PSU and see if this (hopefully) resolves it. Mar 22 07:45:09 Winston emhttpd: spinning down /dev/sdc Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:00:02 Winston emhttpd: read SMART /dev/sdc Mar 22 11:00:13 Winston emhttpd: read SMART /dev/sdb Mar 22 11:00:25 Winston kernel: sd 3:0:0:0: [sdd] tag#15 access beyond end of device Mar 22 11:00:25 Winston kernel: I/O error, dev sdd, sector 12915028112 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028048 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028056 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028064 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028072 Mar 22 11:00:25 Winston emhttpd: read SMART /dev/sde Mar 22 11:00:35 Winston kernel: sd 3:0:0:0: [sdd] tag#16 access beyond end of device Mar 22 11:00:35 Winston kernel: I/O error, dev sdd, sector 12915028112 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028048 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028056 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028064 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028072 Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO I'm happy for any hints since this is so hard to debug

ok something weird happened. now disk1 is in error state. That is another disk. which makes me suspicious that these errors are NOT the disks. i've downloaded diagnostics before a reboot this time. any idea what could happen here @JorgeB since now this error is across disks apparently ? winston-diagnostics-20230304-2232.zip

Ah damn, should have grabbed the diag before checking the disk, well. Thanks for your insight. Will start to rebuild on top of it and see if anything is looking good. thanks!

Hello, over night my disk2 came into error state Disk 2 in error state (disk dsbl) - WDC_WD80EZAZ-11TDBA0_JEH74D8M (sde) array has errors - Array has 1 disk with read errors I've checked the drive and it was powered down. these are shucked WD drives where i had to cover this 3rd pin to make it run. i suspect this became loose, but no way to confirm. i used an adapter to fix this issue permantently and the drive works again. I've ran a full SMART extended check which resulted in no errors. So i suspect the drive might not be faulty but just lost power. I'm unsure how to proceed. Should i run a preclear on the drive and if this is ok add it back to the array? How would that work? Stop Array Remove Drive from the Array Start Array Do a preclear on the unassigned drive Stop Array Add Drive again Start Array Any help appriciated. I added the SMART report of said drive2 and my diagnostics file. winston-smart-20230221-0952.zip winston-diagnostics-20230221-0952.zip

ok. thank you so much for your time and help

ok. so i moved files, formatted newly to btrfs encrypted, moved files again. Seems to be normal currently. i ran scrub and balance after moving files back and no errors so far. anything i can do besides that to verify its ok now? might happen over time again right?

oh damn, okay. i might switch back to zfs then. really wanted to avoid doing "manual" local backup with rsync. would you mind elaborating what indicates that its metadata?

Ok, it finished, these are the syslog outputs Nov 4 17:12:12 Winston ool www[15451]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '' Nov 4 17:12:12 Winston kernel: BTRFS info (device dm-3): scrub: started on devid 1 Nov 4 17:12:12 Winston kernel: BTRFS info (device dm-3): scrub: started on devid 2 Nov 4 17:12:52 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Nov 4 17:12:52 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 81550143488 on dev /dev/mapper/sdf1 Nov 4 17:13:34 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Nov 4 17:13:34 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 122435252224 on dev /dev/mapper/sdf1 Nov 4 17:13:35 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Nov 4 17:13:35 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 123201454080 on dev /dev/mapper/sdf1 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 179388588032 on dev /dev/mapper/sdf1 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 179478081536 on dev /dev/mapper/sdf1 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 180374007808 on dev /dev/mapper/sdf1 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 185834225664 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 186957123584 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 13, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 186955014144 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187113508864 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 15, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187287994368 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 16, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187306131456 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187558371328 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: scrub_handle_errored_block: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: btrfs_dev_stat_print_on_error: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 70, gen 0 Nov 4 17:14:01 Winston kernel: scrub_handle_errored_block: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 191955169280 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 71, gen 0 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 191962398720 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 72, gen 0 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 192054423552 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 73, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194658598912 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 74, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194773180416 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 75, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194779500544 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 76, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194793492480 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 77, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194779983872 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 78, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194928234496 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 79, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194943197184 on dev /dev/mapper/sdf1 Nov 4 17:16:46 Winston kernel: scrub_handle_errored_block: 1 callbacks suppressed Nov 4 17:16:46 Winston kernel: btrfs_dev_stat_print_on_error: 1 callbacks suppressed Nov 4 17:16:46 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 81, gen 0 Nov 4 17:16:46 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 801075355648 on dev /dev/mapper/sdf1 Nov 4 17:17:54 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdg1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Nov 4 17:17:54 Winston kernel: scrub_handle_errored_block: 1 callbacks suppressed Nov 4 17:17:54 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 953985130496 on dev /dev/mapper/sdg1 Nov 4 17:18:01 Winston kernel: BTRFS info (device dm-3): scrub: finished on devid 2 with status: 0 Nov 4 17:18:12 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 82, gen 0 Nov 4 17:18:12 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 953985130496 on dev /dev/mapper/sdf1 Nov 4 17:18:30 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 83, gen 0 Nov 4 17:18:30 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 846948855808 on dev /dev/mapper/sdf1 Nov 4 17:19:06 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 84, gen 0 Nov 4 17:19:06 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 861991755776 on dev /dev/mapper/sdf1 Nov 4 17:20:33 Winston emhttpd: spinning down /dev/sdc Nov 4 17:20:42 Winston kernel: BTRFS info (device dm-3): scrub: finished on devid 1 with status: 0 Nov 4 17:21:52 Winston emhttpd: spinning down /dev/sde Nov 4 17:24:41 Winston emhttpd: spinning down /dev/sdd not sure what that means? not any files listet here i tried resolving "logical" with inspect, but this doesnt result in any output, f.e.: btrfs inspect-internal logical-resolve 81550143488 /mnt/cache