-
Unraid unresponsive at unknown times.
Ok, found the issue it seams. after a bit of pain i managed to get the output but only with screen attached since for some reason the error cant be writen to syslog. *even copy to flash This is what i found. kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x176/0x1d0 kernel: BUG: unable to handle page fault for address: ffff8805081ac63b kernel: note: lsblk[63268] This seams to be memory related, and i tested stick by stick and suddenly it became stable. *i only did memtest before so no issues there i thought. and keeps being stable now for a weeks time.
-
Unraid unresponsive at unknown times.
Hi, Thank you, for your reply, I assumed it would not be helpfull but trying to include everything. *syslog does not capture the actual error. The last snippit i managed to log (unable to capture the img, was only logged on monitor) BTRS error something Kernel panic and something akin to unrecoverable fault. So i have started the following process to try to fix the issue thank you @JorgeB Updated Unraid *becouse of the kernel panic error i saw. Bios is updated for the cpu issue, i have contacted support to make sure i will do memtest again and test 1 stick at a time if the issue persists if abuve fail. Will update. *might take some time ^_^
-
Unraid unresponsive at unknown times.
Hi, I'll try to explain. I upgraded hardware from 9+years old to almost current gen. Intel® Core™ i5-14500 @ 4554, and new motherbord, that was the best i could find for the application. I have attached diagnostics and MB info. Since then i have had several weird behaviur, fixing one after another. Now im stuck at one issue, where the unraid becomes unresponsive. Sometimes i can still access shares but dockers is always unresponsive same with direct hdmi from the server with gui running. Hoping you can shed some light on the issue, im adding from syslog at the bottom with marked timestamp. Dec 26 16:18:19 LairStorage monitor_nchan: Stop running nchan processes Dec 26 16:28:38 LairStorage nginx: 2025/12/26 16:28:38 [error] 10335#10335: *856637 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.6, server: , request: "GET /Dashboard HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard" Dec 26 16:28:39 LairStorage nginx: 2025/12/26 16:28:39 [error] 10335#10335: *859116 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.6, server: , request: "GET /plugins/unassigned.devices.preclear/assets/sweetalert2.js?_=1766762279696 HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard" Dec 26 16:28:39 LairStorage nginx: 2025/12/26 16:28:39 [error] 10335#10335: *859116 auth request unexpected status: 504 while sending to client, client: 192.168.0.6, server: , request: "GET /plugins/unassigned.devices.preclear/assets/sweetalert2.js?_=1766762279696 HTTP/1.1", host: "192.168.0.175", referrer: "http://192.168.0.175/Dashboard" Dec 26 18:00:01 LairStorage move: Starting Mover Tuning ... Dec 26 18:00:01 LairStorage move: Cron + options: start Dec 26 18:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start Dec 26 18:14:56 LairStorage php-fpm[9573]: [WARNING] [pool www] server reached max_children setting (50), consider raising it Dec 27 00:00:02 LairStorage move: Starting Mover Tuning ... Dec 27 00:00:02 LairStorage move: Cron + options: start Dec 27 00:00:02 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start Dec 27 06:00:01 LairStorage move: Starting Mover Tuning ... Dec 27 06:00:01 LairStorage move: Cron + options: start Dec 27 06:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start Dec 27 12:00:01 LairStorage move: Starting Mover Tuning ... Dec 27 12:00:01 LairStorage move: Cron + options: start Dec 27 12:00:01 LairStorage move: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start Dec 27 13:43:16 LairStorage root: ACPI action left is not defined Dec 27 13:43:17 LairStorage root: ACPI action left is not defined Dec 27 13:43:17 LairStorage root: ACPI action left is not defined Dec 27 13:43:17 LairStorage root: ACPI action left is not defined Dec 27 13:43:17 LairStorage root: ACPI action right is not defined Dec 27 13:43:18 LairStorage root: ACPI action left is not defined Dec 27 13:43:18 LairStorage root: ACPI action left is not defined Dec 27 13:43:18 LairStorage root: ACPI action right is not defined Dec 27 13:43:18 LairStorage root: ACPI action down is not defined Dec 27 13:43:19 LairStorage root: ACPI action up is not defined Dec 27 13:43:19 LairStorage root: ACPI action left is not defined Dec 27 13:49:57 LairStorage rc.rsyslogd: Syslog server daemon... Started. Dec 27 13:49:57 LairStorage root: Delaying execution of fix common problems scan for 10 minutes Dec 27 13:49:57 LairStorage unassigned.devices: Mounting 'Auto Mount' Devices... Dec 27 13:49:57 LairStorage emhttpd: Starting services... lairstorage-diagnostics-20251227-1352.zip W680-NAS-Motherboard-10G-3L12Bay-English.pdf
-
-
Changeing allocation does not work
Hi, Thank itimpi for the explanation of most free. (i thought it was based on %free) With that information, Highwater. must disk 1-5 be filled to 75% before disk 6 will be filled to 50%? Or When will disk 6 start to be filled? Any way of having equal amount saved on all disks regardless of disk size? Thank you for your patience and all of your answers.
-
Changeing allocation does not work
Why not disk 6,7,8? I'm missing something could you explain why most free is not using disk 6,7,8
-
Changeing allocation does not work
Hi, Does not write to disk 6,7,8. (When i made the share they where excluded) In global nothing is excluded and all is included in share nothing is excluded *anymore I have tried for Most-Free, high-water *high-water right now. I'm have manually moved files to Disk 6,7,8 and everything seams to be still working so there is no issue there. and on share i have Automatically split any directory as required Now its only writing to disk 1. *is this due to high-water and because its not writing to disk 6,7,8? Been searching and googling but cant seam to work it out. sorry to make another topic about this but have not found a solution *tried most free again, and its now stopped writing to disk1, and is writing on the most empty of disk 1,2,3,4,5 lairstorage-diagnostics-20240623-1233.zip
-
Disabled disk, files emulating nothing. (My fault i think)
Any thoughts to make sure i get back all data or, limit the loss as much as possible?
-
Disabled disk, files emulating nothing. (My fault i think)
New controller card arriving in 2h, is there a best way to make sure i get as much data as possible back? From my searching i have found that this might be best?? 1. new config 1.1 retain assignment 2. put disk1 with data back 2.2 put all disks in correct position 3.start array Is this the best way or have i missed something?
-
Disabled disk, files emulating nothing. (My fault i think)
Yes as a troubleshooting before we realized its a controller issue. *before i removed the disk The format did not do anything, everything is still on the disk.
-
Disabled disk, files emulating nothing. (My fault i think)
Hi, have controller issue. (new one ordered) So disk 1 got disabled. For testing i removed disk1 and put it in dock to troubleshoot I replaced the PSU, so the server got restarted with no disk in disk1, now the emulation is emulating no files. Don't know if that's a bug/feature but how do i fix. Missing around 4TB of data, the data is still on the disk. I don't want to make it worse, what should i do? (The only thing i can think of is to mount it separately and transfer the files manually with crusader but its so slow) lairstorage-diagnostics-20240617-1839.zip
-
Problems with Parity and new disk.
Now after a day of no problems and no errors, it failed again. Since i marked this as solved should i start new thread? 1. Disk 1 failed, removed and added again to test = fail 2. Former parity 8tb added to disk1 = fail 2.1 Now that i know there is no power issue, HX650 now installed. 3. Just to test i tested new cable harness = fail on both devices. 3.1 (Random sometimes disk3 disappear, when disk1 fail, this is why i tested new cable harness) 4. So my controller card is the issue? 4.1 I have already ordered LSI SAS 9300 8i (LSI 3008 chipset). *based on previous conv. lairstorage-diagnostics-20240616-1305.zip
-
Problems with Parity and new disk.
Im half way though the parity, never gotten this far while doing both drives at the same time. So must have been a power issue. Seeing performance numbers from your link, last question what would you recommend? *not sure if there is a downside should i get 2x LSI LSI00301 (9207-8i) PCI-Express 3.0 x8 or a single card LSI 9300-16i SAS-controller HBA-card, 12 Gbps 16 SATA SAS-port PCIe 3.0, PCIe 8X HBA
-
Problems with Parity and new disk.
Is there a quicker way since parity has been 100% and disk 4 100% synced. (Spare PSU being used so no disk is using power splitters) Or do i need to unassigned disk restart array and add them as replacement drives? (even if its the same drive?)
-
Problems with Parity and new disk.
https://www.startech.com/en-se/cards-adapters/8p6g-pcie-sata-card Not sure how a sff-8087 connector work, but according to site "4 2-Port SATA host controllers" I will run extension cord to get the psu and test. If its the controller, i have 10disks any tips?
-
Problems with Parity and new disk.
Hi, Not anymore and from what i can tell they should even be on different rails/ atleast not on same cable to psu. (the powersupply is old, Its a Corsair vs 450) If we think that power is a issue then i have a separate psu i can try. and only attach new parity and disk 4 to that one.
SwedeOzzie
Members
-
Joined
-
Last visited