January 15, 201214 yr I just put together my new unRaid server. Now booting takes forever with strange lines in the log and one of me disks is now red balled when it was fine before. The new system is a Supermicro Atom motherboard (X7SPA-HF-D525) and 8 gigs of RAM. I am using the onboardd SATA ports. I attached the syslog and results from smartctl for the red-balled drive. syslog.txt smart.txt
January 16, 201214 yr Author I trusted the red-balled disk and it is working fine now. I trusted it after running smart reports on the disk and it passed without any issues. I am still having the issues in my log from my other disk. I am running smart tests on it now. I've already replaced the cables to known working cables. After running a short smart report I saw: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 204 188 021 Pre-fail Always - 4791 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 315 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 172 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 152 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 30 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 755 194 Temperature_Celsius 0x0022 126 109 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 I guess the only issue reported was the 1 Current Pending Sector. I am running a long smart test now to get more info.
January 17, 201214 yr Author I ran a long test on the drive causing the syslog errors using WD's DOS tool. The drive passed without issue. After doing so, now unRaid boots without the drive issue and it booted quickly.
January 17, 201214 yr I was under the impression that these boards only supported up to 4 GB ram Is there a bios update that will increase the maximum ram? Sent from my DROID2 using Tapatalk
January 17, 201214 yr They officially support 4GB.. but 8GB does work in the D525 series quite well. it will step-down the speed of the ram (as most supermicro boards do as you increase the ram size). It is just very picky about what ram you use.
January 17, 201214 yr Author Exactly. I've seen it mentioned here and some other hardware focus forums. The QVL list was quite small. I made some inquires to other users and then found what I felt was a good deal on some RAM another owner reported as working well. Anyone have a clue what those log errors were about and how running a long test seems to have fixed it?
January 17, 201214 yr Thank you johnm, I have the X7SPA-HF-525 using v5b14 with sab/sb/cp/pms plugins downloading to an app drive (using drive mount plugin) and then moving the completed files to the shares automatically. The only issue is when streaming 720P mkv's to a Roku 2 using plex. (Roku doesn't support mkv and I think the server has to handle the transcoding to play on Roku using Plex client). Streaming to Boxee Box works great. In your opinion, would I see any better performance using 8 GB ram? I don't really care about the Roku streaming part, just wanted to know if it was a worthwhile upgrade Sent from my DROID2 using Tapatalk
January 17, 201214 yr this is a bit of a hijack of this thread.. I have not tried the 8gig upgrade on my unraid box yet.. just my 2k8 box. in fact, i sent kricker a PM earlier asking how it handled MEMtest. Kricker any input? i dont really have need to up the ram my D525 unraid box. as you see in my sig, my unraid D525 is limited to just 4 drives and 2.5" cache drive. I might even repourpose it now since i got a N40L. @ kricker, so you're saying that fixing the pending sector solved your issue?
January 17, 201214 yr Author I don't really know what happened. Does running a long test with the WD tools fix things like that? I thought it would just scan the disk and report results. Now that I got that squared away, I'll run memtest tonight.
January 17, 201214 yr Author There are probably threads that discuss RAM amounts and performance. I don't know enough personally to comment on it.
January 17, 201214 yr this is a bit of a hijack of this thread.. You are right and I should've known better. I am sorry all Sent from my DROID2 using Tapatalk
January 17, 201214 yr I don't really know what happened. Does running a long test with the WD tools fix things like that? I thought it would just scan the disk and report results. Now that I got that squared away, I'll run memtest tonight. I'd run the smart test once again and see if it changed. it is quite possible that it relocated that sector for you.
January 17, 201214 yr Author Yeah. I'll run another smart report and see what it says now. BTW, memtest is running now, so far without issue.
January 17, 201214 yr Author Multiple memtest passes later and everything is golden. The RAM appears to be solid. I ran another smart report on the drvie that previously caused the syslog errors: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 222 188 021 Pre-fail Always - 3883 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 331 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 183 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 159 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 30 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 794 194 Temperature_Celsius 0x0022 122 109 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 It appears running the long test in WDs tools fixed the pending sector and everything is looking fine again. Everything appears to be booting and running properly. Time to try a move to a version 5 beta!
Archived
This topic is now archived and is closed to further replies.