Sledgehamma

Members
  • Posts

    100
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Sledgehamma's Achievements

Apprentice

Apprentice (3/14)

10

Reputation

  1. Thanks again for your support! I managed to install it with the provided steps. However, I cant seem to change the theme to anything other than organizr. I tried step 4 and setting it to "aquamarine", "Aquamarine", "Hotpink", "Nord" (tried both small and capital first letter) but it always reverts to the default organizr theme.
  2. You do it for free in your spare time! No need for an excuse mate! Very happy and thankful that you helped me. I will try it next week as I’m currently remote and my VPN decided to take some time off
  3. Thanks! However, I don't quite understand. These are examples for other container like Hotio or ls.io. Can I add the theme for your Dockers like this? If so, which should I use?
  4. Hi ich777 did you have a chance to look into it?
  5. Thanks a lot mate for looking into it! No worries, take your time
  6. So I assume its working for everyone just fine with the cache dirs plugin? //edit: So the disk do not spin up when I open a directory which just has other directories in it. But as soon as I open a directory which has video files in it, the disks are spinning up. So could it be that FileBrowser is scanning the files for some reason? //edit2: It seems that this is the intended behaviour of cache dirs...well its already in the name stupid me
  7. I did it the way you described but it is not working. I also tried changing to but it didn't change anything. What did I do wrong?
  8. Hey ich777, thanks a lot for your great templates Would it be possible to add theme.park support for your templates for supported Dockers like Sonarr? https://docs.theme-park.dev/setup/#docker-mods
  9. Does it work for you with the cache directories plugin? For the Docker I used /srv to /mnt/user in order to see all my shares. I set the option inside the cache dir plugin to also scan /mnt/user. But when my drives are asleep and I want to open a share say "movies" (doesn't even have subdirectories) my disk are spinning up.
  10. I just made the switch from Qnap to unRaid and this really bothers me. For me it’s an essential feature to cp,mv,rm files from my smartphone or tablet. Solutions like midnight commander are just not usable with this way. Plus I think an App for that would appear to potential Switchers coming from the competition. Im currently trying several different options. Yesterday I tried Nextcloud and it was just buggy. Moving a 50Gb file from cache to a cache enabled share took way too long. Then I tried a 7Gb file which resulted in an error that it couldn’t be moved but it still was. And the whole container crashed… A very lightweight a beautiful solution is https://filebrowser.org I’d be absolutely happy if there was an app for that! Another solution I’ll be testing over the weekend is tonido. It was mentioned that SMB 3 can do these operations without moving the files through a client but it doesn’t work on “files” on iOS. Maybe I configured something wrong? I also tried FE File Explorer on iOS but it doesn’t support moving between shares -.- //edit: Tonido seems very useful! It does exactly what I want. Sadly you don't see your favourites when moving files so you have to go through "\" then scroll down to "unRaid" and then select your share. Just need to be sure that all remote connections are disabled as I dont what all my shares exposed to the internet. //edit2: Sadly Tonido creates .tonidodb files for indexing and it cant be disabled. Also, while not a biggie the UI seems quite outdated and more importantly development has stopped. So I'm back at Filebrowser I linked above. The fact that an App is missing, really bothers me. For now I just made a bookmark of it on my home screen. Maybe I'll look into how to build a web app or pay somebody on fiverr to do that for me.
  11. I just did that and it seems fine for now. No mention of a disconnected device! Thanks for the tip Any idea how this can be? Did I mess up the config or something? Or could it still be a bad cable? I just dont want it happen again.
  12. Thanks for the swift reply Here you go: stormy-diagnostics-20211115-1432.zip
  13. Hello again, it seems after solving one problem another one pops up This time its my Raid1 SDDs (2x240GB Seagate Ironwolf 510), which are connected via "Cablecc 4X NVME M.2 AHCI to PCIE Express 3.0 Gen3 X16 RAID Card VROC Raid0 Hyper Adapter". Out of the blue I got errors that one of the drives is missing: "Cache pool BTRFS missing device(s)". I thought it was the PCIe riser cable which I used, but even with another PCIe to NVME adapter (Sabrent NVMe M.2 SSD to PCIe X16 / X8 / X4 Card with Aluminium Heatsink (EC-PCIE) I still get the same error. These errors are with the Sabrent adapter and SSD1: I do get these warnings: Nov 15 11:14:46 Stormy kernel: ACPI: Early table checksum verification disabled Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:21:02.0: BAR 14: failed to assign [mem size 0x00500000] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 6: failed to assign [mem size 0x00080000 pref] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:20:00.0: BAR 14: failed to assign [mem size 0x02400000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:06.0: BAR 14: failed to assign [mem size 0x01800000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:01.0: BAR 14: failed to assign [mem size 0x00100000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:02.0: BAR 14: failed to assign [mem size 0x00500000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:04.0: BAR 14: failed to assign [mem size 0x00100000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:05.0: BAR 14: failed to assign [mem size 0x00100000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:08.0: BAR 14: failed to assign [mem size 0x00200000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:09.0: BAR 14: failed to assign [mem size 0x00100000] Nov 15 11:14:46 Stormy kernel: pci 0000:21:0a.0: BAR 14: failed to assign [mem size 0x00100000] Nov 15 11:14:46 Stormy kernel: pci 0000:23:00.0: BAR 0: failed to assign [mem size 0x00004000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.0: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 7: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:24:00.1: BAR 10: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:26:00.0: BAR 0: failed to assign [mem size 0x00080000] Nov 15 11:14:46 Stormy kernel: pci 0000:26:00.0: BAR 3: failed to assign [mem size 0x00004000] Nov 15 11:14:46 Stormy kernel: pci 0000:27:00.0: BAR 0: failed to assign [mem size 0x00080000] Nov 15 11:14:46 Stormy kernel: pci 0000:27:00.0: BAR 3: failed to assign [mem size 0x00004000] Nov 15 11:14:46 Stormy kernel: pci 0000:28:00.0: BAR 14: failed to assign [mem size 0x01800000] Nov 15 11:14:46 Stormy kernel: pci 0000:29:00.0: BAR 0: failed to assign [mem size 0x01000000] Nov 15 11:14:46 Stormy kernel: pci 0000:29:00.0: BAR 1: failed to assign [mem size 0x00020000] Nov 15 11:14:46 Stormy kernel: pci 0000:2a:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:2a:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] Nov 15 11:14:46 Stormy kernel: pci 0000:2b:00.0: BAR 5: failed to assign [mem size 0x00000800] Nov 15 11:14:46 Stormy kernel: pci 0000:2c:00.0: BAR 5: failed to assign [mem size 0x00000800] Nov 15 11:14:46 Stormy kernel: sd 0:0:0:0: [sda] Asking for cache data failed And these errors: Nov 15 11:16:20 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321237188608 have 545259526 Nov 15 11:16:20 Stormy kernel: BTRFS: error (device nvme2n1p1) in __btrfs_free_extent:3188: errno=-5 IO failure Nov 15 11:16:20 Stormy kernel: BTRFS: error (device nvme2n1p1) in btrfs_run_delayed_refs:2150: errno=-5 IO failure Nov 15 11:16:25 Stormy inotifywait[9879]: Couldn't watch /mnt/apps: Input/output error Nov 15 11:16:25 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321237745664 have 1157409746040655887 Nov 15 11:16:29 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321241186304 have 826882912313 Nov 15 11:16:29 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321241186304 have 826882912313 Nov 15 11:16:29 Stormy kernel: blk_update_request: I/O error, dev loop2, sector 62914432 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 15 11:16:29 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321241186304 have 826882912313 Nov 15 11:16:29 Stormy kernel: blk_update_request: I/O error, dev loop2, sector 62914432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 15 11:16:29 Stormy kernel: Buffer I/O error on dev loop2, logical block 7864304, async page read Nov 15 11:16:29 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321241186304 have 826882912313 Nov 15 11:16:29 Stormy kernel: blk_update_request: I/O error, dev loop2, sector 62914432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 15 11:16:29 Stormy kernel: Buffer I/O error on dev loop2, logical block 7864304, async page read Nov 15 11:16:29 Stormy kernel: BTRFS error (device nvme2n1p1): bad tree block start, want 321241186304 have 826882912313 Nov 15 11:16:29 Stormy kernel: blk_update_request: I/O error, dev loop2, sector 62914432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 15 11:16:29 Stormy kernel: Buffer I/O error on dev loop2, logical block 7864304, async page read Nov 15 11:16:29 Stormy kernel: BTRFS error (device loop2): bad tree block start, want 22020096 have 1117782016 Nov 15 11:16:29 Stormy kernel: BTRFS error (device loop2): bad tree block start, want 22020096 have 1126170624 Nov 15 11:16:29 Stormy kernel: BTRFS error (device loop2): failed to read chunk root Nov 15 11:16:29 Stormy root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error. Nov 15 11:16:29 Stormy kernel: BTRFS error (device loop2): open_ctree failed Nov 15 11:16:29 Stormy root: mount error I also tried different PCIe slots on my MB, but same behaviour. When I use the same adapter with SSD2. I get these errors (the PCI warnings are the same): Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 49, gen 0 Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 50, gen 0 Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 51, gen 0 Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 52, gen 0 Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 53, gen 0 Nov 15 14:01:54 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 54, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 55, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 56, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 57, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 58, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 59, gen 0 Nov 15 14:06:11 Stormy kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 60, gen 0 So does this mean that the SSD1 is defective? If so I hope that SSD2 is still okay. What. should I do next? Format it again and then install Docker etc. from scratch?
  14. Alright, so its fixed. Not a big fan oof ASRock that's for sure... So it wasn't enough to disable network bonding which I already had: I also had to disable eth1 (eth0 is the IPMI): It really didn't help that the MAC address of eth1 wasn't listed in unRaid (not blaming Limetech, probably ASRocks fault). Eth0 I can understand because its the IPMI port. Then I used one of the 10GBe ports in unRaid (disabled bonding as well) and put it as eth0 (this is not the same eth0 as the IPMI port) and disabled all other ethernet ports. If anybody else has this problem or this board, for the love go God do not disable eth0! I did and while eth1 was set to DHCP it didn't get an IP address. While stupid me saw the 0.0.0.0 IP in the BMC I thought it was a display error because DHCP for sure would work....of course it didn't and I had to buy a VGA to HDMI adapter in order to access the BIOS or the BMC because I couldn't access it anymore over LAN. All in all a pretty bad implementation for a board that costs 500€