flokason

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by flokason

  1. Thank you for the help Yes that activity is no more, it looks normal now I will look up that pool monitoring, thank you
  2. Thank you JorgeB I would appreciate any advice so I can prevent this happening again, and perhaps knowing how to fix it if it happens again Best regards tower-diagnostics-20240330-1052.zip
  3. I got kind of depressed, google something Though I should delete everything from both of my cache drives and then restore it with appdata backup Did those commands shown on screenshot Dockers started to work And hevy read/write on my cahce drive I have literally know idea what it happening
  4. I think I have to format and start from scratch on my cahce drives root@Tower:~# btrfs dev stats /mnt/cache [/dev/nvme0n1p1].write_io_errs 296591154 [/dev/nvme0n1p1].read_io_errs 454910 [/dev/nvme0n1p1].flush_io_errs 1525783 [/dev/nvme0n1p1].corruption_errs 16434475 [/dev/nvme0n1p1].generation_errs 13247 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0
  5. I do have the appdata backup plugin and backed up last time 25th of Mars Should I restore that?
  6. I can only do it on Cache, not Cache 2 (they are mirror) I get this: [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/nvme0n1p1 UUID: 7928d4a8-c447-4027-8952-2e27c43e51a9 found 511549218816 bytes used, no error found total csum bytes: 401640012 total tree bytes: 1649328128 total fs tree bytes: 993787904 total extent tree bytes: 166559744 btree space waste bytes: 372308360 file data blocks allocated: 1470746066944 referenced 495950946304
  7. Like topic says, I updated from 6.12.8 to 6.12.9 and now I get this message on my dockers: Docker Service failed to start. Attached is my diognostics I would appreciate all help tower-diagnostics-20240329-2118.zip
  8. Thank you that worked, Now forexample Dockers don't work But I do have access to a weeks old backup of my old flash drive. Do I gain anything on recreating my usb flashdrive from that backup?
  9. Thanks for your help Should I just click "delete pool". And then I can start the array up again
  10. Well that does sound good, I can't imagine that something crucial was on it So what should I do now. That is, how do I start my array without it correctly Thank you
  11. Thanks for your replys I checked BIOS, did not see the drive. Took the drive out, in again. Power on, did not see in the BIOS There has been for some time 1 error on it in SMART, don't remember which one. I kind of thought it was no big deal. So if this drive is dead, what are we talking about. Can I restore everything without it? I think I was using it as cache for every 24 hours
  12. So my usb flash drive died. And all my backups of it are on on my array, and encrypted rclone gdrive I was able to DMDE to restore my config file, or hopefully all of it. So I made a new USB drive with unraid, and c/p my recovered config file to the new USB I have gotten my licence to work on the new USB drive But it says my cache drive is missing. It is a 1TB m2 SSD. So there are no cables to connect/reconnect Now I am a afraid to do something wrong so destroy my data. So I will appreciate all help tower-diagnostics-20231215-1737.zip
  13. Appears to be working! I deleted eth2 from the network-rules Thank you so much https://imgur.com/HpiOjBq Now I don't have a multiple MAC address Pretty strange problem though
  14. Hi I'm pretty sure this file is now called "network-rules.cfg" See mine here: # PCI device 0x8086:0x15b8 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e0:d5:5e:0d:a9:af", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" -- # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ec", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ed", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ed", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" I tried deleting the network-rules.cfg and reboot. Did not work, came back like this. Aslo tried deleting the duplicate line of eth3 and rebooting. Did not work, came back like this Any more ideas? My diagnostics file is attached edit: Is it possible that the conflict is that it is sharing an IOMMO group with the PCI bridge? IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) [15b3:6750] 01:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) tower-diagnostics-20210519-0051.zip
  15. I'll try that But right now the mellanox card is not installed, as I gave up on installing it yesterday, because it made it impossible to use eth0 as my old nic to get internet to my Unraid server I do have 4port i340 card installed, but it is bounded to pfsense VM, so perhaps thats the reason why i have no interface-rules.cfg Thanks for your help
  16. Thanks for you comment. There is no interface-rules.cfg files there unfortunatly
  17. I got myself a Mellanox ConnectX-2 Dual SFP+ card. It appears in unraid, but there is one problem. I get three interfaces from it, and two of them have the same MAC Address. So I am unable to make changes what is eth0, eth1.. etc because of that. I get an error saying there is a mac address duplication I guess I need to some how remove eth3 from the interfaces. Has anyone experienced anything like this?
  18. Just wanted to share my share experience I've been running Unraid for many years, and mostly SMB has worked without problems Tonight however, my work laptop was unable to access my smb share. However my unraid virtual win10 machine could, and also my gf laptop I went through most of the tips, and the one that worked was going to windows credentials. I saw \\tower there with my work laptop credentials for some reasons I deleted it, and then when I tried to access my smb drive I had to set in user and password (which I thing is a bit strange since I don't think you should need user&pass for that access, but anyway) I entered my unraid user and password, and then it finally worked So thanks to the one that talked about the windows credentials
  19. I have been trying to get inter HW transcoding to work for the past months without success. I have the Intel 8700k Gigabyte HD3 Z370 motherboard Unraid 6.6.5 In Plex, extra parameters, I have this line: My go file: My syslinux file has this: when I list directories in the path /dev/dri I have these: I do have a lifetime plex pass I have it ticked "use hardware acceleration when available" in the Plex settings. But still no hardware transcoding. Here is the error from the Plex logs: If anyone could help me it would be greatly appreciated edit: I think I might not be using the linuxserver.io docker. I think I have the official unraid docker, this is what says in the repistory: plexinc/pms-docker So perhaps this question doesn't belong here, but I hope I get some answers, maybe I should post it somewhere else
  20. I gave up, I think that router was crap, so I turned it in Back with using my ISP old router as modem for my VDSL and Unifi USG as a router
  21. Thanks for taking a look, This resulted since I had the older router fix the IP to 192.168.1.132, and the newer one is rather simple (its from my ISP) So I had to manually set the IP address in the unraid server to get this IP, as I use it in my config documents, I rather have it at this IP. So when changing from DHCP to static, I did this mistake. I have fixed that, then my fixcommon problems told me to add a DNS, and now my network config file looks like this: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0" BRNICS[0]="bond0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.132" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.254" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" SYSNICS="1"
  22. Very strange though I can only access through https://192.168.1.132:442/ my virtual machines are missing edit: vdisk images still there so I can mount them Still the issue regarding https and using 192.168.1.132 to directly access my server and ofcourse nextcloud, probably same letsencrypt error
  23. EDIT got access when I entered this, so hopefully everything is alright: https://192.168.1.132:442/
  24. So I just changed my router. The old one had a gateway of 192.168.1.1, but the newone 192.168.1.254. Otherwise everthing is about the same. IP of the server was and still is 192.168.1.132. All my dockers work, plex, tautulli etc. (excluding nextcloud/letsencrypt) So I can't access my webgui, when I enter 192.168.1.132 the url goes to https://2b18d61e08b171a29b19d1282b7aa8ae2b4ab766.unraid.net:442/ Which it always did, or something like that at least, but now I get the error message This site can’t be reached 2b18d61e08b171a29b19d1282b7aa8ae2b4ab766.unraid.net’s server IP address could not be found. Try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN I have tried many browsers, clearing all cache but this always happen. Does this have something to do with the lets encrypt certs? I once had a problem with letsencrypt and my nextcloud and I couldn't run certbot renew, but it worked deleting /etc folder and restarting docker. But I don't know what I can do for the unraid webgui I have attached the tower diagnostics folder I do have access to the server with ssh Any help appreciated tower-diagnostics-20180904-1934.zip
  25. I fixed the problem regarding: "Import failed, path does not exist or is not accessible by Radarr: /data/complete/movies/ xxxxxxxxxxxxxxx" It was previous downloads via sabnzdb somehow telling radarr to check on them (or something) What I did was delete/purge nzb files from SABnzdb and then this error log stopped The /movie/movie error seems to be gone, hopefully it doesn't start over again Thank you again for quick replies