surferjsmc

Hi Jorge, in. the past same thing happened but from my laptop and I'm pretty sure it wasn't because I've double click it 😊

Hi all, Last night I shutdown the server from my mobile phone, it was by clicking on the shutdown button of the web interface and because I was next to the server I've noticed it did it right away like in two seconds which is not the usual thing. Today after starting the server again it started a parity check making me think that something went wrong with last night's shutdown. Since this is not the first time I've noticed this situation I would like to ask for your advice so I can avoid potential issues. Thanks in advance. corellia-diagnostics-20240221-1743.zip

No more temperature alerts in the last 15 hours so i'm confident to say this fix works Running Unraid 6.11.5, cache drive Samsung 980 500GB. Thank you all.

Hi Jorge, I've been facing this temperature issues since i've got a 980 for the main cache poll, my Syslinux configuration looks different from what you describe on your post, here is a screenshot of it because i'm not quite sure where to add that line, could you please take a look? By the way, after checking logs and time of the temperature warnings i found the trigger to be Flash Backup process and it always went down to 34ºC exactly 30 minutes after the warning, I was very worried because even added a thick heatsink to the drive but nothing changed. Thx!

Hi, i have a similar issue on my VM using EVGA GTX 970 SSC Today i've realized that my screen settings was on 60Hz. used to be 144Hz. but when i tried to change it there is no option aside from 60, did lots of troubleshooting: tested another DP cable = only 60Hz. switch to HDMI = only 60Hz. rebooted in baremetal = DP up to 165Hz. and HDMI 144Hz. same result with different cables. NVIDIA driver wiped with DDU installed and installed fresh. = 60Hz. Changed virtIO driver from 190 to latest 225-2 but VM crashes so revert back to ver. 190. The only changes that i recall are related to Unraid OS updates.

Updated from 6.9.2 without any issues, executed Update Assistant and informed me about Nerd pack and Config editor been not compatible so I uninstalled them before update and everything went smooth. Thanks to Lime tech and all the people involved, great work.

Hi all, Posted this on plugin thread but had no answer. After upgrading parity disk to a bigger one I added the old parity disk to the array, now with more free space I want to move files from Disk1 to Disk3 but no matter hoy much I tried unBalance isn't doing anything. I've tried scatter, select folder to be move from Disk1, then select destination Disk3, when pressed Plan permissions error or warning shows as this: Ran Fix common problems extended test and it returned this: (other directories and irrelevant info not included on the screenshot) If I continue and select move it says all files were moved but after checking destination Disk that isn't true. Tried copy instead but same result. All Dockers are stopped as well as VMs. Any hints?

Hi all. After upgrading parity disk to a bigger one I added the old parity disk to the array, now with more free space I want to move files from Disk1 to Disk3 but no matter hoy much I tried unBalance isn't doing anything. I've tried scatter, select folder to be move from Disk1, then select destination Disk3, when pressed Plan permissions error or warning shows as this: Ran Fix common problems extended test and it returned this: (other directories and irrelevant info not included on the screenshot) If I continue and select move it says all files were moved but after checking destination Disk that isn't true. Tried copy instead but same result. All Dockers are stopped as well as VMs. Any hints?

Umm that's weird, I checked Open Files plugin and killed all processes before stopping the array on the first time.

Shutdown from the UI worked, plugged the new disk and powered on the server, parity error because unclean shutdown message appeared as expected so I stopped the array and leave it on all night to give it time to stop correctly. This morning everything looked alright so I proceeded to start parity rebuild on the new drive with both Dockers and VMs turned off, After almost 10 hours (4TB Disk) finished to rebuild without errors and now I just reassigned the old parity drive to the array. To be honest there is drive on the array that is working but not 100% healthy, could be this the reason why it takes so long to stop the array and also the unclean shutdowns errors?

It's been almost two hours since tried to stop the array and it is still unmounting disk 1, should I try shutdown button from the UI or is there a command that can be run to make sure array stops correctly?

VM was stopped.

Hi ppl! I've got a new bigger drive to replace parity so I proceeded to stop all containers and VMs and then stop the array before shutdown, now is been more than half an hour and the server is trying to stop the array, checking the logs I can see is this: Feb 18 14:27:28 Corellia root: umount: /mnt/disk1: target is busy. Feb 18 14:27:28 Corellia emhttpd: shcmd (3275): exit status: 32 Feb 18 14:27:28 Corellia emhttpd: Retry unmounting disk share(s)... I don't want to force shutdown but don't know how much to wait neither. Note that my disks are pretty much full at this moment hence the party upgrade and reassign old parity disk to array. corellia-diagnostics-20220218-1427.zip

Hi! Have you checked you MB manual and how you should populate storage? in most cases internal SATA controllers are limited by the amount of NVME drives installed, for example my server's MB has 6x SATA III and 2x NVME/PCI, if i populate one NVME all of the SATA ports are available but, if two NVMEs are installed i'll have only 4x SATA ports available. Regarding your plan, it sounds good to me

Hola @EUGENI_CAT la controladora venía ya flasheada, en otro post me dijo jorgeB que no estaba en la última versión y que puedo actualizarla, de momento no lo hice porque estoy probando funcionamiento y estabilidad. Si te soy sincero tuve algunos problemas al instalarla, ella funcionaba desde el día 1 y Unraid la detectaba junto con los discos conectados pero el server me daba problemas al iniciar, no tenia webui abri post y haciendo varios troubleshootings al final determiné que era el USB, restaure un backup en otro y me funciono bien pero por unas horas, así que no me quedó más remedio que flashear otro USB y contactar a Unraid para pedir que me dieran una nueva key ya que era un segundo cambio en una semana. Ahora mismo lleva casi una semana funcionando bien, todavía no lo he convertido al servidor definitivo pero creo que de esta si va a serlo, sigo haciendo pruebas agregando algún ssd más como cache pool y con VMs.