dmoney517

New update....it looks like this is occurring for me with ANY browser page left open. I like to leave my main up, but I am noticing sometimes I come back and see my logs full of this. I have also woken up to my server being off. Seems these logs are filling to the point it crashes the server. Hopefully this is resolved in a future version.

Thanks! I started up and ran a parity check just to test all the drives. Ran perfectly, and finished my parity check about 1.5 hours faster than my old HBA. So I'll take it!

I just changed my HBA from 9201-81 to 9207-8i PCIex3. Needed for various reasons. Anyway, with the old HBA, all of the drives would populate and show on the BIOS splash screen during boot. With the new HBA, they are not. Only the USB, M.2 and 4 on board SATA drives are showing. Once Unraid boots, all drives are present. Is this OK? Diags attached, and a pic of the splash screen. nas-diagnostics-20240407-1005.zip

Thanks. It finished overnight. Everything looks in order. Diags attached. My assumption is that the port on my second HBA is went bad? Both DSBL disks were on the same SFF-8087 breakout. I moved that cable to an open port on my other HBA (running 2 9201-8i, but only using 3/4 ports) when one of the disks stopped being read and it came back? I replaced one of my 2.5 SSDs with an M2 during this build (unplanned, I broke it while pulling cables), so I could technically consolidate at this point down to 1 HBA (8 drives) and the 4 on board sata ports and that would cover all my current drives. Should I do this assuming the entire HBA is bad? Or is it possible to have 1 bad port on the HBA? Also debating returning both of them (bought at the same time, still in return window until May) and getting a new HBA all together from a different seller. As always, greatly appreciate your advice and help! Last set of diagnostics attached! nas-diagnostics-20240403-0717.zip

I moved cables and the missing disk is back again, albeit in DSBL mode still (obviously). I have intitiated rebuild of both drives. Attaching diags again. Can you please take a look 1 more time to ensure everything is looking as it should? Appreciate all of your help! nas-diagnostics-20240402-1620.zip

I rebooted the server, and now Parity Disk 1 is not showing at all. Ugh. I thought I was passed all of this.

Thanks...what about the Parity? Should I rebuild both? Or rebuild disk 4 first then parity?

Here they are... nas-diagnostics-20240402-0906.zip

Cli reboot worked. New diagnostics attached. nas-diagnostics-20240402-0852.zip

It wont let me cancel when I click the button. Nothing changes on the screen. 20 minutes after I tried, this just popped up in the log. Not sure if its related. Apr 2 07:46:34 NAS nginx: 2024/04/02 07:46:34 [error] 22158#22158: *4835131 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.105, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "192.168.0.108", referrer: "http://192.168.0.108/Main"

I am not able to Cancel the current Parity Check. When I click cancel / OK, the Parity check dialogue does not go away and STOP Array is still greyed out.

Scheduled Parity kicked off laat night 10pm. My health check ran last night 12:20am, no problems. 2:10am 1 of my parity disks and a data disk went to DSBL. 3 am Scheduled Prity Check Paused so Mover could run, then resumed as it should at 3:21am when mover finished. I've been awake for 15 minutes and the parity check has not moved. Stuck at 74.7%, and claiming it is moving at 99MB/s. Any thoughts on if I need to replace? What is my best path forward to fix both disks? I do have 2 disks in unassigned devices on standby, precleared and ready. Diagnostics attached nas-diagnostics-20240402-0644.zip

Ok. Not sure what happened with /mnt/user/flash, but I was assuming whenever I connected to \\NAS\flash over SMB from my windows desktop, it was connecting to /mnt/user/flash. But I just went into /mnt/user/flash in the terminal and it is basically empty. so Unraid is sharing the /boot drive over \\NAS\flash by default I guess? Either way, Thanks for the help! I have moved that "share" to a new name and my Fix common problems is now clean. Appreciate the help!

Interesting. Glad I found this thread. I just did a server rebuild and upgraded from 6.9.2 to 6.12.8. I thought I was running smooth, then woke up to this. Looked at my phone and saw i left a tab open on Dashboard. Kind of annoying, but glad it isnt anything wrong with the server/build.

Ok...If I navigate to the /mnt/user/flash folder, it is the contents of my Flash drive. Should I do the rename procedure? Is it "safe" to rename directory since it is the Flash drive? cd /mnt/user mv flash flash-drive Thanks for the help!

I just moved from 6.9.2 to 6.12.8 and am now seeing errors related to flash drive share. However, I dont have a share named Flash. Not that I created at least - But I do see it if I go to /mnt/user - I know the guidance is to manually go to the terminal and run mv flash new-flash to rename it, but I want to confirm this before doing so as I never created this share, it was shipped this way when I initially built my server several years ago.

I decieded to just let it rip. No issues going from 6.9.2 to 6.12.8.

For awhile now I have not been able to consistently load the SabNZB GUI on my Unraid. It still starts, and downloads and works. But getting the UI to load is very inconsistent. I would say it works 1 out of 10 tries. I barely every need to look at it, so not a major hindrance. I noticed today when I tried to launch it, I got this error in my Server log - TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters. Nothing on my server is exposed to the internet. It used to work flawlessly, so I am guessing a docker update did something that I never really noticed. As I said, I dont try to access it often. Appreciate any guidance.

I would like to see this other thread as well. I am ok 6.9.2 and ready to leap to the latest, 6.12.8. I am a bit nervous.

Hmm, Ill look into that. Thanks. For now, Thank you @JorgeB! I was able to pre-clear one of my disks as well to confirm it is good. My final disk seems to be dead. SMART shows below. When i tried to pre clear it had a ton of errors in the logs and smart shows below. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 069 064 006 - 163877417 3 Spin_Up_Time PO---- 097 096 000 - 0 4 Start_Stop_Count -O--CK 084 084 020 - 16546 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 083 060 045 - 213584792 9 Power_On_Hours -O--CK 082 082 000 - 15876 (164 223 0) 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 092 092 020 - 8295 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error -O--CK 100 100 099 - 0 187 Reported_Uncorrect -O--CK 081 081 000 - 19 188 Command_Timeout -O--CK 100 100 000 - 0 0 8 189 High_Fly_Writes -O-RCK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 073 063 040 - 27 (Min/Max 20/28) 191 G-Sense_Error_Rate -O--CK 100 100 000 - 0 192 Power-Off_Retract_Count -O--CK 096 096 000 - 8234 193 Load_Cycle_Count -O--CK 089 089 000 - 23081 194 Temperature_Celsius -O---K 027 040 000 - 27 (0 17 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 082 064 000 - 163877417 197 Current_Pending_Sector -O--C- 100 100 000 - 40 198 Offline_Uncorrectable ----C- 100 100 000 - 40 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 240 Head_Flying_Hours ------ 100 253 000 - 3027h+32m+37.751s 241 Total_LBAs_Written ------ 100 253 000 - 55058677784 242 Total_LBAs_Read ------ 100 253 000 - 277759799893 ||||||_ K auto-keep Thanks everyone for helping!

This is what they should be, based on the listing. LSI Avago IT mode firmware version P20 (20.00.07.00) Is there a better firmware version? In my old setup I flashed myself. I wanted to avoid that step this time so bought pre-flashed.

Im not one to mess with BIOS a ton. So I didn't change any settings for the CPU. I had read that system was a power hog, so I assumed (incorrectly) that my PSU would be fine with the new hardware. and my UPS even said it could power my old system for 5 minutes, and the new one for 20+ minutes. It does seem to me that the new setup is using less power, but regardless here we are. I am very happy it is a PSU issue. Fairly easy, and not overly expensive fix (cheaper than getting 2 new HBAs or multiple new disks). I have since all this started plugged the new system into a power calculator, and it called for 500-599 w. So, I should have done my homework first and checked the power requirements for the new setup instead of making an assumption.

Holy moly - No errors in syslog like were coming on previous tries. Rebuild is cruising at 160 MB/s. Attached one last diags...But I am hopeful that the new PSU is fixing this problem! Note - I did see some Power On Failures in the start up when i booted the system. nas-diagnostics-20240311-1532.zip

Should I leave P1 in dsbl and add a new disk to P2?

New PSU hooked up. Re-cabled and seated everythjing again while attaching the new PSU (750w). All drives are online again. Have not started the array. Diagnostics attached. Should I reassign Parity and start the array? nas-diagnostics-20240311-1458.zip