mrtrilby

Ok, so I found the file vfio-pci.cfg under the config folder on the USB flash drive. It contained a line starting with BIND=, followed by these IDs that I listed above. I just deleted that file, and the server booted fine. I have a copy of that file just in case, but it seems no new file with the same name has been created. I'm assuming this binds the GPUs to certain IDs? Anyway, my VM with GPU passthrough is working like before, and server is thankfully doing fine.

Thank you, that was absolutely the case..

My USB flash died last week, but I got the server up again. However, in order to split IOMMU groups to enable sound in my VM, I enabled ACS override for downstream according to SpaceInvader One's excellent video from about 16:00. I believe this is what I had to enable previously in order to get sound working. However, the server will no longer boot. It starts from the USB, and then stops after the lines I have printed below: vfio-pci 0000:01:00.0 vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none vfio-pci 000:0b:00.0 vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem I took the USB drive to another computer, edited syslinux.cfg and removed the acs override option that I added, but the issue is the same... Anyone able to shed light on this?

After my USB flash ended up dying a week ago, I reinstalled 6.11.5. Thanks to the forums here, I managed to get things running again, but I have a couple of issues. For example, on the VMs tab, I can see the Virtual Machine that I recreated, but there are no other options to add USB devices to the VM like I did previously. Before, I could locate attached USB devices from a dropdown list and choose Attach, to attach it to the currently running VM. Why is this no longer visible below the list of VMs? This is the same in any browser.

Good to know, thanks!

You were right about me using Firefox. Tried from another computer, different browser, no problem at all! Parity is rebuilding. Thank you so much for your help!

I tried that, but it says the configuration is stale, and the array won't start. I've tried setting New config in Tools, but it doesn't seem to help. What to do then..?

Thank you, that is very helpful! One of them is indeed bigger, so thank you so much for pointing out those details. I'll run the correcting parity check. I had a stressful day in many regards, not even counting the death of my Unraid server, and at least the help I received today eased the pain. Thanks to all, hopefully it'll be up again soon!

That said, following the guidance, I cannot determine which of the 2 disks was the parity drive, since I can mount both disks, following either of the 2 options given in the documentation. How can I find out which is the data disk and which is the parity..?

I have to commend Lime Tech here, I already received the new license key!

Thanks for reply. The credentials work for logging in to the forums and to the Connect page, so I doubt they are incorrect..? Thanks for the manual alternative, I've filled out the form. Not so happy to potentially have to wait up to 4 days... Hopefully they can make it happen faster.

Hi. Please help with how I can replace the flash key. Following the way to do it I get issues with login. On the Unraid server I am asked to use another client because "Unfortunately Firefox in Unraid's OS GUI mode causes issues with the webGUI communicating with this pop-up windows. Please use an alternative client to access the Unraid webGUI to interact with your account." If I do it from another machine, the login simply doesn't work, it just sends me back to login after supplying the credentials.

Hi. I wake up to a dead USB drive that had Unraid OS on it. I have run flash backup many times from the My Servers page (now rebranded to Unraid Connect..?) but there is no backup to be found there now. Isn't the online My Servers supposed to store your last flash backup? If not, what's the point of it..? So what do I do now..?

Hi. Today my server is acting weirdt-tower-diagnostics-20230404-2115.zip. After a few minutes of uptime, the shares become inaccessible, and so does the GUI of the server. The docker containers are also not working. My VM running on the server is working fine, except I can't open any shares, obviously. I'm writing this from the VM now. Diagnostics attached. The diagnostics are taken from the web GUI before it becomes unresponsive. Afterwards, I can SSH into the server and start the diagnostics command, however, it just says "Starting diagnostics collection ..." and the cursor blinks in a loop. Here is from the log file after successful startup. Errors start popping up about 15 minutes after startup (scroll down). Please, if anyone has a clue to what's going on... Apr 4 21:14:45 T-TOWER avahi-daemon[27824]: Registering new address record for 127.0.0.1 on lo.IPv4. Apr 4 21:14:45 T-TOWER emhttpd: shcmd (162): /etc/rc.d/rc.avahidnsconfd restart Apr 4 21:14:45 T-TOWER root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Apr 4 21:14:45 T-TOWER root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Apr 4 21:14:45 T-TOWER avahi-dnsconfd[27833]: Successfully connected to Avahi daemon. Apr 4 21:14:46 T-TOWER avahi-daemon[27824]: Server startup complete. Host name is T-TOWER.local. Local service cookie is 2480387511. Apr 4 21:14:46 T-TOWER avahi-daemon[27824]: Service "T-TOWER" (/services/ssh.service) successfully established. Apr 4 21:14:46 T-TOWER avahi-daemon[27824]: Service "T-TOWER" (/services/smb.service) successfully established. Apr 4 21:14:46 T-TOWER avahi-daemon[27824]: Service "T-TOWER" (/services/sftp-ssh.service) successfully established. Apr 4 21:15:07 T-TOWER nmbd[27788]: [2023/04/04 21:15:07.567216, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: Samba name server T-TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: [2023/04/04 21:15:07.567390, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: Samba name server T-TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: [2023/04/04 21:15:07.567458, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: Samba name server T-TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: [2023/04/04 21:15:07.567521, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: Samba name server T-TOWER is now a local master browser for workgroup WORKGROUP on subnet 10.10.100.10 Apr 4 21:15:07 T-TOWER nmbd[27788]: Apr 4 21:15:07 T-TOWER nmbd[27788]: ***** And now, almost 15 minutes later, this happens (see below). 10.10.100.10 is my server, 10.10.100.139 is my VM. Something's happening with the unnassigned devices? Apr 4 21:29:46 T-TOWER nginx: 2023/04/04 21:29:46 [error] 9252#9252: *263 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.100.139, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.10.100.10", referrer: "https://10.10.100.10/Docker" Apr 4 21:29:46 T-TOWER nginx: 2023/04/04 21:29:46 [error] 9252#9252: *263 auth request unexpected status: 504 while sending to client, client: 10.10.100.139, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/2.0", host: "10.10.100.10", referrer: "https://10.10.100.10/Docker" Apr 4 21:29:50 T-TOWER nginx: 2023/04/04 21:29:50 [error] 9252#9252: *263 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.100.139, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.10.100.10", referrer: "https://10.10.100.10/Tools/Syslog" Apr 4 21:29:50 T-TOWER nginx: 2023/04/04 21:29:50 [error] 9252#9252: *263 auth request unexpected status: 504 while sending to client, client: 10.10.100.139, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/2.0", host: "10.10.100.10", referrer: "https://10.10.100.10/Tools/Syslog" Apr 4 21:32:56 T-TOWER nginx: 2023/04/04 21:32:56 [error] 9252#9252: *263 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.100.139, server: , request: "GET /Settings HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.10.100.10", referrer: "https://10.10.100.10/Docker" Apr 4 21:32:56 T-TOWER nginx: 2023/04/04 21:32:56 [error] 9252#9252: *263 auth request unexpected status: 504 while sending to client, client: 10.10.100.139, server: , request: "GET /Settings HTTP/2.0", host: "10.10.100.10", referrer: "https://10.10.100.10/Docker" Apr 4 21:35:34 T-TOWER nginx: 2023/04/04 21:35:34 [error] 9252#9252: *263 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.100.139, server: , request: "GET /Dashboard HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.10.100.10", referrer: "https://10.10.100.10/Tools/Syslog" Apr 4 21:35:34 T-TOWER nginx: 2023/04/04 21:35:34 [error] 9252#9252: *263 auth request unexpected status: 504 while sending to client, client: 10.10.100.139, server: , request: "GET /Dashboard HTTP/2.0", host: "10.10.100.10", referrer: "https://10.10.100.10/Tools/Syslog" Apr 4 21:36:39 T-TOWER nginx: 2023/04/04 21:36:39 [crit] 9252#9252: *11657 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 168.80.174.2, server: 0.0.0.0:443

Hi. I have a rather strange issue with file and folder access, it seems. I have mapped external drives in Nextcloud (mapped as ext_Cloud), and I am able to see old folders and files. I can also manually upload new files to any location. However, if I create a new folder on the drive in the file system, I am unable to see this folder in my Nextcloud. Furthermore, using the Android app, I am unable to auto-upload images to any location. I have used this in Nextcloud in the past for the camera, although not from this docker image. These lines are repeated over and over in the log. (The IP is not mine, it is probably Cloudflare's, which I'm using): 141.101.97.101 - mrtrilby [09/Feb/2023:16:48:53 +0200] "HEAD /remote.php/dav/files/mrtrilby/ext_Cloud/Photos/2023/02/ HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.23.1" 141.101.97.101 - mrtrilby [09/Feb/2023:16:48:53 +0200] "MKCOL /remote.php/dav/files/mrtrilby/ext_Cloud/Photos/2023/02/ HTTP/1.1" 409 747 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.23.1" 141.101.97.101 - mrtrilby [09/Feb/2023:16:48:54 +0200] "MKCOL /remote.php/dav/files/mrtrilby/ext_Cloud/Photos/2023/ HTTP/1.1" 423 768 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.23.1" Please advise on what could cause this..?

I suggest you follow IBRACORP's most excellent guide here. This is the one I used, and it worked perfectly for me. It is so easy to forget one of the steps if you try to go by memory, so better to follow a guide that works from A-Z.

Yes, this works, thanks!

Hi. You write: "Please make shure you got the volume mounting correct. Please note you can mount any share to for example /mnt/Share and mount it in nextcloud with the "external storage" app." I've enabled the External Storage app, but when I go to set it up (following Spaceinvader One's YT video, which I've followed in the past with a different docker image), I get this error message: ""smbclient" is not installed. Mounting of "SMB/CIFS", "SMB/CIFS using OC login" is not possible. Please ask your system administrator to install it." What can be done to fix this?

Got it, setting up everything again. I'm glad reinstalling docker containers in Unraid is a breeze! Thanks for your help!

Successfully ran a restore. Then I tried a --repair. Does the result below mean a reformat is needed..? ====== root@T-TOWER:/mnt/disk1# btrfs check --repair /dev/nvme0n1p1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... bad tree block 22036480, bytenr mismatch, want=22036480, have=30425088 ERROR: cannot read chunk root ERROR: cannot open file system

Got it, running a btrfs restore now - it's copying stuff over to the array.

None of the options worked... What's left - reformat and restore manually..? ====== root@T-TOWER:/mnt/disk1# mount -o degraded,usebackuproot,ro /dev/nvme0n1p1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. ====== root@T-TOWER:/mnt/disk1# btrfs restore -vi /dev/nvme0n1 /mnt/disk1/restore No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super ====== root@T-TOWER:/mnt/disk1# btrfs check --repair /dev/nvme0n1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... No valid Btrfs found on /dev/nvme0n1 ERROR: cannot open file system ======

Ok, thanks for quick response! I'll try those and see.

Hi. I recently upgraded to 6.9.2 (I had lots of VM issues with 6.9.2 previously, and stayed with 6.9.1 until now), and moved my NVMe M.2 drive from slot 2 to slot 1 on the MB (it's faster, and I removed GPU #2 so it would release the bus). Yesterday all worked perfectly, and I got my Windows VM up and running. Today I tried booting a Linux VM. It resulted in a hang, and I had to do a power button hold to stop it. After that, the main cache drive (the NVMe I moved) says it's unmountable. In the syslog it says there's a "bad fsid on block ... (long number)". I tried disabling VM Manager and Docker, but it does not help. Moving the NVMe back to slot 2 also doesn't change anything. The array is working fine, but since docker and VMs are running on the cache, it is not a good situation... Can anyone help? t-tower-diagnostics-20220317-1703.zip t-tower-syslog-20220317-1502.zip

That's fabulous - and thank you for your help!