mdrodge

Wow thanks for the quick response guys. I have 2 brake out cables 4 sata on each. I don't know anything about sas but they seem like normal sata at the drive end. It's plugged in fine and seated nicely. It won't drop out until i try and transfer files so i think it's still alive. (I was attempting to move files from my old array witch is 3 drives on the chip set to 7 smaller drives on the hba.) Also with the hba i loose drive temperature readings even for drives connected to the chipset.

A cable problem could be possible but seems unlikely as it effected all drives at once and the unit + cable is brand new. (Though i don't know much about hba's and this all seems like quite a rabbit hole)

No idea. I just used what was on the in the guide so I'm guessing you could be right. Dam it, the card is behind a vertical gpu and surrounded by a hard line water loop. That's a lot more work. Ok cool. Where might i find an update please? Though the guide was updated in June 2020. Do you mean versions before p20? Or is there sub versions of p20? I'm confused.

Just flashed me card. It seemed to go correctly and now i have all the drives in unraid. I started moving files around in the array and after a few minutes all drives gave CRC Errors and the card seemed to drop out. I turned of the system and tried to position a case fan near the card (a bigger card made that only slightly useful) but it still dropped out after reboot. Does anyone have any insight? I've only ever used the chipset before so I've got no idea what to expect.

I know but i have to many for this mystery task that I'm yet to find and not enough for the task that i am currently facing. It's not like I'd put files on it that could just as easily be accessed from my UNRAID server wirelessly. Maybe I'll make some modern art with them or maybe grind them up and use them to grit my path when it snows. (I still love unraid and it's not even limetech's fault as such but it's annoying and i wish there was something I could do about it) I'll get one once I've fully built the new device and not before (i am not risking any more sticks than necessary especially when you add on the risk of getting a fake USB stick)(That's quite a big risk to, I've had a few of them over the years not just with UNRAID) Can i boot from floppy disk instead? (joke)

Yes it says that above. It's still frustrating and obviously it's going to cause complaints from time to time. I think those complaints are justified. (In case you haven't heard there is a whole wave of Ryzen owners with USB issues at the moment, it's easy to blame a USB stick when it's actually a BIOS issue) I'm still not happy with this. They obviously have a mechanism to block the things in the first place. So why not just not block them in the first place? The GUID are unique and if they are not tied to my license any more then that's enough. I am wanting to buy an additional license but I'm stuck at the moment (i have plenty of working USB sticks that are suitable) It's like saying "i don't have a mechanism to prevent myself from punching your face..... That makes it okay for me to punch your face." I'm not expecting a fix. I just wanted to voice my feelings.

Usb sticks

It can also happen if you move from one usb drive to a new one (they block the old one) I thought my usb key had died so i got a new one but i needed something to use in the meantime (turns out it was an Ryzen USB bug) so then i moved to my new one (that was 2 usb keys blocked in one day. In total now i think i've gotten 4 blocked and they are all good keys. I'm just about to replace my synology with a itx build and unraid (i'll soon have 2 unraid devices) I'm starting to get fed up with buying new usb keys each time i want to use one. I understand they are trying to protect their software but what about my pile of unusable usb keys!!!! I really should be able to use one of those usb sticks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

In remote desktop did everything look OK in hardware manager?

@audiocycleWhen you say blank display do you mean on the vm side or on your vnc?

Iommu groups are nicely split? I'd start simple mate. First set up with just a hdd and vnc Then once I know that works I'd add a gpu then once it's working I'd go for the usb etc.

Hang on. Before you reboot try logging in with your phone or something and cycle just the vm

Are you sure that is your problem? Why daily reboots? Are you stable?

Yes. Mine has been stable for a while. P.s I got it stable on i1440 but I've recently switched to q35 because I wanted stutter free gaming. Acs downstream and vfio unsafe interrupts is what I was fiddling with and had some luck. I've still never got it working properly with only 1 card I've tried that on a few different systems over the past couple of years. Everything mentioned above is the best advice I have though. Mine would boot unraid then go blank and I'd have to kill the vm and launch it again a few times with my phone to get the gpu to take over correctly (I gave up and put in a gt710 in slot 1 so I could have full access to the gpu in slot 2)

Seeing as I've spent most of the day on that I think I'll go double rebuild and save some time. (I've been preclearing for a week already and I don't want a spaghetti monster for to long or my sun might get at it)

I feel like the steps should be, go to settings / vm manager and switch Enable VM's to no, then do same in settings / docker, Then stop the array, Then uncheck the drive, Then start the array, Then stop the array, Then re-add drive, start the array (it starts to rebuild) Then go and re-enable vm's and docker. (The only difference is the additional steps of stopping libvert and docker before) If you don't do that then libvert never starts and you'll end up stopping and restarting the array repeatedly trying to get the vm's to come back (even if my vm's and libvert are not part of the array)(I keep libvert and docker on a 2nd cache pool and vm's are passthrough only)

Thanks. I didn't spot that. So now I'll rebuild just so I can upgrade parity 1 then rebuild and upgrade parity 2 then rebuild and swap disk 1 (the one I'm currently rebuilding) then rebuild and repeat working my way through the whole array. I guess at least I keep parity now.

Can anybody explain how to re-enable a disk?? Someone above asked but go no answer. ___________________________________ So how do we re-enable a disk once it's been disabled??? I've been searching this for a while after I had a bad cable a couple of months ago. Now I'm in a similar situation again. I've got double parity now and the disk that is disabled is also good (1 year old 0 error). It has just happened (a physical event). I just need a way to un-disable it. It makes no sense. Last time I had to use "new config" and lose parity and re-import the data. Now I have double parity but still no way to re-enable the disk without ditching the config and invalidating the parity. I understand that if a drive falls you need it to behave in this way but why is the no way back even from a bad cable. Maybe I'm missing something fundamental but I am normally trying to do this sort of bring it online fix from a phone so I may not be seeing something. As far as I can tell there is no redundancy that actually functions if you want to reuse the same drive that was disabled. (Double parity should be able to tell if one drive has bad data so I see so issue with spinning up a "bad" drive anyway. (Also my drive isn't bad))

Man preclear is brutal. I think it's killing one. 47c but still going at 215mbs But it's ticking. I think it's bad. Let's see if it lasts. If this doesn't kill um I'd say they are good but I think that one is going back either way. I've heard that noise before (20 years ago) and it's not good. (As you might have noticed I'm new to preclear so I don't know if I should worry about the click (click if death maybe)) and i didn't bother with my last drives because they were new wd golds and the warranty is 5 years. I'd possibly get no warranty if I shuck them so I'd need to feel confident. These will be my new double parity if I can trust them.

Was about to shuck 2x 14tb wd my books. Thought I'd run preclear before I did. One of them started ticking for a few minutes but seems to be running. I'm only on the first pass though. At least I know to be suspicious of it and if it does it again it's going back. It's better to identify a faulty drive early and return it than it die later. (Especially if it's been shucked out of a usb) The ticking has stopped now so I'm not sure but I'll make sure I'm happy before I shuck it. I think preclear adds random head movements so I'll wait and see what happens next. (Or maybe it was my plumbing making the noise)

o wait sync command seems to be part of that command. yep that's definitely it it's going so much better now unfortunately i need to run the command each time a file created but i'll settle for hourly and just clear out all the Emby Auto Organise errors later

I might have found the problem for me. I run a script to fix permissions on files downloaded #!/bin/bash /usr/local/sbin/newperms /mnt/cache/Downloads with a custom schedule of * * * * * aka the script runs once a minute. Once i thought about the time stamps it made me think about this script. Not sure how fixing permissions on the cache drive would cause this issue though. still I'll just disable until I'm finished then do a full docker safe permission once it's all done.

Jan 01 22:14:35 preclear_disk_51474B4254555954_93420: Resumed Jan 01 22:15:13 preclear_disk_51474B4254555954_93420: Pause (sync command issued) Jan 01 22:15:13 preclear_disk_51474B4254555954_93420: Paused Jan 01 22:16:03 preclear_disk_51474B4254555954_93420: Resumed Jan 01 22:17:06 preclear_disk_51474B4254555954_93420: Pause (sync command issued) Jan 01 22:17:06 preclear_disk_51474B4254555954_93420: Paused Jan 01 22:18:48 preclear_disk_51474B4254555954_93420: Resumed Jan 01 22:19:13 preclear_disk_51474B4254555954_93420: Pause (sync command issued) Jan 01 22:19:13 preclear_disk_51474B4254555954_93420: Paused

I get a similar issue. Preclear is working but it go's for 5 seconds then pauses for 5 seconds and repeatedly does this. I'm going for 2 full cycles. I'm 42 hours into doing 2x 14tb usb drives at the same time. I'm still erasing in the first cycle. At this rate it'll be a 2 week process. I will wait because I don't want to shuck them until I'm sure they will not fail but dam Maybe it's a usb bottle neck for me but everything else on the system is fine. I thought it might be an Unassigned devices bug????

I know windows definitely "ticks" and buildzoid did a YouTube video showing with an oscilloscope that it even caused boost to come on for ryzen cpu's. The effected vm has just fired up runs sonarr and has just fired up a download so it's busy now so that will effect my results. The vm I tried it on has no hardware apart from a harddrive passed through. The other vm has all the passthrough and I've not touched it yet because it is my terminal. Even with or without using the system if I look via my phone I see the same behaviour though so I don't think that's what is going on. It's an overhead of some kind, ot never go's away and the system becomes unresponsive if I tax it because it thinks it can use core 1 but it's already at 80% I tried to having an extra core in the cpu isolation compared to the cpu pinning to see if I could move that load to it and have the vm's unaffected by it but that didn't work.