mdrodge

When in dos and flashing i get "Warning! IO Base address high. Currently not supported." I was getting that originally aswell but each section finished with "success" Is that okay?

I have removed the drives from the hba but the hba is still in the slot and the chipset is displaying drive temperature again. (I'm just waiting for a large transfer to finish then I'll get back to working on it) ((For the dos part of the flash i had it in slot 3 but i had to give up and move it to slot 1 for the efi part so maybe i can just reflash in slot 1)) For anyone wondering. I had 7x 5400rpm wd red's attached.

Okay that's good to hear. I might try a reflash in a minute. (I have that long number written down anyway)

6.9.0 rc2

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.

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)

4194304 is the golden number for me at the moment

Agent Run Out Of System Notify Watchers Fixed (Unraid Terminal) open terminal (the icon that looks like (>_) on the top right of the main unraid gui on and type cat /proc/sys/fs/inotify/max_user_watches This tells you how many watchers you have (8192 is stock), to change the amount, type sudo sysctl fs.inotify.max_user_watches= followed by the number of watchers needed. There website says some os's only support 524288 and setting it higher does nothing BUT at 1048576 i still get the error and at 4194304 I don't so unraid ISN'T effected by this I use sudo sysctl fs.inotify.max_user_watches=4194304 DO NOT SET ABOVE 2147483647 You can set this once and forget it (doesn't need resetting on boot) Just wanted to share this with anyone who might have the same issue

Cron Schedule needs a space. (* * * * *) not (*****) that explains my problem.

So i still don't know how to use it guys. I've got mc open in terminal. I've got a file that I need to remove. None of the keys do anything apart from f8 and that tells me Cannot stat "file.xml" Structure needs cleaning. Even just an explanation of how to launch the help would be awesome. (If it has a list of commands)

My UNRAID server corrupted a vm a couple of days ago and I had to wipe that vm (i have 2 windows 10 vm's) Once I'd finished setting up the vm I noticed one of my shares had become inaccessible after some tinkering it became intermittently accessible. I'd been pulling my hair out for hours. I noticed it was only 1 share that was effected and it was the same on both vm's and my phone. I stopped any docker that might use the share, then I renamed the effected share and set up a new share to replace it (making sure it was on the same harddisk to avoid long file transfer) Then I used dolphin in docker to move all the files across (9tb on a 12tb drive took about 30 seconds) after that I checked everything had moved and deleted the broken share and restarted my docker apps