lelejau

Replaced my PSU for a better one. Rebuilt my drive, everything seems to be fine now. Probably my bad PSU must have caused issues in the first place. Ran an extended smart test and rebuilt the drive, 0 errors, 0 warnings. 100% success. Thanks for your help, I'm glad my unraid server is now back to normal again. I had some issues with case insensitive share names, but I found your solution in another thread. Moved the cfg file to tmp folder and re-applied settings from the GUI. Cfg was re-created and everything works now. I think this is the best software purchase I ever did, the support here is outstanding. I couldn't thank everybody enough.

Funny it says 1b.0 and I passedtrhu 1f.0. Does that mean anything? I'm not too familiarized with this subject. So I read about rebuilding the drive onto itself. That's what I need to do now to fix the array right? If so, I will first buy a new pair of sata cables before doing this process again, to avoid any new errors. Is a PSU problem even a thing to consider here? Not enough power? I have a 500w PSU (not any certified fancy font though) I'm also running an extended smart test. Short test completed with no errors. https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

It was already set as AHCI. Maybe something wrong in proxmox config?

I thought I had passtrhu the devices correctly? What should I do? Is it safe do reboot unraid and try to start the array again? 02:00.0 and 04:00.0 are my NVMES used in cache. 1f.2 is my entire sata controller from motherboard

IT was solved. Probably related to that github rate limit. Everything is working fine now.

I was running a parity check and I got some read errors. After a while, my disk went offline. Parity is almost finishing but I'm not sure what I should do next to keep my files safe. Has my HD gone bad? What steps should I take to make my array protected again? I'm attaching diagnostics and some screenshots. I'm running Unraid on Proxmox. magonhacloud-diagnostics-20251104-0741.zip

it's completely random, every time I refresh they change. Something weird is going on..

Same behaviour I suppose?

I'm wondering if this issue has something to do with I'm being unable to update plugins, or even check if they are updated at all. Seems like South America is constantly getting HTTP 429 when trying to access some github endpoints. GitHubReceiving the 429 error eventhough not using github for a...Select Topic Area Question Body Hi folks; I am ot a developer but I am a just normal user of a PVE machine and the famous "PVE Helper Scripts" to create LXC containers. I am not a heavy user and on...

o meu servidor nao tem tanto uso assim. Comprei um senno vt, chegou hoje. Mas vou devolver. Barulho insuportável. Da pra ouvir de várias salas de distância, tem nem como. Foda pq eu tava hypado esperando chegar, nunca broxei tanto na vida... alguem indica um que nao faça barulho? nem precisa ser dupla conversão e top de linha, pelo jeito esses devem ser os mais barulhentos. A sala aqui é toda aberta, não tem porta. Se fizer muito barulho fodeu

It still happens. No apparent reason. Using NVIDIA GTX 1660. It works fine for several days then it just stops out of the blue. Vendor command returned unparseable data.

Well, everything worked in the past. My switch is gigabit, my desktop is gigabit and unraid says it's interface is also gigabit. The cable is new. My desktop: Unraid: About the iperf I'm still trying to figure out how to use it. Well, that was weird. MY desktop was indeed only reaching 100mbs speeds in speedtest even though windows said it was in gigabit connection. So I rebooted every router and switch and my desktop got normal speeds in speed test. Also speed transfer is back to normal. Weird. Now I dunno which answer to mark as solution

So I'm moving some files into my server and speed doesnt go beyond that. I've never had any issues regarding speed in my array. I must say I've been updating my server to latest versions but it's been a while since I used my server so I can't really tell when this started to happen. magonhacloud-diagnostics-20250308-0144.zip

Bom eu já abri um tópico aqui uma vez sobre o mesmo assunto e no final me recomendaram o Senno VT 1000va. Lendo algumas reviews falaram que tem bastante ruído porque a ventoinha fica ligada todo tempo. Alguém que tem pode confirmar? Essa parte do barulho quebra demais aqui. Eu queria um nobreak só pra poder deixar meu servidor ligado sem preocupação. As vezes a energia da uma piscada e volta e isso já dispara o verificador de paridade e demora muito tempo pra completar. Imagino que força muito o disco. Eu não consigo mais deixar o servidor ligado com medo de que qualquer falta de energia cause essa verificação enorme. Existe algum nobreak na medida do possível silencioso que funcione só para evitar esse tipo de problema? Não preciso de nada de nível empresarial, só queria poder deixar meu servidor ligado sem medo de queda de energia e que tenha o mínimo de compatibilidade com o sistema de monitoramento do unraid.

Maybe try this, fixed for me.

Just upgraded to version 7.0.0 and my array does not start and I get this error message: It was working just fine before the upgrade. What could possibly be wrong? How can I fix it? diagnostics-20250110-0026.zip

Uso um Cooler Master CM 690 II Advanced Nvidia Edition. Comprei usado de um amigo aqui da minha cidade. Se garimpar bem, deve encontrar. É muito grande. Encontrar gabinete com muita baia e que não seja R$ 1.000 é complicado. Passei por isso, só raiva. Simplesmente não existe no br, é incrível. A saída é olx, marketplace da vida ver se acha um antigo em bom estado.

Parity-sync finished now with no errors. It seems like it fixed itself regarding those SATA errors. I wonder why I got the read check error in the first place that caused all this trouble? is that possible to know? UPS top 1 priority now. Can't be bothered by this again lol Meanwhile I'm setting some settings in parity check tuning: Should I enable "write corrections to parity disk"? Seems good idea?

I stopped the array, unassigned parity disk. Started the array. Stopped the array again. Assigned parity disk. Started array in maintenance mode. Start sync parity. My log is flooded with weird errors: tower-syslog-20240912-0424.zip Changed sata cables to another port on motherboard but didn't work. It starts the syncing, after a couple of seconds, same errors again and syncing starts to become slow and then stops. Is my motherboard bad because of the power outage ?

After a power blink, my system was unresponsive (UI unreachable) and I had to force shutdown pressing power button. When it got back online, parity check began but after some hours I got some warnings in discord: Parity check is now paused in 20.7% and I don't know what I have to do to gracefully restore parity errors and get everything back online. I still can't afford a UPS, unfortunately. So Murphy law applies to me a lot. Diagnostics attached. tower-diagnostics-20240911-2355.zip

I see. If I have done preclear things would be much easier for me now. For example, now I wanted to completely erase the disk. So I started a preclear with operation "Clear Disk". If I bought a new one and want to certify that it is good before adding to my array, which operation should I choose? Verify disk? Seems like a reasonable choice, lol

I'm no targeted, just for privacy. I have no clue of what the RMA may do to the hard drive to try to deny warranty for me, I don't know. SMART test is failing, and the extended one spams me with tons of warnings while it's running. "Pending sector"... So, I pretty much think its dead? Damn. I just bought it, assigned as parity drive and let it build it. Should I have done it another way? I mean, I just can't believe me eyes. The HD just died with 1 week usage lol and as a parity drive.

Extended or short ? --Edit I get a read failure when trying to do a short test.

So it became faster after a while and it just finished with this error (discord notification): Despite the error, would you say its erased?

preclear.txt Not much...