phbigred
-
Posts
265 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by phbigred
-
-
You appear to have 16GB of memory in the system assigning 12GB including overhead is why you are at 83% used. Is your jump drive 64GB for unraid? Think that's where your 55GB comes from.
-
#1 within a minute or 2 of purchase. You drop your key on the drive and boot up.
#2 this includes cache, parity, unassigned devices mounting at boot. USB drive for unraid doesn't count.
#3 USB 2.0 or 3.0, SanDisk has a good reputation. If you can plug it into a USB 2.0 port on your board. Historically has a better result, but 3.0 is fine.
#4 Updates are only manual. You have to initiate them.
-
1
-
-
-
Everything should work. Recommend 3 slot pci-e motherboard. Install your nic in the 3rd slot at pci-e 2.0. Don't forget you need to get ddr4 memory.
-
You could use Krusader docker to move from disk to disk. That's the preferred methodology. Then once you confirm you got off all the emulated data do a new config making sure to note which serial number your parity drive is.
-
Getting odd logs and a D3 reset error since upgrading to Ryzen 3000. Now throwing code 127's when passing through the Phison controller.
Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:32:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Jan 1 16:41:00 unraid-box kernel: nvme nvme0: failed to set APST feature (-19)
Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:32:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:01:00.0: Refused to change power state, currently in D3
Jan 1 16:41:00 unraid-box kernel: nvme nvme0: pci function 0000:01:00.0
Jan 1 16:41:00 unraid-box kernel: nvme 0000:01:00.0: Refused to change power state, currently in D3
Jan 1 16:41:00 unraid-box kernel: nvme nvme0: Removing after probe failure status: -19Thoughts on a solution? I'd love to get my system back functional with NVMe passthrough, having to use an old image on a sata based SSD currently.
-
Was there plans for a release updated for 6.8 stable?
-
SVM for virtualization is a biggie. If doing passthrough using multi-function in VM Manager for ACS override. Otherwise it's pretty much plug and play.
-
5 minutes ago, cypres0099 said:
Ok, cool. So you're saying that I shouldn't have to select disks from the drop down and manually setup the array? It'll just boot up and probably start the array correctly?
You got it. Should be plug and play.
-
Take a screenshot as a backup. But the order of disk serial are kept on the USB drive for unraid. 99% of the time if you wire up everything properly and everything is seen properly it will just work. If you are doing anything with IOMMU passthrough with hardware for vms you'll need to do a bit of resetup there otherwise you are set.
-
1
-
-
Quick question, were there changes in this build that affected the br0 settings with VMs? I can't isolate out VPN vs no VPN traffic without using the local client now. Used to just add the IPs to an alias list that routed it on the individual br0 IPs. Pfsense gateway routing used to work for unraid now doesn't function unless I remove the unraid server IP from the VPN.
For clarification I haven't tested against the Limetech build as I just figured this out yesterday. Might be worth some testing.
-
This worked beautifully on my msi x370 sli plus that I updated for ryzen 3000. Was pulling my hair out trying different settings to get iommu working until I found this thread. Mucho kudos, now if we could get Limetech to implement these fixes....
-
Most likely a setting in your router needs to be added. Try going to the IP address directly as a workaround.
This is the workaround I added to the DNS resolver of my router.
-
CRC errors may be nothing more than a loose cable. The drive that died might be the same thing. Are you by chance using onboard connections that might be Marvell controllers? New board new connections might be something as simple as that.
-
Have you attempted turning off docker, going to advanced. Delete docker image file under settings -> docker and rebuild? May need a reboot afterwards to see if that clears it. Then restore your Dockers.
-
It's for others to go through that have more experience reading diags than I.
-
1
-
-
Recommend going to tools tab and diagnostics. Upload what you get from it. It'll show more than the log info.
-
When is your mover set to run?
-
1 minute ago, Frank1940 said:
The UDMA CRC errors are not a disk problem in 99.99% of the cases. They are a transmission of the serial data failure between the disk drive and the SATA controller where the data is converted back into parallel data. The data stream is sent with a check sum and if that check sum test fails the data is resent. However, they do slow down disk operations because the correction process suspends further transfers until the error is cleared.
I am assuming that the reallocated Sectors are very recent. (These sectors themselves are not a problem because they will never have data stored on them again!) If they are recent, they could be an indicator that the disk is entering a period of slow decline toward failure.
Good point with the crc. I'd say Op go with your best judgement.
-
Both are going to take time. Turn off anything that could be writing to the array. Pop out the parity and get that swapped. Order another drive to have on standby. Worst case you have a parity drive you can use for recovery should things go belly up. That's the route I would suggest.
-
If you have a prompt login and type diagostics just to capture a log.
First step shut down and reseat all cables. The drive dropping off may have had a similar problem. You mention an lsi card is it seated properly in the mini sas connection? May be worth finding out if your motherboard has Marvell controllers. Having this much weirdness at once makes me think whatever the data connections are being driven from is having a problem with unraid. Rerun the data cables/swap. I'll leave it for the more experienced to give more ideas. Also to be sure you aren't having any brownouts correct? Hopefully using a UPS of some sort.
-
https://wiki.unraid.net/Shrink_array
You can shrink your array, I've done it as few times. If you are looking to reduce the count of disks go with a single parity. Remember it has to be = or greater than the largest drive. Word to the wise... If you are thinking of encrypting later on, you may want to do it from the beginning as in-place encryption isn't available yet. Also confirm your nvme drives aren't using a Marvell controller, known issue with Linux.
-
Try the commands in XML mode listed by testdasi for x16 pci-e. But overall bump to 2 vCPUs minimum if you can afford to.
-
Sounds similar to a problem SpaceInvader One had. Might be worth attempting a move to QT35 instead of i440fx machine type. I had a similar problem with my RX580 passthrough.
Unraid 6.9RC1
in General Support
Posted
Yeah the GSO bug is back in this RC1 for me. Not enough to push me off it but the log is filling up and will need to manually purge periodically until remedied.