Froberg

Looking for some quick pre-purchase advice. I'm looking at updating my existing Avoton based server with a new one. Unfortunately it seems like if I want quicksync support, IPMI, ECC support & fairly low TDP I'm locked in to 9th gen Intel - if I don't want to add a dedicated GPU, which I don't. From what I've read 9th gen should be better supported by UnRAID regardless. I've found an available SUPERMICRO X11SSH-F and can source an i3 9100, too. Which should be fine for UnRAID, a handful of containers and most of all - plex transcodes. Was hoping for more than four cores, but it seems that unless I drop ECC and IPMI all I can get is either XEON or Pentium Gold - neither of which seems to be preferable for my use-case. Thanks

A bad disk shouldn't really be causing the loss of an entire raid setup though, ideally, surely?

Yes, obviously. Probably just shouldn't have upgraded the OS Was running fine until then. I'll try the other memtest once I'm done recovering. Plex takes literal ages.

Surely other issues would have cropped up during six years of use other than this btfrs issue? Surely?

Seems fine so far.. I think it's BTFRS itself that self-corrupts.. I think I've tried all variables by now, including getting the motherboard replaced at one point. Eh - think I'll just go for xfs and get started on recovery.. haven't tried recovering using backup/restore before, so it'll be a nice test at least. edit: pass complete, no errors.

What makes you suspect a memory issue? It's ECC memory and it's been put through memtest before.. I'll usually get 8-12 months out of the btfrs cache before it implodes..

yeah BTFRS is completely unmountable now.. never had it this bad before.. even set up a script to regularly monitor for corruption. Damn thing just keeps screwing up. It just says the filesystem is unmountable now, like it's all gone.. thinking I'll just to xfs from now on.. haven't had btfrs be stable despite changing s-ata connections, cables, power delivery and even switching to new SSD's entirely. Annoying. Please advise, otherwise I think I'll just have to recover from backup appdata.

Seems like it had another crash during the night.. fortytwo-diagnostics-20220609-1637.zip

I'm having it too with standard SSD's.. find any cause? Jun 8 03:18:34 FortyTwo kernel: BTRFS error (device sdb1): block=455832535040 write time tree block corruption detected Jun 8 03:18:34 FortyTwo kernel: BTRFS: error (device sdb1) in btrfs_commit_transaction:2438: errno=-5 IO failure (Error while writing out transaction) Jun 8 03:18:34 FortyTwo kernel: BTRFS info (device sdb1): forced readonly Jun 8 03:18:34 FortyTwo kernel: BTRFS warning (device sdb1): Skipping commit of aborted transaction. Jun 8 03:18:34 FortyTwo kernel: BTRFS: error (device sdb1) in cleanup_transaction:2011: errno=-5 IO failure Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 29152 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 458944 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 983232 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 459392 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 983680 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 460448 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 984736 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS: error (device loop2) in free_log_tree:3451: errno=-5 IO failure Jun 8 03:18:36 FortyTwo kernel: BTRFS info (device loop2): forced readonly Jun 8 03:18:36 FortyTwo kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction. Jun 8 03:18:36 FortyTwo kernel: BTRFS: error (device loop2) in cleanup_transaction:2011: errno=-5 IO failure Jun 8 03:18:36 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 32928 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 Jun 8 03:18:36 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Jun 8 03:28:38 FortyTwo root: Restoring original turbo write mode Jun 8 03:28:38 FortyTwo kernel: mdcmd (129): set md_write_method auto Jun 8 03:28:38 FortyTwo kernel: Jun 8 03:44:08 FortyTwo kernel: blk_update_request: I/O error, dev loop2, sector 29152 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jun 8 03:44:08 FortyTwo kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 0, flush 0, corrupt 0, gen 0 BTFRS has been the single most unstable thing with my UnRAID experience thus far..

Yup.. (It's being updated regularly.) Actually your post reminded me that linuxserver seems to have abandoned direct support of their UnRaid container offerings.. so I switched to binhex/arch-medusa instead just now.

I fail to see how it could be an ABS container issue, when it's working flawlessly on my end.

Noticed a lot of people asking about nginx proxy manager, here's my working setup: Hope it helps someone.

Eh my car is fairly random. It's a SKODA with the integrated option. It works fairly weirdly, haven't been able to resolve it. But basically: * Enter car and turn ignition * Mount phone and start playing audio * Go in to bluetooth media and press play (being able to see the artist but no audio) * This pauses playback on the device, press play on device and audio comes finally, but you can no longer see the artist information. This works for all apps I've tried.. but this software won't trigger the audio at all. Workaround is just starting audio from something else - and clearly it may just be my funky car stereo system at fault.. just figured I'd mention it regardless.

After having used this for a few months now, well, since you came out with it.. I cannot recommend this enough. This is flippin' awesome. Beats Plex with a large metal rod mercilessly. One oddity, which I'm sure can't be replicated. I use this exclusively in my car while commuting and I found something interesting. I am unable to get audio through my car speakers, until I start any other app - like PlexAmp - then pause that, which will allow me to hear the audio from Audiobookshelf. It's weird, and probably unique, but figured I'd mention it. It's like it can't initiate the audio signal on its own or something. Can replicate it every time I reboot the phone without fail.

Resetting the library fixed it. It kept trying to find files in folders I had deleted. It decided to remove the cover art for almost the entire library. Some it downloaded instead. But it seemed to suddenly decide to ignore the embedded covers, despite them working previously. If I delete an audiobook folder, will I then need to manually remove it from ABS too?

Err.. I may be missing something obvious here. Once I got the system up and running, I was made aware of some naming issues, missing serialization in my folders and some outright flaws in my files. So after renaming, reordering and general fixer-uppery I did I a rescan of the library. Now most of the embedded artwork has decided to disappear, and the "download artwork if missing" option didn't resolve it, either. What's worse is that it remembers the now-deleted directories where files used to be stored, incorrectly. How do I force it to let go of now-deleted stuff?

So I saw on your github that you're not accepting donations as yet, so I'll hold off on that for a while. Just got this up and running an hour ago, already I'm loving the library layout and the ease of use of it all. Miles and miles better than running it through my plex library. Much love to you. I can't wait to follow this application and see where it goes. I'm using the Android app as well, everything seems to just work. (Well, as soon as I ticked the right options in NPM ) Kudos man, this is great stuff.

You're on the linuxserver one, then?

Works fine without, tried that first, but I figured it should be there since it's explicitly mentioned in the OP?

Renamed to lower-case - postargs: docker exec -u 0 nxtcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' No joy, container won't load. log says: /entrypoint.sh: 194: exec: docker: not found

yeah it's the post-args, tried removing some stuff and it won't behave. If I remove all the post-args the container launches. I'll try and rename it lower case. Cheers.

Trying to use this to replace a b0rked LinuxServer version, and this was recommended to me. I already have a nextcloud, currently stopped, but I'm not deleting it yet, so I wanted to add yours as "NXTCloud" and changed the folder mappings appropriately, and added the variables and parameters you mentioned, even added a port number for bridge mode. It doesn't want to launch however. Removing container: NXTCloud Successfully removed container 'NXTCloud' Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='NXTCloud' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -p '8666:80/tcp' -v '/mnt/user/appdata/nxtcloud/':'/var/www/html':'rw' -v '/mnt/user/appdata/nxtcloud/apps':'/var/www/html/custom_apps':'rw' -v '/mnt/user/appdata/nxtcloud/config':'/var/www/html/config':'rw' -v '/mnt/user/appdata/nxtcloud/data':'/var/www/html/data':'rw' -v '/mnt/user/Share/':'/mnt/Share':'rw' --memory=2G --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 'nextcloud:latest' PostArgs: && docker exec -u 0 nxtcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' 2c3b5dfa03141bda7dbd795480db77ec70845af59c511b1ae910008bded9e6b8 Error: No such container: nxtcloud The command failed. It's sad if I'm too blind to do monkey see monkey do, but I'm stumped, really.

It's already using MariaDB. I had a problem with my cache drive, everything went down, turns out it was the database, but I hadn't suspected that before fiddling with NPM first, as that had just been updated and I noticed things not working post-updating that, rather than when MariaDB updated. So not sure what exactly happened, but Nextcloud was working perfectly with the config it had. I have to assume that maybe something got corrupted, despite its services being functional. I'll have a look at the Knex-container as you recommended. I've gotten this stuff to work before, I just ran against a wall trying to debug this and, well, finding a clue when you're frustrated isn't easy. I really appreciate you taking the time, thank you so much!

You are correct! When changed to http in NPM, the wordpress install is now accessible. That at least means that NPM works. So either my settings for nextcloud are off, just as they were with the wordpress install, or I guess nextcloud is just broken.. although it's updateable via command line and everything appears to function fine. Unless you can see anything obviously wrong, I think I'll just have to scrap the nextcloud and start over.... I do wonder what on earth has gone wrong though.

The wordpress test-site works via local logon, if that's what you wanted to verify? 🙂 Since they suffer from the same fault I think it serves the purpose for testing?