Everything posted by ShadowLeague
-
6.12.13 - sluggish UI, video streaming degraded
Hello - Navigating the webui is struggling, regardless of the system I use to access it. A reboot had no effect. When I tried to download the diagnostics, it never started the download. After several minutes, I ssh'd in, copied the diags to a share, and downloaded the zip through the webui. From what I recall, I haven't made any significant changes in the past two weeks, which is around the time I've been experiencing these issues. I'm using Emby and direct streaming of files (those that don't need transcoding) is almost impossible without stuttering. I don't see any failing drives in the array, or any errors. diags.zip
-
[Support] Linuxserver.io - Duplicati
Just installed duplicati and during the first backup, it filled up my array drive. TLDR, it appears to be writing data to the system share, even though nothing is mapped to that folder within the config. To clarify, the backup and source folders are not on the array; only the appdata/duplicati folder is. I'm guessing it's doing some type of a temp folder into system before copying the data over to the backup folder I've specified. anyone else seeing this, and what was the fix?
-
Broadcom / LSI SAS3416 randomly initializes at startup. unRAID 6.12.13
I'm curious with anyone with this card or a SAS3xxx has had issues getting their card to initialize from a reboot or a cold start. This issue prevents unRAID from booting. And it's a random amount of times that it'll work after I turn the PC off and back on. No other hardware in the PC is having similar issues. mobo PRIME H770-PLUS D4, 64GB RAM with latest BIOS (NOV, 2024) Core i5, 12th gen Aside from the above gremlin, the system works as expected.
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
Apologies on the delay. Steps taken: stopped all docker containers by CLI, exported the zpool stopped the array within unRAID UI started the array within unRAID UI The array is mounted within the UI and I can see all the details of it within the ZFS Master plugin. Thank you for the help on this one.
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
I setup a new config for the pool and lined up the drives as the zpool sees them (from zpool status output) and unRAID still stays there are unmountable disks present, and wanting me to format in order to mount the pool. Is there another step I should try?
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
oh man - I overlooked that. I think I'm in a good spot now. I ran the zpool clear and I think everything is good to go. Strange that the UI says I still have unmountable disks, but the zpool is mounted and data is accessible. root@virtunraid:~# zpool clear spinners root@virtunraid:~# zpool status -v pool: spinners state: ONLINE scan: resilvered 213M in 00:00:05 with 0 errors on Sat Oct 12 18:47:02 2024 config: NAME STATE READ WRITE CKSUM spinners ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdf1 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 sdk1 ONLINE 0 0 0 sdl1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 sdb1 ONLINE 0 0 0 sdm1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 sdo1 ONLINE 0 0 0 sdi1 ONLINE 0 0 0 sdp1 ONLINE 0 0 0 sdj1 ONLINE 0 0 0 errors: No known data errors I think the next part is to run a scrub to ensure everything is good.
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
Here's the latest root@virtunraid:~# zpool status pool: spinners state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P scan: resilvered 213M in 00:00:05 with 0 errors on Sat Oct 12 18:47:02 2024 config: NAME STATE READ WRITE CKSUM spinners DEGRADED 0 0 0 raidz2-0 DEGRADED 0 0 0 sdf1 ONLINE 0 13 0 sdd1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 sdk1 ONLINE 0 0 0 sdl1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 sdb1 ONLINE 0 0 0 sdm1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 replacing-9 DEGRADED 0 0 0 sdg1 ONLINE 0 0 0 3500479797208464185 FAULTED 0 0 0 was /dev/sdg1 sdo1 ONLINE 0 0 0 sdi1 ONLINE 0 0 0 sdp1 ONLINE 0 0 0 sdj1 ONLINE 0 0 0 errors: No known data errors With the suggestion from the above output, I can't get them to work root@virtunraid:~# zpool replace spinners sdg1 invalid vdev specification use '-f' to override the following errors: /dev/sdg1 is part of active pool 'spinners' root@virtunraid:~# zpool replace -f spinners sdg1 invalid vdev specification the following errors must be manually repaired: /dev/sdg1 is part of active pool 'spinners' From what I'm reading, I need to: export the pool stop zfs services clear zfs cache import the pool start zfs services I'm just afraid to do these steps without some confirmation that this is the best path to get the pool back to a healthy state.
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
I booted the system back up. Before clicking `start array` I did the zpool import command and it came back with a prompt with no output. But, the pool is seen in the ZFS Master plugin and cli, but not the pool in the UI. The pool still says it's an umountable filesystem, but I can still see the data in the plugin and cli. Currently, it's resilvering but the ETA for completion is increasing (3+ days) while one of the other drives is kicking out read errors. This is a raidz2, so technicallly, i could try to replace the failing drive... but given that I found the system unresponsive yesterday, the UI not completely seeing the pool, I'm not sure if that'll help or hurt my current position. UPDATE: resilvering is now past 7 days and counting. Once I grab what I want from the system, I'll run SMART tests and see if any other drives need to be replaced. I'm open to other suggestions if there's a better path to take.
-
system non-responsive during resilver. Pool not found after reboot. Hosed?
I was replacing a failed drive and during the resilver, I found unRAID to be unresponsive... no SSH access, no Webui, no prompt when directly connected to the box. Upon a forced shutdown and bringing it up, unRAID told me my ZFS array was invalid, despite having all the right disks selected. I built a new config, selected the drives, and now it's saying my drives aren't mountable, and I need to format them before it'll load the zpool. There's no pool found in the ZFS Master plugin, or when I look for one via CLI. I think I'm hosed, but before I format the drives and start over, I was hoping all is not lost... diags attached. virtunraid-diagnostics-20241011-1520.zip
-
zfs export to another server running TrueNAS not working. Thoughts?
I have a zfs pool on my unRAID box, and I'm wanting to export it (while still having access to the data) to a remote system currently running TrueNAS. I've configured a ZFS Pool on the TrueNAS box, enabled SSH, and confirmed I can SSH and make a new folder on the TrueNAS box from the unRAID system. I keep running into issues using zfs send, similar to this root@virtunraid:~# zfs send -R slow@pre-migration-snapshot_17sep24_231pm | sshpass -p 'Password' ssh [email protected] sudo -S zfs recv slow cannot send slow@pre-migration-snapshot_17sep24_231pm recursively: snapshot slow/vmz@pre-migration-snapshot_17sep24_231pm does not exist warning: cannot send 'slow@pre-migration-snapshot_17sep24_231pm': backup failed Permission denied, please try again. root@virtunraid:~# zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT slow@pre-migration-snapshot 0B - 3.22T - slow@pre-migration-snapshot1 0B - 3.22T - slow@pre-migration-snapshot_17sep24 0B - 3.22T - slow@pre-migration-snapshot_17sep24_231pm 0B - 3.22T - slow@pre-migration-snapshot_17sep24_233pm 0B - 3.22T - I'm not sure why it's referencing a snapshot that doesn't exist. Maye some compatibility issues between unRAID and TrueNAS? The snapshots listed are for the pool - the plan was to export everything in one swoop while keep the data available.
-
create VM with 1000G disk, webui is hung up. ver 6.12.10
I think I found the problem - the GPUs were shared in running docker containers while I started a VM to which the same GPUs were passed through. I have configured the containers to only use a specified GPU, and the remaining unspecified GPUs were passed to the VM. So far, everything is working.
-
create VM with 1000G disk, webui is hung up. ver 6.12.10
I read in another post that you can type `diagnostics` if you have CLI access. I reviewed the zip and didn't see anything attributing to my issue. I tried to restart the nginx service with no luck, so I reboot was performed. I now have my webui again and, there doesn't appear to be any remnants of the VM i tried to create
-
create VM with 1000G disk, webui is hung up. ver 6.12.10
Hello - I fat fingered the VM disk size for 1000G and the page for creating the VM is still stuck on creating the VM (more than an hour). If I try to open a new tab for unRAID, it times out. Good news - docker containers are still running, and I can SSH in. Any advice to getting the WebUI responsive?
-
unRAID to Proxmox: do I need to migrate existing data?
I have a Dell T630 currently running unRAID and I'd like to move it to a VM managed by Proxmox. The Perc card is in JBOD mode. If I setup a VM in Proxmox for unRAID and pass the Perc card to the VM, will all the current data still be there and accessible to the unRAID VM, or should I migrate the data to another system and then transfer it back?
- Wazuh
-
Wazuh with docker compose
did you get this to work?
-
[SUPPORT] CRIBL SOFTWARE FOR UNRAID
What would you recommend if a user wanted to monitor logs from unraid, docker containers, and VMs? Looks like Crible Edge Single could potentially do this
-
[Plugin] Appdata.Backup
I just shared my logs: 455bd7c3-90a9-4842-a521-de24a1645f7d Looks like the backup acknowledges to exclude backing up /mnt, but a few lines later it's calculating /mnt's backup. I ended up cancelling the scheduled backup since it was taking several hours; causing its backup to be hundreds of GB in size.
-
[Plugin] Appdata.Backup
Update 2: After adding directories to an excluded folders/files, the backup completed much faster. I overlooked the 'per container' settings option when I configured the app. But, unless I'm misunderstanding the external volume options, I shouldn't have to do this if `save external volumes` is set to `no`. Update: I just found the "per container" settings and Plex did have /mnt/user/ listed but external volumes are NOT selected for backup. I'm going to add /mnt/user/ to the exclude list and start the backup process. I'll update this post and share my findings. Hello, I've noticed that my backups are now exponentially bigger. For example, the folder for Plex is roughly 350GB and its backup is over 3TB. I didn't have compression enabled at the time... I have since enabled it and the current backup is still bigger than the folder itself (and still growing and running 2+ hours). I'm on unRAID 6.12.3 docker container location is /mnt/user/appdata
-
constant disk writes even when docker isn't running. iotop help
TLDR: I didn't review the settings closely. appdata backup was backing up media folders (arrrgh) Update: I believe this is related to the new backup plugin. Backups with the new plugin are 10x their original size. Their last modified time appears to line up what I observed prior to me doing a restart. I'm trying to determine what is writing files to my disk and what are the files. Could be my paranoia but better safe than sorry someone suggested running iotop to see what's going on with my server, and here's the output. I'm green to the command... but seeing the ?unavailable? with root running it is concerning (til someone says otherwise). In the interim, I'm trying to stop the array but I'm getting the "try unmounting user shares" message. 10:38:52 16601 be/4 root 4278.03 K/s 1432.38 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 20940 be/4 root 1222.29 K/s 2043.52 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 10885 be/4 root 3055.74 K/s 1623.36 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 10886 be/4 root 1833.44 K/s 1661.56 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 10923 be/4 root 3666.88 K/s 1585.16 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 27495 be/4 root 1222.29 K/s 1890.74 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0 10:38:52 25824 be/4 root 611.15 K/s 2024.43 K/s ?unavailable? shfs /mnt/user -disks 4095 -o default_permissions,allow_other,noatime -o remember=0
-
upgrade to 6.12.3 + ZFS cache for docker = sluggish apps
I converted my cache pool to btrfs with Raid0 and Plex and other app UIs running from this pool are back to being responsive. Someone on reddit mentioned specifying the docker image (and not the folder location) helped with their issue. At this point, I'm happy with the performance and I don't think it's worth further testing. I did keep my second cache pool as zfs and don't have any issues with it.
-
upgrade to 6.12.3 + ZFS cache for docker = sluggish apps
optimizing libraries had no effect. I'm going to rebuild the cache array to something other than zfs to see if that helps.
-
upgrade to 6.12.3 + ZFS cache for docker = sluggish apps
Are you wanting help setting them up or you're experiencing the same issue?
-
upgrade to 6.12.3 + ZFS cache for docker = sluggish apps
For Plex, it's back to taking awhile to view recommended items. It might take 10-15 secs before anything is displayed. After that, it works as expected. Other times, it'll time out. I'm optimizing the database to see if that helps. I'm not seeing a delay in SAB but I don't feel like I've tested it enough to confirm it's fixed.
-
upgrade to 6.12.3 + ZFS cache for docker = sluggish apps
Might have made progress: Deleting docker apps and re-adding them didn't help Deleted the docker.img file and downloaded a fresh copy reinstalled docker apps via community apps plugin (thank to the author(s) for this) so far, the lag experienced in Plex is gone, but more testing to follow Maybe the old btrfs settings were causing an issue? I also just specified an image folder and not a docker image... not sure if that made a difference.