Bizquick

Seams odd that just started to happen. I was planning on moving everything to a new case with more cooling options. I guess I'm just going to have to make it a little quicker move than I expected. I do have one other option I can do. I've also been trying to move to new hardware again so I might be able to see if the backup server is ready enough to take over.

Server is rebooting on its own I think about every 6 hours or so.

Not sure what is going on I need to some help to see if this is hardware or software. If hardware what is failing. Seams like this just started the last few days. Log attached. neonas3-diagnostics-20240326-1201.zip

Well like I said above a lot of times people will list and say anything. But you don't know for sure unless you check here is where I saw it in the log. Mar 11 11:03:50 NAS kernel: mpt2sas_cm0: LSISAS2008: FWVersion(11.00.00.00), ChipRevision(0x03), BiosVersion(07.00.00.01) I would think the firmware version would say something else. I just dont have a log file with one of these HBA cards to tell for sure. So thats why I suggested you at least check. You ont have to flash it but I would try to follow the steps like you would flash it and check the firmware version. or if the place you got it from added the BIOS to it. you could check before boot and get into the controller. Just don't try to change anything. It might be fine though so not sure. I wish I had a older log file from my older systems to see what mine said.

from your Log post it does look like your HBA controllers are on a older firmware. But If you don't have any issues you might not need to do anything. I would guess that your older setup might have had the power settings in bios set low which was why it could boot up and make all your drives usable. Now in this newer setup. Generally they set things a little more on the higher side especially after you add 1 or 2 cards plugged into the motherboard. But for me when I'm building out systems if I got more than 5 drives I usually use a 650watt min PSU. and I was seeing 7 spin drives plus the small SSD's. That with a new Intel chip with igpu. 500watts was just a little under. might 550watts would be just enough. but it was just a little on the low side to me.

Still not sure what is causing these messages. Diag is above.

500 watts PSU does seam a bit low with that many drives and HBA cards. older 4TB and lower Spin Drives do take some power when I ran 6 4TB WD reds. I made sure my PSU was 650. kind of surprised your dual Xeon box didn't have power issues. unless the CPU's just constantly ran in low power mode. Which can happen if your Bios is not set to turn off C-states and a few other things all depending on what the BIOS lets you do. glad to hear it sounds like your up and running now. I would double check your HBA Firmware to make sure its P20. Sometimes I've gotten a few of those old 9201 cards and I've had to reflash them because who ever sold them didn't do it right or just claimed they did. But your log shows that's good I don't know how to read everything in the logs yet still learning.

Here I'm currently replacing my parity drive. But other than that I just got those weird errors for the i915 and the i2c's neonas3-diagnostics-20240311-1245.zip

I'm not really a 100 percent familiar with the SyncThing Docker. But you do need to setup your docker to see all your shares or what your syncing. I think this should go into the SyncThing Docker support maybe. Its not really General Unraid OS issue.

Yeah I've removed and replaced drives a few times. If you have enough open sata ports or drive connection ports. I would just add the new 20TB to the array and use either plug-in balance to move the files from the 8TB drive to the new 20TB. or add Krusader Docker and move the files manually. Balance Plug in most likely a littler safer but might take as long as swapping one of the 8TB drive out and letting parity rebuild on the 20TB. Christopher in his above post is most likely the easiest. only reason I might not like that way is you end up doing 2 parity checks 1 is rebuilding. then the next one after you redo the array and move the files manually. 20TB parity takes you almost 1.2 days right? my 12TB is 19 hours without my HBA. with my HBA I can get it in 17hours.

I guess I've had this error in my logs for a while too. Not sure how to get rid of it. Mar 10 06:15:09 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Mar 10 06:15:36 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Mar 10 06:37:03 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Mar 10 06:47:14 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 3f Mar 10 07:30:02 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Mar 10 08:11:47 NEONAS3 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f I dont have a video card installed its just onboard iGPU. And I stopped using a dummy plug to see if this would stop generating the error. I suspect its maybe a video card driver error. Because I have Swapped motherboards a few times and CPU's. But I haven't reloaded just swapped and removed the video card plug-ins a few times and added them back. Anyway I'm almost ready to where I can swap to another server. I just need to figure out a way I can get all my dockers completely duplicated over on my new box. I tried a backup and restore but it didn't like to use appdata backup to restore to a new box. Something about wanting the same server name. I'll most likely have to figure out how I can do it a different way.

not sure what this means but I'm seeing this in my logs every now and then. Not sure what it really means I don't see any issues on my server. But just trying to figure out if this is something I can clean up or what. Mar 6 17:26:39 NEONAS3 kernel: i2c i2c-2: readbytes: ack/nak timeout Mar 6 17:26:39 NEONAS3 kernel: i2c i2c-2: readbytes: ack/nak timeout Mar 6 17:26:39 NEONAS3 kernel: i2c i2c-2: readbytes: ack/nak timeout Mar 6 17:26:39 NEONAS3 kernel: i2c i2c-2: sendbytes: error -110 Mar 6 17:26:40 NEONAS3 kernel: i2c i2c-2: sendbytes: error -110 Mar 6 17:27:26 NEONAS3 kernel: i2c i2c-2: sendbytes: error -110 Mar 6 17:27:26 NEONAS3 kernel: i2c i2c-2: sendbytes: error -110 Is this like NIC card related or something else?

One of my systems I need to upgrade the parity drive and I don't have a open sata slot. Can I just shut down and replace the parity drive and then put in the new one and assign it before array starts? If not I guess i can add one of my HBA's and do what I've see on other threads suggested. I just got some larger drives and only way I think I can use them is to swap out my smaller parity.

If you cant get that working with out display plugged in I suggest just getting a dummy plug. I had to do that for one of my builds that used IPMI and igpu. or you can hit on the motherboard maker to make some sot of BIOS adjustment that works. That would be my suggestion sense you have done most of the work and found that it works with a display plugged in. A dummy plug shouldn't cost you too much I got a 2 pack on amazon for almost 9 dollars.

Totally agree I think its the Catch 22 there. The hardware Dev's don't want to spend time on the open source because not getting paid for it. And the community is limited to what it can see to help them. I think I'm just going to wait till I upgrade again and then use this board and test the Marvel 9172 controller ports in a backup box to test with. So it might be another year I guess.