JorgeB
-
Posts
67,797 -
Joined
-
Last visited
-
Days Won
708
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
You should start your own thread, and post the diagnostics and the log from the syslog server after a crash.
-
Do you know which filesystem it was using? -
Try this:
-
Which GPU model? For older Nvidia GPUs we found that the below fixes it: https://forums.unraid.net/topic/124890-gtx650ti-code-43-with-windows-10/?do=findComment&comment=1139615
-
Yep, corrupt ISO.
-
Yes, still keep old disk intact for now.
-
Not really, both types are pretty common.
-
After downloading the file in Windows run in Powershell certutil -hashfile path_to_file MD5 After transferring the file to Unraid run in the console: md5sum path_to_file Compare both results.
-
Forgot to mention, that m.2 device is SATA, not NVMe, so it will likely share a standard SATA port, check board manual.
-
You can leave the array running, it will just be missing any data that was on cache.
-
No signs of a valid filesystem being found on the emulated disk4, that's very strange assuming parity was valid, try running a manual check to see if a backup superblock is found, but not very optimistic, with the array started in maintenance mode type: xfs_repair -v /dev/md4
-
Then the cables are good, I never used optical drives with an LSI, don't know if they work, though according to Vr2lo they should.
-
Unassign disk5 from the array, start the array, stop the array, create a new pool or use the UD plugin to work with the old cache, do you know what filesystem it was? The primary superblock will be destroyed, but it might be possible to recover a backup superblock, alternatively use a file recovery util, like UFS explorer.
-
Do you mean the emulated disk4 is unmountable? If yes: If it's not that post new diags.
-
Jun 26 02:28:44 Tower kernel: ata1.00: qc timeout (cmd 0xef) Jun 26 02:28:44 Tower kernel: ata1.00: failed to set xfermode (err_mask=0x4) Jun 26 02:28:44 Tower kernel: ata1.00: disabled Disk is dropping offline soon after being detected, try with a different model disk, also make sure power/SATA cables are good, or just replace them.
-
Wait for the rebuild to finish then do what I posted above. it can get more complicated if the rebuild doesn't finish due to errors, but errors are much more likely on reads vs. writes.
-
Then it should be showing here as an option.
-
That still looks to me like a corrupt ISO, maybe it's getting corrupt during the transfer to Unraid.
-
If disk6 was never formatted you can do a new config without it (tools -> new config), then check "parity is already valid" and start the array, stop the array, and replace disk4.
-
Enable bridge in network settings and then use br0 as the VM NIC.
-
Sorry, I don't follow, disk5 is a HDD, and according to the diags there's no NVMe device connected to your server.
-
Was disk5 your old cache? That's not an NVMe device.
-
It wasn't showing in the first screenshot, also note that you have to bridge the NIC(s), e.g., br0, to have Internet access on the VM.
-
VM config is not showing the Network section, below the sound card, do you have any network bridges created?
-
That can't be, you're likely confusing share data with device data, diags posted don't have any NVMe device connected, where is it now?
