Everything posted by steve1977
-
Disks in USB enclosure not detected
There is no "apply" button? Just a "done". Let me try to reboot though.
-
Disks in USB enclosure not detected
I stopped the array, so VM is stopped. I unselected the "binding", but it doesn't "stick". Whenever i re-enter the setting, it is still ticked. Any idea?
-
Disks in USB enclosure not detected
Maybe, that's the reason? I tried to "untick" it, but the "tick" comes back. How to unselect it?
-
Disks in USB enclosure not detected
Could it be related that below is "tick-marked" (bind)? IOMMU group 15: [1022:43ee] 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller This controller is bound to vfio, connected USB devices are not visible.
-
Disks in USB enclosure not detected
Thanks root@Tower:~# lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=vhci_hcd/8p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=vhci_hcd/8p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 346d:5678 /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub
-
Disks in USB enclosure not detected
I can see below under "system devices". Is this my disk? If so, any idea why it doesn't show under UD? IOMMU group 32: [1022:149c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-1 ID 346d:5678 USB Disk 2.0 Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub
-
Disks in USB enclosure not detected
Unraid crashes when plugging in the USB device. So, something is happening. One suspicion I have is this that the flash disk is low on space, so maybe this makes Unraid stable? Does the two logs indicate anything about the enclosure? Particularly the second one may have some indications?
-
Disks in USB enclosure not detected
And another log where I plugged in the device, but Unraid didn't crash just yet. tower-diagnostics-20260421-1046.zip
-
Disks in USB enclosure not detected
Attached the diagnostic log after restarting. tower-diagnostics-20260421-1026.zip
-
Disks in USB enclosure not detected
Anything else I can provide. Unfortunately, I still cannot access the USB device. When I plug it in, Unraid GUI collapses. I tried another Unraid server of mine with the same enclosure and it worked well. So, it must be something related to this Unraid server.
-
NTFS disk fails to mount - Device '/dev/sdn' failed to mount
Thanks. Any idea how to address this?
-
NTFS disk fails to mount - Device '/dev/sdn' failed to mount
Title says it all. It's a disk attached via USB enclosure. Shows up, but cannot mount it. Attaching diagnostic log. Thanks for your help! tower-diagnostics-20260324-1712.zip
-
[Plugin] Mover Tuning
Thanks. Posted on github
-
[Plugin] Mover Tuning
Done. How to download it?
-
[Plugin] Mover Tuning
7.2.4 and 2026.02.27
-
[Plugin] Mover Tuning
Cannot get the debug. Getting below error message: ERROR: The Mover Tuning Debug Package Generation Script has failed - no response from the bash backend.
-
General instability of Unraid server
I did some recent disk replacements and array rebuild. Also updated to 7.2.4. No idea what's wrong, but facing a few issues, which may have a common root cause? Parity build and copying files within the array is unusually slow (50mb/s). Dockers work, but GUI loads very slowly. And maybe most alarming, the mover does not move the files from share to array (though confirming it does). I posted separately in the plugin thread on the mover issue. Let me post a diagnostic and maybe someone can help me see what's going on. tower-diagnostics-20260314-0817.zip
-
[Plugin] Mover Tuning
Facing some issues. Unraid says "A total of 27 files representing 172GiB were successfully moved/synced by Mover Tuning plugin. Elapsed time: 2 mins 44 sec". First of all, this feels too fast for 172gb. But more importantly, I don't think anything was moved. My cache disk has filled up and stays 90% usage without moving files (though it says things were moved as above). Same happens when manually running the pluging. Tried both sync and move. Any known issue these days. Any log helpful to provide?
-
Disk errors while building parity
Unfortunately, I don't. Possible to do with VM?
-
Disk errors while building parity
I have yet another disk that potentially could include some deleted data that I can try to "undelete". UFS Explorer seems the best tool to do so. The "disk to try" is in an Unraid array. I was trying to use UFS Explorer in a VM, but seems that it cannot access network disks. I can remove the disk from the array. What would be the easiest way to "mount" the disk into the VM. It is formatted XFS, so Windows won't identify it, but maybe UFS can still do recovery? Can I somehow passthrough the individual disk or the full array to my Windows VM?
-
Disk errors while building parity
Ah yes... This explains. One of the dockers was trying to write something there, which must have gone into nirvana. Not literally enclosurename, but something like usb23e23enj2323, which is the name of my USB enclosure. I tried the fallen disk both in the USB enclosure as well as directly on the board. I will now give USB a shot with both disks. Let's see what comes out of it. I am quite hopeful that at least the "old" disk can undelete the files, which is around half of what I have on the fallen disk. Better than nothing and let's see how it goes. Will keep you updated. Thanks again for your help!
-
Disk errors while building parity
ls /mnt/disks/enclosurename/ This shows me the folder structure of the fallen disk. But no files Still really weird as I didn't even mount the disk and didn't even make it over the network. Maybe it's just some weird cached info and not accessing the disk?
-
Disk errors while building parity
There may still be some hope. I SSH into the server. Although the fallen disk is not even mounted, I can see it and it at least gives me the folder structure. No files though. Let me try to mount it as second vdisk and see whether UFS can do any magic with it. Otherwise, may go back to the old disk.
-
Disk errors while building parity
No sdc1, just the info below (plus of course all the other drives): sdc 8:32 0 25.5T 0 disk
-
Disk errors while building parity
Mmh... I don't see a partition for the "fallen disk" and that's why there is probably also no sdc1? It shows "format" button. So, maybe it's at a stage that I cannot even run an xfsrepair? UFS Explorer indeed seems a good choice. From the description, it may help with both the corrupt disk as well as the "fallen" disk. Any experience whether the professional version will do better compared to the standard version. Price difference is 10X. Also, any idea whether I can run it from my VM. I read somewhere that this is not possible? So, what I will do: New disk: Wait your guidance whether anything I can still try with xfsrepair? If not, give it a shot with UFS explorer. Old disk: Use UFS Explorer. Either standard or professional. Preferably from VM