PhilBarker

I thought as an experiment I'd try removing one of the apps stuck on update, removing the image, and then re-install This seemed to work except now Readarr I think updated but now updates are "not-available"

I'm having this issue also I noticed a week or so ago that a few containers permanently said "apply update" I applied the update, everything seemed to go fine, but then they would still say "apply update" it certainly seems to be updating images - and after the docker run command all completes succesfully UI still shows an update pending if I re-run the update, it pulls the same 5 updated images, reports success - and rinse and repeat this is growing now - it was originally readarr and calibre, now qbittorrentvpn and mediaelch too I've also tried installing the update from the apps page - which does the exact same thing, downloads 5 new images, reports success, still shows update required. My DNS has been set to cloudflare always, but this obviously isn't a DNS issue as it resolves, and isn't a bad checksum issue as there are updated images to pull.. Not sure if there's some other logs I could check somewhere?

So this might be completely unrelated - but I hate not following up on an issue I took a day to have a proper look at my server, there's been some other issues like randomly very slow copying files, even when rsyncing from disk to disk I discovered `top` was showing a massive IO wait.. all the time, causing high CPU usage After trial and error, closing VM's, shutting down docker containers one by one - I discovered this was caused by the file integrity plugin when I had ticked to automatically generate hash's on file creation/change. I turned that off and the IO wait instantly dropped from 60-80 to 0. The whole server feels tons faster now, disk speeds are a lot higher. I had presumed that was a good setting rather than having it churn through everything once a week on a schedule, but obviously not as it sets up a load of inotify tasks and grinds the disks to a halt. Since I've sorted that issue, and rebooted, I've had 3 days now without any problem with the USB stick or the VM's - so I'm not saying they're related but I wonder as there has been loads of people with this issue on the forum and none have actually found a cause for it (unless their USB was actually bad) maybe it's just a side effect of the server basically dying from some other reason.

Well.... this morning same issue with HASS VM - it's dead But looking at logs I didn't have the error about the USB pen and unlicensed Jan 7 06:06:33 Jarvis kernel: br0: port 2(vnet2) entered disabled state Jan 7 06:06:33 Jarvis kernel: device vnet2 left promiscuous mode Jan 7 06:06:33 Jarvis kernel: br0: port 2(vnet2) entered disabled state Jan 7 06:06:34 Jarvis usb_manager: Info: rc.usb_manager vm_action HASS stopped end - Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdd Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdf Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdc Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: nvme0n1 Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdi Jan 7 06:06:54 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sda Jan 7 06:07:02 Jarvis samba-dcerpcd[9932]: [2024/01/07 06:07:02.017455, 0] ../../lib/util/sys_popen.c:80(sys_popenv) Jan 7 06:07:02 Jarvis samba-dcerpcd[9932]: sys_popenv: fork failed: Resource temporarily unavailable Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth983191f) entered disabled state Jan 7 06:10:01 Jarvis kernel: veth8a82458: renamed from eth0 Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth983191f) entered disabled state Jan 7 06:10:01 Jarvis kernel: device veth983191f left promiscuous mode Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth983191f) entered disabled state Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth26a5504) entered blocking state Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth26a5504) entered disabled state Jan 7 06:10:01 Jarvis kernel: device veth26a5504 entered promiscuous mode Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth26a5504) entered blocking state Jan 7 06:10:01 Jarvis kernel: docker0: port 3(veth26a5504) entered forwarding state Jan 7 06:10:02 Jarvis kernel: eth0: renamed from veth849cba1 Jan 7 06:10:02 Jarvis kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth26a5504: link becomes ready Jan 7 07:00:01 Jarvis root: Restarting CA Auto Turbo Mode Jan 7 07:00:01 Jarvis kernel: mdcmd (56): set md_write_method 1 Jan 7 07:00:01 Jarvis kernel: Jan 7 07:16:58 Jarvis emhttpd: spinning down /dev/sda Jan 7 07:30:54 Jarvis kernel: usb 3-1: USB disconnect, device number 2 Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager usb_remove Broadcom_Corp_BCM20702A0_5CF370A921D6 /dev/bus/usb/003/002 003 002 Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager Device Match 003/002 vm: 003 002 Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager Removed 003/002 vm: nostate 003 002 Jan 7 07:30:54 Jarvis kernel: usb 3-1: new full-speed USB device number 5 using xhci_hcd Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager usb_add Broadcom_Corp_BCM20702A0_5CF370A921D6 /dev/bus/usb/003/005 003 005 Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM: chip id 63 Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM: features 0x07 Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM20702A Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried: Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' Jan 7 07:30:54 Jarvis kernel: Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager Add device with more than one interface & connect serial . Jan 7 07:30:54 Jarvis usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Broadcom_Corp_BCM20702A0_5CF370A921D6 /dev/bus/usb/003/005 003 005 port 3-1 Still looks like my bluetooth dongle randomly disconnected though The only other thing I'm finding that seems to be connected is usually a dead docker container. Today was Lidarr I looked at the rebuild-dndc logs and found this /usr/bin/docker run -d --name="binhex-lidarr" --net="container:binhex-qbittorrentvpn" -e UMASK="000" -e PUID="99" -e PGID="100" -e TZ="Europe/London" -v "/mnt/cache/appdata/data":"/data":rw -v "/mnt/user/Music/":"/media":rw -v "/mnt/short_cache/Downloads/Torrents/":"/downloads":rw -v "/mnt/user/appdata/binhex-lidarr":"/config":rw binhex/arch-lidarr 84c7e97f86ddcc9a8a3b6c8fc351e962e358f6138b986f72b93d54fab8e5e101 /usr/bin/docker: Error response from daemon: failed to start shim: start failed: runtime: failed to create new OS thread (have 7 already; errno=11) runtime: may need to increase max user processes (ulimit -u) fatal error: newosproc This occured at 06:05 and the HASS VM crashed 1 minute after

Yeah same here. My server has been up and running for maybe near a year now. I have used powertop for most of that but as you’ve confirmed the auto suspend is set as default anyway. Not had any issues until the last few weeks. Maybe this will solve it maybe it won’t. But if it does it doesn’t explain why it’s suddenly started happening

Hrmmmmmmmm sorry to spam this thread but.... Do you use powertop? I do and.. I checked /sys/module/usbcore/parameters and mine was 2. I'm going to try changing that to -1 - I'm wondering if powertop is making the usb devices suspend when it drops down to a certain c-state

Just remembered I have all syslogs backed up so checked them all Jan 1 06:04:34 Jarvis usb_manager: Info: rc.usb_manager vm_action HASS stopped end - Jan 1 06:05:00 Jarvis emhttpd: Unregistered - flash device error (ENOFLASH7) Jan 1 06:05:01 Jarvis emhttpd: Pro key detected, GUID: 0781-5571-5501-060921121721 FILE: /boot/config/Pro.key Jan 1 06:06:07 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did Jan 1 06:06:07 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did Jan 1 06:06:07 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did Jan 1 06:06:13 Jarvis emhttpd: Unregistered - flash device error (ENOFLASH7) Jan 1 06:06:14 Jarvis emhttpd: Pro key detected, GUID: 0781-5571-5501-060921121721 FILE: /boot/config/Pro.key Jan 1 06:10:31 Jarvis root: Mealie: Could not download icon https://cdn.statically.io/gh/KakersUK/docker-templates/mas Jan 1 06:48:15 Jarvis kernel: usb 7-1: USB disconnect, device number 6 Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager usb_remove Broadcom_Corp_BCM20702A0_5CF370A921D6 /dev/bus/usb Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager Device Match 007/006 vm: 007 006 Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager Removed 007/006 vm: nostate 007 006 Jan 1 06:48:15 Jarvis kernel: usb 7-1: new full-speed USB device number 7 using xhci_hcd Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager usb_add Broadcom_Corp_BCM20702A0_5CF370A921D6 /dev/bus/usb/007 Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM: chip id 63 Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM: features 0x07 Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM20702A Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried: Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd' Jan 1 06:48:15 Jarvis kernel: Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd' Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager Add device with more than one interface & connect serial . Jan 1 06:48:15 Jarvis usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Broadcom_Corp_BCM20702A0_5CF370A9 almost the exact same timing when this happened last week but you can see that my bluetooth dongle disconnected, then reconnected - which is probably why HASS crashes as that device is passed through to the VM So it's almost like all the usb devices disconnect and reconnect. But I have absolutely no clue why

Yeah it's weird. I've had a bunch of bizarre issues on my server over Christmas... resolved all of them by swapping out my network card, finally ditched my pcie sata card for a proper HBA... now have nothing coming up in my syslog except every day I find those and one of my VM's is dead. Weirdly my other VM isn't affected (alpine linux) but the home assistant one crashes, and occasionally I find a few dead docker containers too - all die at the time the syslog shows the flash device errors. I've tried testing the usb stick in a PC and it seems fine, I can't see any errors about usb dropping or anything.

I'm having a very similar issue - only started a few weeks ago Nearly every day I get these errors Jan 6 06:06:40 Jarvis emhttpd: Unregistered - flash device error (ENOFLASH7) Jan 6 06:06:41 Jarvis emhttpd: Pro key detected, GUID: 0781-5571-5501-060921121721 FILE: /boot/config/Pro.key Jan 6 06:07:06 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdf Jan 6 06:07:06 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdc Jan 6 06:07:06 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: nvme0n1 Jan 6 06:07:06 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sdi Jan 6 06:07:06 Jarvis emhttpd: error: device_read_smart, 9579: Cannot allocate memory (12): device_spinup: stream did not open: sda Jan 6 06:07:16 Jarvis kernel: br0: port 2(vnet0) entered disabled state Jan 6 06:07:16 Jarvis kernel: device vnet0 left promiscuous mode Jan 6 06:07:16 Jarvis kernel: br0: port 2(vnet0) entered disabled state Jan 6 06:07:16 Jarvis usb_manager: Info: rc.usb_manager vm_action HASS stopped end - Jan 6 06:07:22 Jarvis emhttpd: Unregistered - flash device error (ENOFLASH7) Jan 6 06:07:23 Jarvis emhttpd: Pro key detected, GUID: 0781-5571-5501-060921121721 FILE: /boot/config/Pro.key Jan 6 06:08:00 Jarvis emhttpd: Unregistered - flash device error (ENOFLASH7) Jan 6 06:08:01 Jarvis emhttpd: Pro key detected, GUID: 0781-5571-5501-060921121721 FILE: /boot/config/Pro.key And my home assistant VM is crashed every morning I don't believe there's anything wrong with the USB pen, it's not very old and other thanit disconnecting around 6am it has no issues. I really don't know what's going on - it seems to fairly consistently happen just after 6am but I can't see anything else running/scheduled around that time

Just to close this off in case anyone else has the same issue in the future This 100% was my problem - the disk must have been formatted in my old server and transferred across without being wiped. It was the only disk with a 1MiB GPT, all the others are 4KiB. So when I formatted from exfs to zfs the size of the disk reported changed. The parity restore worked flawlessly and no lost data. The only other weird issue I had was the file integrity plugin started saying the hash's had changed for most of the files on disk3, again likely because of the GPT. I simply checked the files were ok, then removed the hash's and recalculated. All 4 of my other disks reformatted to ZFS without issues 😄

I'm not sure if the actual script itself supports a blank password, but you can try clicking the edit button next to the password field and changing "required" to no Then click save and you'll be able to continue with the field blank If that doesn't work you can try clicking the remove button next to the password fields, then they won't be passed to the container at all Let me know how you get on!

The only issue here is that folders on a 24tb array can't be moved to a 2tb cache and then back again. I'm going to have a play with https://github.com/SpaceinvaderOne/Unraid_ZFS_Auto_Dataset_Update to see if it can do regular folders on array disks. I believe it can

Thanks, I've kicked off a rebuild - fingers crossed! Your explanation probably makes sense, I had a native ubuntu server before moving to unraid, the disk might have been moved over from there and I forgot to zero it out first.

As per the instructions on the other thread I've tried starting the array with the disk removed. All files seem to be emulated ok, I can access them without issues. Attached new diagnostics with the disk now emulated. Does this mean I'm best just to add the disk back in and let it rebuild it from parity? jarvis-diagnostics-20231212-2129.zip

I've just had this exact same issue - I'm going through moving files off of one disk at a time to the rest of the array, then swapping to ZFS The last disk I changed to ZFS, moved all the files off the next disk onto it, when I stopped the array I got the error saying it was the wrong disk. And checking the disk logs the reported size changed after the ZFS format, but the array config obviously didn't update. Not good! Posted a new thread as I'm currently mid-panic and hoping for some help 😱

I'm having the exact same issue as here - I've been moving data from my xfs disks around, to clear a disk, swapping to zfs All has been going well - done disk 5, 4 and 3 Just moved everything from disk 2 to disk 3, stopped the array to change disk 2 to ZFS and it's warning me that disk 3 is the wrong disk The logs for disk 3 show that the size has changed Dec 6 17:12:18 Jarvis kernel: ata38: SATA max UDMA/133 abar m2048@0xfbc00000 port 0xfbc00180 irq 70 Dec 6 17:12:18 Jarvis kernel: ata38: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 6 17:12:18 Jarvis kernel: ata38.00: ATA-10: WDC WD60EDAZ-11U78B0, 80.00A80, max UDMA/133 Dec 6 17:12:18 Jarvis kernel: ata38.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 6 17:12:18 Jarvis kernel: ata38.00: Features: NCQ-prio Dec 6 17:12:18 Jarvis kernel: ata38.00: configured for UDMA/133 Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] 4096-byte physical blocks Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] Write Protect is off Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] Preferred minimum I/O size 4096 bytes Dec 6 17:12:18 Jarvis kernel: sdh: sdh1 Dec 6 17:12:18 Jarvis kernel: sd 39:0:0:0: [sdh] Attached SCSI disk Dec 6 17:13:20 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 6 17:13:20 Jarvis kernel: mdcmd (4): import 3 sdh 2048 5860521540 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 6 17:13:20 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860521540 Dec 6 17:13:20 Jarvis emhttpd: read SMART /dev/sdh Dec 8 03:20:42 Jarvis emhttpd: spinning down /dev/sdh Dec 8 04:01:47 Jarvis emhttpd: read SMART /dev/sdh Dec 8 22:59:21 Jarvis emhttpd: read SMART /dev/sdh Dec 8 22:59:42 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 8 22:59:42 Jarvis kernel: mdcmd (4): import 3 sdh 2048 5860521540 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 8 22:59:42 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860521540 Dec 8 22:59:42 Jarvis emhttpd: read SMART /dev/sdh Dec 11 06:44:23 Jarvis emhttpd: spinning down /dev/sdh Dec 11 08:08:45 Jarvis emhttpd: read SMART /dev/sdh Dec 11 11:01:58 Jarvis emhttpd: read SMART /dev/sdh Dec 11 11:02:16 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 11 11:02:16 Jarvis kernel: mdcmd (4): import 3 sdh 2048 5860521540 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 11 11:02:16 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860521540 Dec 11 11:02:17 Jarvis emhttpd: read SMART /dev/sdh Dec 11 11:04:18 Jarvis emhttpd: shcmd (352990): /sbin/wipefs -af /dev/sdh Dec 11 11:04:18 Jarvis root: /dev/sdh: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Dec 11 11:04:18 Jarvis root: /dev/sdh: 8 bytes were erased at offset 0x57541e95e00 (gpt): 45 46 49 20 50 41 52 54 Dec 11 11:04:18 Jarvis root: /dev/sdh: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Dec 11 11:04:18 Jarvis emhttpd: writing GPT on disk (sdh), with partition 1 byte offset 32KiB, erased: 0 Dec 11 11:04:18 Jarvis emhttpd: shcmd (352991): sgdisk -Z /dev/sdh Dec 11 11:04:19 Jarvis emhttpd: shcmd (352992): sgdisk -o -a 8 -n 1:32K:0 /dev/sdh Dec 11 11:04:20 Jarvis kernel: sdh: sdh1 Dec 12 20:51:22 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:51:41 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:51:41 Jarvis kernel: mdcmd (4): import 3 sdh 64 5860522532 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 12 20:51:41 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860522532 Dec 12 20:51:42 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:52:18 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:52:18 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:52:22 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:52:22 Jarvis kernel: mdcmd (4): import 3 sdh 64 5860522532 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 12 20:52:22 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860522532 Dec 12 20:52:22 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:53:03 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:53:03 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:53:08 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:53:08 Jarvis kernel: mdcmd (4): import 3 sdh 64 5860522532 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 12 20:53:08 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860522532 Dec 12 20:53:08 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:55:07 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:55:07 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:57:54 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:57:54 Jarvis kernel: mdcmd (4): import 3 sdh 64 5860522532 0 WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ Dec 12 20:57:54 Jarvis kernel: md: import disk3: (sdh) WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ size: 5860522532 Dec 12 20:57:54 Jarvis emhttpd: read SMART /dev/sdh Dec 12 20:58:19 Jarvis emhttpd: WDC_WD60EDAZ-11U78B0_WD-WX22D70KRVPJ (sdh) 512 11721045168 Dec 12 20:58:20 Jarvis emhttpd: read SMART /dev/sdh Yesterday it was reporting as 5860521540 and then after the zfs format it's reporting as 5860522532 but the array config is now saying this is the wrong disk! I am extremely nervous now because there's been a lot of files moved around over the last few days during my zfs conversion, and changing of filesystems. The parity should be fine, but I'd really rather not let it rebuild the disk from parity over what's on there in case I lose everything! Is there any way at all that I can just fix the array config, and tell it that it really is the correct disk and then after it's mounted I can do a parity check? Any help very much appreciated at this point jarvis-diagnostics-20231212-2114.zip

Overview: Support for Docker image mattwebbio/orbital-sync which can synchronise a master pihole container on Unraid to a single or multiple slave pihole instance (either virtualised or physical on Raspberry PI). Docker Hub: https://hub.docker.com/r/mattwebbio/orbital-sync GitHub: https://github.com/mattwebbio/orbital-sync No credit is taken for this excellent application, I spent days trying to find a nice solution without SSH/Rsync capability in the pihole container, this works perfectly as it connects to the admin interface, creates a backup using the inbuilt "teleporter" then imports the backup into the slaves. You can also setup notifications if you want to be notified on success/failure. Expectations: This container will run when started, perform a synchronisation, then wait for x minutes (as specified by a container variable). It will run every x minutes until stopped. 12/9/2023, 11:12:20 PM: ➡️ Signing in to http://192.168.1.xxx/admin... 12/9/2023, 11:12:20 PM: ✔️ Successfully signed in to http://192.168.1.xxx/admin! 12/9/2023, 11:12:20 PM: ➡️ Downloading backup from http://192.168.1.xxx/admin... 12/9/2023, 11:12:20 PM: ✔️ Backup from http://192.168.1.xxx/admin completed! 12/9/2023, 11:12:20 PM: ➡️ Signing in to http://192.168.1.yyy/admin... 12/9/2023, 11:12:20 PM: ✔️ Successfully signed in to http://192.168.1.yyy/admin! 12/9/2023, 11:12:20 PM: ➡️ Uploading backup to http://192.168.1.yyy/admin... 12/9/2023, 11:12:26 PM: ✔️ Backup uploaded to http://192.168.1.yyy/admin! 12/9/2023, 11:12:26 PM: ➡️ Updating gravity on http://192.168.1.yyy/admin... 12/9/2023, 11:12:28 PM: ✔️ Gravity updated on http://192.168.1.yyy/admin! 12/9/2023, 11:12:28 PM: ✔️ Success: 1/1 hosts synced. 12/9/2023, 11:12:28 PM: Waiting 30 minutes... Logs This container logs to stdout. To see the logs you will have to execute the docker logs command. docker logs OrbitalSync or use the logs link from Unraid gui.

Exact same issue here File downloaded - `Samsung_SSD_870_EVO_SVT02B6Q_Win.iso` Followed all 7z commands - cd into ./root/fumagician, chmod +x, run it and get the error that the firmware files aren't in the correct path did anyone manage to fix this?

https://forums.unraid.net/topic/129124-run-keeps-filling-up-due-to-log-file/ This ^^

Just had this issue this morning Seemed to be the Plex container writing a ton of info logs {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-06-10T08:17:17+01:00"} {"level":"info","msg":"Running with config:\n{\n \"AcceptEnvvarUnprivileged\": true,\n \"NVIDIAContainerCLIConfig\": {\n \"Root\": \"\"\n },\n \"NVIDIACTKConfig\": {\n \"Path\": \"nvidia-ctk\"\n },\n \"NVIDIAContainerRuntimeConfig\": {\n \"DebugFilePath\": \"/dev/null\",\n \"LogLevel\": \"info\",\n \"Runtimes\": [\n \"docker-runc\",\n \"runc\"\n ],\n \"Mode\": \"auto\",\n \"Modes\": {\n \"CSV\": {\n \"MountSpecPath\": \"/etc/nvidia-container-runtime/host-files-for-container.d\"\n },\n \"CDI\": {\n \"SpecDirs\": null,\n \"DefaultKind\": \"nvidia.com/gpu\",\n \"AnnotationPrefixes\": [\n \"cdi.k8s.io/\"\n ]\n }\n }\n },\n \"NVIDIAContainerRuntimeHookConfig\": {\n \"SkipModeDetection\": false\n }\n}","time":"2023-06-10T08:17:22+01:00"} it's writing this into log.json over and over until it runs out of space in my case in here /run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/ee915362cd78cd496a851176c392358304b634dd99e244d1700b5c2b825e06dc/log.json I have deleted the log.json file for now and it's recreated it - buys some time I have to go out but when I get back home I'll see if I can work out what's going on

Same issue here - have to restart unraid-api every day

There's a big difference between opening up the plex port for sharing your legally purchased media and opening up the main web port so you can access the unraid admin panel remotely. I'd never even consider doing that - as others have said you can use a VPN for that or personally I use tailscale. The tailscale client installs on my phone, laptop etc... and I can access my unraid admin panel from anywhere securely if I need to (not that I ever have had to). These kind of hacks are usually not that smart and are just scanning IP's looking for an unraid server to respond. If you've only got plex ports open you've not got much to worry about.

I am so confused. So you're no longer using an ASM1166 card - you're using a SAS card. In that case the firmware is irrelevant and if the SAS card isn't detected you have a different issue.

As has been said it's highly unlikely the 8 port card will work as it uses a port multiplier. The very first post in this thread recommends the ASM1166 6 port card. I've linked the one I have and it works fine. Most 6 port ASM1166 cards work fine. And also previously discussed is that the silverrstone firmware applies fine to generic cards, I've upgraded mine, I've even written a blog post about it https://docs.phil-barker.com/posts/upgrading-ASM1166-firmware-for-unraid/ I'm afraid if you ignore all the advice on which card to buy, and buy an 8 port instead of a 6 port, and don't read the previous posts - you're going to continue having bad times

Let me try that again Mzhou SATA Card