threiner

Interesting info. does the open GUI degrade the Performace of UNRAID even on such a powefull system?????

Ich habe seid ca. zwei Wochen probleme mit Unraid es treten plötzlich schreibfehler und lesefehler auf und platten werden deaktiviert. Ich habe SAS kontroller mit den SAS zo SATA Kabeln. die habe ich für die Platten die die Fehler betreffen bereits ausgetauscht. Auch habe ich den SAS Kontroller ausgetauscht. das 1 :5 Molex zu SATA netzkabel habe ich auch schon ausgetauscht. Leider gibt es immer noch diese undefinierbaren Fehler. So langsam habe ich keine Idee mehr was das sein kann und es raubt mir den letzten Nerv. Ich habe jetzt noch ein neues hochwertiges Netzteil bestellt. Vieleicht hat ja jemand eine Idee woran das liegen könnte. Das System ist auch sehr gut gekühlt ist eine Fractal Meshy XL mit 120er Lüftern normal erreicht keine Platte mehr als 36 Grad. Vielen Dank schon mal im voraus!

I needed to replace my USB stick, so i followed the instructions, and put the backup on the new USB Stick, now i get this message from UNRAID, and i dont see the option replacing the key.

After nearly two hear attacks, all sas sata cabels exchanged two controllers testetd i found it it was most likley the Powercable adapter from one to five... looks like it works now stable

after changing the cable i get this... Sep 21 20:18:09 Tower root: Error response from daemon: Pool overlaps with other one on this address space Sep 21 20:18:09 Tower kernel: mdcmd (36): check Sep 21 20:18:09 Tower kernel: md: recovery thread: recon Q ... Sep 21 20:18:13 Tower kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Sep 21 20:18:19 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=4s Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00 Sep 21 20:18:23 Tower kernel: I/O error, dev sdo, sector 15628052992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Sep 21 20:18:28 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:29 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:43 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:52 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:53 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:57 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:02 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:03 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:07 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:12 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:21 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:22 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:31 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:32 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:36 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:36 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:41 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:46 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:46 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) so do i assume it right the drive seems to have problems??

The smart test looks good to me, so i guess i should then try to use a other cable first tower-smart-20230921-2007.zip

I have played in my testsystem with melanox cards and a cheap SFP+ / 2,5 GHZ switch fromAmazon in my testsetup it worked fine the card is called IBM Mellanox ConnectX-2 VPI 10GBE HCA Card 81Y1533 bought them from this seller https://amzn.to/3LBz2fJ and i used this switch VIMIN 6 Port 2.5G Unmanaged Network Switch, 4X 2.5Gbase-T Ports, 2X 10G SFP, 60Gbps Ethernet Switching Capacity https://amzn.to/3ZoxxqZ it was easy recogniced in WIN 11 and also in Unraid

I go this message in my log, but cant figure out what SAS controller the drive is attached to and what drive it is, can someone point me in the right direction? Sep 21 18:59:04 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:04 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:32 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:33 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:43 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:44 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred tower-diagnostics-20230921-1855.zip EDIT: I forgot to say this started when i replaced the disabled Second parity drive now i have paused the rebuild as i think is nt healthy for the dirve to restart every few seconds

thanks, but the servers stops while booting and is not booting, how do i remove the plugin?

My servier dirves me mad today... now i get this message while trying to boot after replacing a disabled harddrive with a new one. mv: can not stat usr/bin/mover : NO SUCH FILE OR DIRECTORY how do i solve this...

Thanks for the explaination, so how would i do this then? I would prefer to loose some data insted of all.

thanks, so when the systems thinks th edrive should be disabled then i cant overwrite this and have to rebuild it even when it is perfectly fine??? THis puts stress on all drives. Is there not the option to aktivate the drive? For example in the case of to disabled dirves with one parity to rebuild i need to be aböe to activate the drive if it is fine to be be able to rebuild the array.

I can not find how to put a disk from disabeled back to online without rebuilding it. I dont want to rebuild the drif i just like to change the state to online again.

worked thanks, now i have the next problem how do i enable a drive again what was disabeld by unraid?

i was going to replace the drive unraid disabeld, but unraid is not showing anymore the details like serialnumber of the drive. How do i find out the serial of the drive ?

i was going to replace the drive unraid disabeld, but unraid is not showing anymore the details like serilnumber of the drive. How do i find out the serial of the drive ?

ok but ther should be a way to take one drive out of the array or also not???

Hi , guess it is somewhere explained but i cant find it... how do i replace a failed drive with an empty one what is already in side the array?

For me the best thing on UNRAD is by far that when the system fails or hardrives, all data is on the drive and there is no problem to access them. I had Drobos for a long time till one broke and had no other chance to get on my data as searching a used device and put my drives inside there... it was a nightmare

thanks for the explication, how shoud i deal with this then? I have now rebuild one datadrive, but one parity is still disabeled, how can i solve this? thanks

I had restarted the server before i made the diagnostics, The proble came up when i restared after the update. I saw there was CRC errors so i also switched from mainboard sata ports to a second SAS controller. hope this fixes the problem. What i dont understand is, why the system disabeld working hard discs.

nobody replayed here, so i started rebuilding0,0

This Update is a proper nightmare, now i just restated the server and it hangs on starting the SAMBA for 10 minutes. How do i downgrade back to a working version? I need my data and dont want to play beta tester

tower-diagnostics-20221109-2158.zipmaybe this helps solve the problem

after update to Version: 6.11.3 Unraid disable two drives I have no clue why and can not find the reason...