CBMX Posted May 20, 2020 Share Posted May 20, 2020 Yes, yes, it is strange, but it is what it is... and I dont understand why. Also I did lost my VM. And How do I know it is the VM and not the disk?, because I did it twice!!, first time i thought "Mhh... I did forget to format this disk!?", now, second time i have lost not only the disk VM and the work that was there, I will also have to spend 4 hours copying data to the disk... 1. I did create my VM (with help of Spaceinvader One's macinabox) 2. I did play around with my new machine, setting up for some work... 3. I did install a some dockers and configure them.... 4. I did change the xml to passthrough an AMD RX570 5. VM starts ok, but at a point i got a read error from the server 2 disks with read errors. 6. I did re-start the machine, but this time one disk is unmountable but no errors. 7. Im here. So the vc is IOMMU group 19:[1002:67df] 25:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) IOMMU group 20:[1002:aaf0] 25:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] affected disk is [6:0:0:0]disk ATA ST4000DM004-2CV1 0001 /dev/sde 4.00TB The code I did use for passthrough : <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x25' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x25' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> **I was waiting some days before to use the biggest disk as partition (5TB) because I have some valuable info there. What kind of help I want?, not much, if you have a way to recover the disk it will be welcomed, also if you can point out what im doing wrong so i will not screw this up again. Thanks!! Helpme SPACEINVADER ONE you are my only hope! newarchivaldo-diagnostics-20200520-1745.zip Quote Link to comment
CBMX Posted May 20, 2020 Author Share Posted May 20, 2020 Also, using xfs_repair: xfs_repair -v /dev/sde Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ..found candidate secondary superblock... unable to verify superblock, continuing... [dots, a lot of dots] Quote Link to comment
JorgeB Posted May 21, 2020 Share Posted May 21, 2020 Diags are after rebooting so can't see what caused the problem but that's not how you use xfs_repair, not against the device or you'll invalidate parity, and it's missing the partition anyway, see here: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Quote Link to comment
CBMX Posted May 21, 2020 Author Share Posted May 21, 2020 13 hours ago, johnnie.black said: Diags are after rebooting so can't see what caused the problem but that's not how you use xfs_repair, not against the device or you'll invalidate parity, and it's missing the partition anyway, see here: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Thanks JB Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.