dmoney517

Members
  • Posts

    69
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dmoney517's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. 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!
  2. 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.
  3. 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!
  4. 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.
  5. I decieded to just let it rip. No issues going from 6.9.2 to 6.12.8.
  6. 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.
  7. 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.
  8. 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!
  9. 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.
  10. 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.
  11. 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
  12. Should I leave P1 in dsbl and add a new disk to P2?
  13. 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
  14. All the error counts for read error and seek error rate don't matter? I just ran to best buy and bought a new psu. Currently using the 500w that powered my old dual xeon 5650 setup. Just grabbed a 750w.
  15. Restarted server. I did not touch any cables or cards. Did not start array. Diagnostics attached. I really appreciate your help! I am in a bit of a panic right now. nas-diagnostics-20240311-1107.zip