steve1977
-
Posts
1,471 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by steve1977
-
-
I have an unassigned device that used to be formatte as XFS. I an trying to format it as NTFS, but unsuccessfully. See below what I did:
1) Remove partition
2) Select Format and select NTFS. Confirm with "Yes"
3) FS now shows as "XFS" and it is not possible to mount the disk
Happy to provide logs if helpful. Any thougths appreciated!
-
Connecting 8 HDs in a USB enclosure. Has worked for many years, but now stopped working. Somehow, the disks no longer get detected. Anything you can see in the logs? Thanks for your help!
-
Great, thanks!
-
Thanks a lot. Maybe a stupid question. Does the secondary disk that I'd like to passhtrough to a VM directly need to be formatted as NTFS or can be in XFS?
-
-
That doesn't read ideal. People delete "historical devices". And in this case, it seems to require to open the server case and unscrew a harddisk?
-
Thanks, let me understand option 2 as this is what I was trying to do. "Pass the disk" means to enable to passthrough featiure in UD?
-
Yes, I detached it. Seems I shouldn't have done this. How to re-attach a detached disk without historical devices?
-
And here we go with the log. I have passed through and then used historical devices to disable (to get it back). Thanks!
-
I could change my hardware setup that the nvme has a dedicated sata, so it would not be together with others. But I'd assume it may still be greyed out (e.g., I have my cache disk on a dedicated controller, but it is also greyed out). Do I need to passthrough the disk that it is not greyed out? Or unmount it?
-
Yes, it does show in historical devices and that's how I got it back. But obviously, that's a risky approach as I wouldn't know how to get it back if I were t delete the historical devices (which luckily I hadn't done yet).
-
Thanks. Unfortunately, it is greyed out. And even if it wasn't greyed out, it is in iommu group 17 together with other disks.
-
Here we go. I only screeshot the right side, not to post the device IDs. If I enable passthrough, the disk just drops from the view. I can also post this, but it is identical to below with one disk less.
-
On 12/28/2020 at 6:38 AM, dlandon said:
Major new release of UD:
- "Where are the switches?" The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog. This is also where the script is modified. This saves some real estate on the UD page and keeps the page refresh smooth.
- A "Show Partitions" switch has been added to set showing all partitions by specific hard drive device and not generically as before. The option to show all partitions has been removed from the UD Settings.
- Read and Writes and all other status is updated every 3 seconds. You don't have to refresh the page with the browser to get an update.
- Mounts, unmounts, disk spin, and read and write status updates are much smoother. This is the same as the array pages. The values just update in place.
- You can see the current status of the device switches in a tool tip by hovering your mouse over the settings icon.
- Automount of remote shares and ISO files is off now by default. If you previously had a remote share that automounted and is not now, just edit the settings and turn on the Automount switch.
I've been trying to achieve this for a long time, and I think I finally got there.
Understand how to enable "passthrough". However, not clear to me to disable it again as the disk is no longer visible in the UI after enabling the passthrough.
-
Attaching log file
-
My VM is running out of space due to too many Steam games
I would like to put the Steam games on a separate disk. Thinking to passthrough a NVME Disk to the VM and then move all Steam games to it.
Is this possible and how to do it?
-
21 minutes ago, Olivier POATO said:
Thank you so much for your advices @ghost82 i've finally managed to have Fifa 23 working on my boy's Win 11 VM.
I've just wonder how some of you successfully created the drive to make it readable by bios. On my side, i've failed. But as a work around i put the files on a a USB Stick and put it on the VM.
Last thought, as now unraid is TPM 2.0 friendly, why not to go full steam ahead and let lambda users to be able to configure a VM withe secure boot activate within a proper template ? ( i second @steve1977's remark)Thanks for sharing. Can you share what you have done from above to make it working? With amazing help by @ghost82, I followed all steps above. But the issue reamsins. Still no Fifa 23 in the VM for me.
-
I filed a bug report on github: https://github.com/Taxel/PlexTraktSync/issues/1394
-
Thanks. This indeed seems to have solved it. It now shows as "insecure" in my browser. Is this expected?
-
Tried from different devices and browsers.
-
Weird issue... I am running Unraid headless. I can tell that it is working as I can SSH into it. However, I cannot access the GUI. When entering the IP in my browser, it defers to a long https://[removed].unraid.net/ address and says "site cannot be reached".
Any thoughts? Thanks!
-
Docker: Docker Service failed to start
VM: Libvirt Service failed to start
Not sure, but maybe my cache drive "died"?
Any advice from the diagnostic log for me? Thanks!!!
-
Thanks. Unfortunately no luck. Still getting the error message "This software cannot be used at the same time as the game: Hypervisor".
-
Thanks. I had tried this before, but unfortunately unsuccessful. From what I have googled, the issue is that the Fifa anticheat is on "kernel level" and not on "os level". Whatever this means, but this may make it more difficult to hide that the game is run inside a VM?
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
in Plugin Support
Posted
Thanks. And when you are at it, there is another thing to check out.
You kindly included a feature that prevents to remove disabled disks from historic. However, now there are many disks now that are actually part of the array (active), but show up under historic disks (and cannot be deleted). Not sure why, but it could be because they were mapped under a different drive name before and now no longer show up.