darkside40

I think getting a Firmware upgrade for an unlabled card is nearly impossible. I mean if you want es good ASM1166 i think i would be a good Idea to buy a Silverstone ECS06, at least than you now the manufacturer.

Just a quick warning. Because i wanted a new faster controller card to replace my AAR-1430SA i grabbed a rather cheap (30€) Sata controller card with ASM-1166 chipset from Amazon. Okay they shipped a different model than it was advertised on the photos but okay, nearly all of the ASM1166 are unlabled etc. You can only differ them by the board Layout etc. What i got was that here: Using it resulted in kicked out drives etc. For gods sake with much help here in the Forum the situation was manageable. I dont know if the card is faulty or if the model is crap, but at least i could return it to Amazon. What i ordered now was a bit more expensive model, hopefully it works better: https://smile.amazon.de/dp/B09K4WKHKK?psc=1&ref=ppx_yo2ov_dt_b_product_details

Rebuild went okay, seems that everything worked out. Files are readable at least. Its mainly Media files, so if there is a bitflip anywere it is not the end of the world. That is the ASM1166 Card card which seemed to be faulty, there is no labeling etc: I have returned it to Amazon and ordered another one: https://smile.amazon.de/dp/B09K4WKHKK?psc=1&ref=ppx_yo2ov_dt_b_product_details Hopefully that works better.

Okay its rebuilding. Really many thanks for your help. I hope that will now go on without any interruption. Sorry for beeing so confused.

Okay power down, remove WD Drive, place the Seagate, assign it to Slot 6 and than bring array up and start rebuild?

So rebuild it onto the old WD Drive or the newer (previously unsused) Seagate does it matter?

Okay done. htms-diagnostics-20230105-1754.zip

Thanks, also the rebuild was on a fresh disk, not on the one with the red cross.

Could be if the controller was no good.

So WD Drive went Red, replaced it with a fresh Seagate, tried to rebuild, Disk 7 went red, stopped the rebuild, than placed WD back. Done nothing more. The Smart report of the WD drive was good, when i recall it right. So i doubt the HDD failed. Maybe the controller was no good.

Hold on stop, let me explain further, really sorry i an so confused right now. Let me recall what i have did befor i switched back to the old card. You are correct, i did tried to rebuild. I placed a new disk to slot 6. Then the disk 7 went red while rebuild. So i stopped the rebuild, and switched back to the WD Drive which is now in. Really sorry i am not really concentrated right now.

Beeing honest i dont know. Never had such a problem before. Is there anyway i can checkt if the contents of the disk are okay without starting the array? It showed that way after the second reboot when i switched back the controller, althouiugt i dont know if the array was autostarted. Was a bit confused

Was an existing array disk

Yes thats correct, disk6 was disabled first. htms-diagnostics-20230105-1720.zip

Hi there, i think i have a big problem now. After changing my Sata controller card i now have one disk with a red cross and one with an orange warning sign. Have not started the Array in normal mode only in Mainatanance Mode. I also have switch back to the old controller card. What can i do now? Is my data lost? Parity should be valid because i had no writes to it since i switched the card. Is there any hope?

@limetech could you or any of the team explain how the status is determinated?

Just want to check if the routine i am planning is correct. What i want to to: I have one 4TB Drive left in my array but more than 4TB left on a 8TB drive which is in the array. I now like to copy all that stuff from the 4TB drive to the 8TB drive so i can remove the 4TB drive, resulting in less power consumption etc. Screen is installed, so what i woul do now is. 1. New Config and than unassign the parity drive 2. Copy the stuff from the 4TB to the 8TB using screen an rsync -avX /mnt/4TBDisk/ /mnt/8TBDisk 3. New Config to unassign 4TB Ddrive an reassign Parity 4. Start array and Rebuild parity Is that correct?

Normally i dont have to reboot my server but today i did. And just like the last time appr. 2 months ago it didnt came up again. So plugin a display to see that the board directly hops into the UEFI. Unpluged the USB Stick, plugged it into my Laptop and it was corrupted. No big deal, i have a backup. The question is ask myself now is: Is there something wrong with the reboot feature in Unraid or is the USB Stick slowly dying. There was no problem reformating it and copying the files to it. Accouring to my License file i use the Stick since 2014. What do you think?

Wurde das auch als Bug gemeldet? Kaputter USB Stick unter unRaid ist ja alles andere als lustig. Edit: Ja ist passiert:

Und immer schön bei jedem Update checken ob die Version die du in /boot/extra hast auch noch mit der genutzen unRaid Version kompatibel ist. Ist schon ziemlich scheise das das Nerdpack nicht weiterentwickelt wird.

Warum nutzt du nicht einfach den Kalender in Nextcloud?

Have you tried what the debug message suggests?

Maybe there is no symlink from python3 to /usr/bin/python

I know which packages i need and i know how to install it, thats not the point. And yes many really good and useful Plugins rely on community developers. Myself i am maintaining my own fork of S3 Sleep, a function which should be in the core of unraid, because energy prises are rising and most of the unRaid Servers dont need to be 24/7, which means it would be better for the environment if they go to sleep. Guess what, the Core unRaid developers give a shit about it. https://forums.unraid.net/topic/118129-why-does-unraid-not-have-powersaving-eg-s3-functions-build-in-by-default/ Also a major issue: because there is no proper documentation about the Plugin System for years, only a few know how it exactly work. If they burn out you have the same situation like we have now with the nerdpack.

Just updated from 6.9.2 to 6.11 and saw that the Nerdpack is depracted. Also i have read that Limetech refuses to integrate a similiar solution. Dont know if i like the way unRaid is taking as the Windows of the Linux World. Managing the packages yourself by putting it into the correct folder, crossing the fingers on every update that hopefully Slackware and unRaid are not too different from each other, feels like you are back in the days of unRaid 5. The pre-Docker era, where extending unraid was an adventure. So instead of having a solution you now have to beg to the devs that they integrate that or that package, and if they dont think it is worth it you have to to it youreself. If you want to be on the safe side you also have to buy another unRaid License for a testing system, since there is no really free demo Version enymore or another solution for developers. Really, really frustrating, but me complaining wont change anything, thats what i have learned heren in the last couple of years