Disk Errors on Passthrough SSD

[Symon]

tower-smart-20190129-1319.zipSince a few week I'm getting strange errors in the log of unraid:

 

Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument
Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 8708 has a size (24) differing from the directory specified size (4096).
Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument
Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14458 has a size (24) differing from the directory specified size (4096).
Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument
Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14501 has a size (24) differing from the directory specified size (4096).
Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument
Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14531 has a size (24) differing from the directory specified size (4096).

I managed to find out that it is related to an SSD disk which I mounted with unassigned devices and passed thorugh to a Windows 10 VM VM.

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

If I unmount and remount the disk, the errors will go away but usually reapear after a few hours

While the errors are shown, I experience stutters on the VM and Games that are stored on this disk but I still have access. I can't tell whether this is because the log of unraid is getting spamed or the disk is not working properly.

 

I already did an extended SMART test but there are now errors shown (File is attached). I'm kind of lost right now what to check next and hope somebody else has a clue

 

 

tower-smart-20190129-1319.zip

logs.zip

Edited January 29, 2019 by Symon

[JorgeB]

If the SSD is being passed through to a VM it should not be mounted at the same time by UD, that can cause filesystem corruption and data loss.

[david279]

use virtio as the bus for the disk It will help. Also look into virtio scsi for ssd pass through as it allows trim and could give a bit more performance but setting it up is a bit more of a process.

[Symon]

1 hour ago, johnnie.black said:

If the SSD is being passed through to a VM it should not be mounted at the same time by UD, that can cause filesystem corruption and data loss.

Thank you.. I didn't know that .. I thought it would only work with pass through if I mount it first

I will stop doing that from now on

[Symon]

1 hour ago, david279 said:

use virtio as the bus for the disk It will help. Also look into virtio scsi for ssd pass through as it allows trim and could give a bit more performance but setting it up is a bit more of a process.

Thanks for the tip .. I will try to change this and see if the error messages will stop

[Symon]

3 hours ago, david279 said:

use virtio as the bus for the disk It will help. Also look into virtio scsi for ssd pass through as it allows trim and could give a bit more performance but setting it up is a bit more of a process.

I tried to find a place were the two setups are compared and a guide on how to pass through the disk with virtio as you described but couldn't find either...

 

Did you test Sata vs Virtio of is VIrtio scsi just always better? Do you have a description or example on how to set it up (Primary disk is alreadry running on virtio but as a Vdisk and secondary should be passed through). I found some ressources outside of UnRaid community but am also a bit worried to messup my system

Edited January 29, 2019 by Symon

[david279]

Virtio is always better. I have my vm setup with a SSD using virtio scsi and a regular hard drive using virtio. It also has a nvme drive passed through as my boot drive.

Sent from my SM-N960U using Tapatalk