Hi All

 

I was playing with a script (Yes I know don't use script's if you don't understand them 100%)

Anyway this was a backup to a UAD drive r-sync incremental but I did some path wrong and I got this

 

 

And just before this it stopped my VM and wrote:

 

The positive is that I do have access to MC:

So what can or should I remove before trying another reboot?

 

Br

Casperse

 

 

 

 

I have checked the Flash/Cache/and CPU and memory load and everything seems ok

But after reboot I am stuck at:

 

 

 

 

 

 

 

Ok found that the passthrough drive was "sdk" before

But after a reboot its now "sdn" how can the naming ID of the drives on the Unraid change? Very scary

1 hour ago, casperse said:

Ok found that the passthrough drive was "sdk" before

But after a reboot its now "sdn" how can the naming ID of the drives on the Unraid change? Very scary

The sdX designations are always subject to change as they are assigned dynamically by Linux.    Unraid does not rely on the device name to identify drives, but instead the disk serial number.

3 hours ago, itimpi said:

The sdX designations are always subject to change as they are assigned dynamically by Linux.    Unraid does not rely on the device name to identify drives, but instead the disk serial number.

But I was told using passthrough from a drive to a VM I should use the sdX?

Is there another way to secure that it doesn't break after af reboot?

 

12 minutes ago, casperse said:

Is there another way to secure that it doesn't break after af reboot?

If you look under /dev/disk at the Linux level you will see several folders giving ways that drives are identified in an invariant manner.

3 minutes ago, itimpi said:

If you look under /dev/disk at the Linux level you will see several folders giving ways that drives are identified in an invariant manner.

 

So how would I go about defining that in a VM so I don't have to update this all the time?

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/sdn'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>

I guess people that passthrough HD's and GPU have some fix to do this

 

2 minutes ago, casperse said:

dev='/dev/sdn'/>

This entry will typically be of the form

source dev=/dev/disk/by-id/xxxxx 

where 'xxxxx' is correct for the disk in question.   

So like this:

 

source dev=/dev/disk/by-id/ST10000NE0004-1ZF101_ZA21DG4A

  - Sorry for being Thick...

23 minutes ago, casperse said:

So like this:

 

source dev=/dev/disk/by-id/ST10000NE0004-1ZF101_ZA21DG4A

  - Sorry for being Thick...

yes - as long as that is the correct serial number for the disk you want to pass through.

 

FYI:  the /dev/sdX number do not change often as normally they are allocated in the order Linux sees them (which is timing dependent so normally consistent (but not guaranteed).    However if you accidentally pass through the wrong disk because the sdX value changed it can be catastrophic making the contents of that disk corrupt - not something one wants to take even a small chance of happening.

Ok so I started changing my drives:

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ST10000NE0004-1ZF101_ZA21DG4A'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>

Serial from the dashboard ID:

 

And trying to start I get:

Update tried the serial number I could save the VM but it couldnt start

 

Sorry @itimpi this doesn't seem to work?

 

Edited October 21, 20205 yr by casperse

It works fine on my VMs - not sure why you are having a problem.

I think I found the solution you have to add "ata-" then it works

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-ST10000NE0004-1ZF101_ZA21DG4A'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>