Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

joelones

Members
  • Joined

  • Last visited

Everything posted by joelones

  1. This errors keep on repeating. The syslog is 30MBs! The drive is 6.0Gbs but the board is 3.0Gbs, I doubt that could be the problem. Could it be the backplane in the Norco? There are at least 4 indicators of bad communications to the drive - degraded SATA link speed ("SATA link up 1.5 Gbps"), degraded UDMA speed ("configured for UDMA/33"), SATA error flag ("Handshk"), and drive error flag ("ICRC"). This is most likely caused by a bad SATA cable, but could also be bad power to the drive. Replace the cable ASAP, with a known good SATA cable, and test again. Just a note, what is usually most helpful from the syslog is either all of it in a zipped file, or at least the section that includes the very first occurrences of the error. The 6gbps vs 3gbps SATA speed difference should not be a problem. Your response is much appreciated. I have changed the sata cable and will begin the preclear process again, unfortunately it's only at step 2 of the preclear process that the errors appear, so I will have to wait and see. I have attached the syslog which details the first occurrence of the error. Many thanks. syslog_1.zip
  2. Hi All, I am in need of some desperate help. This is a new build with only one disk and I am getting errors in the syslog Drive: ST2000DL003 Case: NORCO RPC-4020 MB: supermicro x8sil-f The drive is connected to a sata port on the motherboard and I am using the supplied sata cable that came with the motherboard: Syslog: This errors keep on repeating. The syslog is 30MBs! The drive is 6.0Gbs but the board is 3.0Gbs, I doubt that could be the problem. Could it be the backplane in the Norco? I did however try preclearing a 1.5 seagate (ST1500DL003) in the same port (it's a 6Gbs too), same types of messages. It appears that the preclear has froze at the following point: Please help. Thanks
  3. Hey Joe L., not sure what to make of this output seems like others experienced similar results with EARS in previous posts. Hopefully nothing too bad, thought I'd post the results anyway. First drive I preclear with these results with the same controller. Added jumper on pins 7 & 8 before preclear. The drive is a brand new WD15EARS. Thanks in advance. Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: ============================================================================ Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Disk /dev/sdh has been successfully precleared Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Ran 1 preclear-disk cycle Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Using :Read block size = 8225280 Bytes Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Last Cycle's Pre Read Time : 5:45:46 (72 MB/s) Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Last Cycle's Zeroing time : 7:09:59 (58 MB/s) Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Last Cycle's Post Read Time : 13:00:29 (32 MB/s) Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Last Cycle's Total Time : 25:57:21 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Total Elapsed Time 25:57:21 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Disk Start Temperature: 26C Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Current Disk Temperature: 29C, Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: == Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: ============================================================================ Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: S.M.A.R.T. error count differences detected after pre-clear Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: note, some 'raw' values may change, but not be an indication of a problem Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: 19,20c19,20 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < Offline data collection status: (0x80)^IOffline data collection activity Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < ^I^I^I^I^Iwas never started. Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: --- Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > Offline data collection status: (0x84)^IOffline data collection activity Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: 54c54 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: --- Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: 58c58 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: --- Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 1 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: 63c63 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 7 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: --- Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: 67c67 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: --- Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]: ============================================================================ Nov 26 17:32:27 Clara-Belle preclear_disk-diff[30942]:
  4. unRAID version 4.5.8 seems to have support for my mobo's chip it87. issuing modprobe it87, now gives: FATAL: Error inserting it87 (/lib/modules/2.6.32.9-unRAID/kernel/drivers/hwmon/it87.ko): Device or resource busy I did some searching and apparently the fix is by passing a kernel parameter like so: - insert GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax" As unRAID does not use grub, I guess I can pass this kernel parameter in the syslinux.cfg but is it safe to add? default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot acpi_enforce_resources=lax label Memtest86+ kernel memtest Edit: seems like that worked it8712-isa-0290 Adapter: ISA adapter VCore 1: +1.31 V (min = +0.00 V, max = +4.08 V) VCore 2: +1.20 V (min = +1.28 V, max = +1.68 V) ALARM +3.3V: +3.34 V (min = +2.78 V, max = +3.78 V) +5V: +4.84 V (min = +4.49 V, max = +5.48 V) +12V: +12.10 V (min = +9.98 V, max = +13.95 V) -12V: -15.95 V (min = -22.94 V, max = -17.05 V) ALARM -5V: -2.28 V (min = -9.14 V, max = -7.75 V) ALARM Stdby: +4.87 V (min = +4.49 V, max = +5.48 V) VBat: +3.10 V fan1: 1318 RPM (min = 811 RPM, div = fan2: 1095 RPM (min = 811 RPM, div = fan3: 3924 RPM (min = 811 RPM, div = M/B Temp: +39.0 C (low = +127.0 C, high = +73.0 C) sensor = thermal diode CPU Temp: +47.0 C (low = +127.0 C, high = +73.0 C) sensor = thermistor Temp3: +48.0 C (low = +127.0 C, high = +73.0 C) sensor = thermistor cpu0_vid: +1.350 V
  5. Trying to determine whether my chip supports pwm. The chip in question is ITE IT8712F and my motherboard has 5 fan inputs. Here is some output: sensors-detect Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8712F Super IO Sensors' Success! (address 0x290, driver `it87') Probing for Super-I/O at 0x4e/0x4f ... #----cut here---- # Chip drivers # Warning: the required module it87 is not currently installed # on your system. For status of 2.6 kernel ports check # http://www.lm-sensors.org/wiki/Devices. If driver is built # into the kernel, or unavailable, comment out the following line. modprobe it87 dmesg | grep it87 it87: Found IT8712F chip at 0x290, revision 7 it87: in3 is VCC (+5V) it87: in7 is VCCH (+5V Stand-By) ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296] modprobe it87 FATAL: Module it87 not found. So the module isn't built, perhaps directly in the kernel. pwmconfig /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed edit: found this post, modules are not present in 4.5.6 http://lime-technology.com/forum/index.php?topic=7746.0

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.