October 10, 201015 yr I just build my first UnRaid and noticed the following entries in the Syslog while performing preclear on 3 disks: Oct 9 21:47:55 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x3f SErr 0x0 action 0x6 frozen Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:00:d8:4e:7b/02:00:5a:00:00/40 tag 0 ncq 262144 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:08:08:69:7a/02:00:14:00:00/40 tag 1 ncq 262144 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:10:88:41:fc/02:00:39:00:00/40 tag 2 ncq 262144 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:18:d8:ca:2d/01:00:4d:00:00/40 tag 3 ncq 131072 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:20:d8:c9:2d/01:00:4d:00:00/40 tag 4 ncq 131072 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/20:28:00:00:00/00:00:00:00:00/40 tag 5 ncq 16384 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 21:47:55 Beanstalk kernel: ata20: hard resetting link Oct 9 21:47:57 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Oct 9 21:47:57 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 9 21:47:57 Beanstalk kernel: ata20.00: device reported invalid CHS sector 0 Oct 9 21:47:57 Beanstalk last message repeated 4 times Oct 9 21:47:57 Beanstalk kernel: ata20: EH complete Oct 9 21:56:19 Beanstalk unmenu[3219]: sh: bwm-ng: command not found Oct 9 22:07:16 Beanstalk unmenu[3219]: which: no bwm-ng in (/usr/local/sbin:/usr/sbin:/sbin:./:/usr/local/bin:/usr/bin:/bin) Oct 9 22:12:51 Beanstalk unmenu[3219]: Disk /dev/sda doesn't contain a valid partition table Oct 9 22:12:53 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 9 22:12:53 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 22:12:53 Beanstalk kernel: ata20.00: cmd 60/00:00:98:e1:0b/01:00:58:00:00/40 tag 0 ncq 131072 in Oct 9 22:12:53 Beanstalk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 22:12:53 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 22:12:53 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 22:12:53 Beanstalk kernel: ata20.00: cmd 60/00:08:98:e0:0b/01:00:58:00:00/40 tag 1 ncq 131072 in Oct 9 22:12:53 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 22:12:53 Beanstalk kernel: ata20.00: status: { DRDY } Oct 9 22:12:53 Beanstalk kernel: ata20: hard resetting link Oct 9 22:12:56 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Oct 9 22:12:56 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 9 22:12:56 Beanstalk kernel: ata20.00: device reported invalid CHS sector 0 Oct 9 22:12:56 Beanstalk kernel: ata20: EH complete Some of the lines are red in UnMenu SysLog view. Is this serious? I have not configured any drives in the array yet since I plan on running preclear first while waiting for the Pro license. Attached is the more of the syslog. syslog-2010-10-10.txt
October 10, 201015 yr Oct 9 21:47:55 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x3f SErr 0x0 action 0x6 frozen Oct 9 21:47:55 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 9 21:47:55 Beanstalk kernel: ata20.00: cmd 60/00:00:d8:4e:7b/02:00:5a:00:00/40 tag 0 ncq 262144 in Oct 9 21:47:55 Beanstalk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 9 21:47:55 Beanstalk kernel: ata20.00: status: { DRDY } If you are using AHCI mode, try to disable NCQ, if not then switch back to IDE mode and give it another try
October 11, 201015 yr The syslog viewer in unMENU simply matches patterns of text on lines and applies colors if they match. The syntax looked for is from when the syslog viewer was originally written by RobJ. The red lines are those matching these patterns: any_case ||"error"||red match_case||"Emask "||red match_case||"arity incorrect"||red match_case||"Fsck?"||red match_case||"invalid opcode: "||red match_case||"nobody cared"||red match_case||"Unknown boot option"||red match_case||" ata[0-9\. ]+: disabled"||red match_case||" DMA disabled"||red match_case||"kernel BUG "||red match_case||"Write Protect is on"||red Any line with the word "error" on it in any case will be colored "red", even those that might say "No Error Found" (simply because the line has the word error in it somewhere.) You can find all the syslog match rules in a file named syslog_match.conf in the unmenu directory on your server. You need to use Google to learn the real meaning of any errors you might see. Many are harmless, others more serious. Joe L.
October 12, 201015 yr Author I have not configured my array yet, still trying to get the unRAID server to run with any SATA errors. However, I am getting these errors. Is there a way to identify the drive that is causing it (there are 15). Oct 11 23:18:42 Beanstalk ntfs-3g[5980]: Global ownership and permissions enforced, configuration type 1 Oct 11 23:18:49 Beanstalk kernel: ata16.00: exception Emask 0x10 SAct 0x0 SErr 0x1400000 action 0x6 frozen Oct 11 23:18:49 Beanstalk kernel: ata16.00: edma_err_cause=00000020 pp_flags=00000000, SError=01400000 Oct 11 23:18:49 Beanstalk kernel: ata16: SError: { Handshk TrStaTrns } Oct 11 23:18:49 Beanstalk kernel: ata16.00: failed command: IDENTIFY DEVICE Oct 11 23:18:49 Beanstalk kernel: ata16.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in Oct 11 23:18:49 Beanstalk kernel: res 58/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x12 (ATA bus error) Oct 11 23:18:49 Beanstalk kernel: ata16.00: status: { DRDY DRQ } Oct 11 23:18:49 Beanstalk kernel: ata16: hard resetting link Oct 11 23:18:49 Beanstalk kernel: ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 23:18:50 Beanstalk kernel: ata16.00: configured for UDMA/133 Oct 11 23:18:50 Beanstalk kernel: ata16: EH complete Oct 11 23:19:38 Beanstalk kernel: ata16.00: exception Emask 0x0 SAct 0x3 SErr 0x400000 action 0x6 frozen Oct 11 23:19:38 Beanstalk kernel: ata16: SError: { Handshk } Oct 11 23:19:38 Beanstalk kernel: ata16.00: failed command: READ FPDMA QUEUED Oct 11 23:19:38 Beanstalk kernel: ata16.00: cmd 60/c0:00:60:00:00/01:00:00:00:00/40 tag 0 ncq 229376 in Oct 11 23:19:38 Beanstalk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 11 23:19:38 Beanstalk kernel: ata16.00: status: { DRDY } Oct 11 23:19:38 Beanstalk kernel: ata16.00: failed command: READ FPDMA QUEUED Oct 11 23:19:38 Beanstalk kernel: ata16.00: cmd 60/20:08:3f:00:00/00:00:00:00:00/40 tag 1 ncq 16384 in Oct 11 23:19:38 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 11 23:19:38 Beanstalk kernel: ata16.00: status: { DRDY } Oct 11 23:19:38 Beanstalk kernel: ata16: hard resetting link Oct 11 23:19:39 Beanstalk kernel: ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 23:19:39 Beanstalk kernel: ata16.00: configured for UDMA/133 Oct 11 23:19:39 Beanstalk kernel: ata16.00: device reported invalid CHS sector 0 Oct 11 23:19:39 Beanstalk kernel: ata16: EH complete Oct 11 23:20:09 Beanstalk kernel: ata16: limiting SATA link speed to 1.5 Gbps Oct 11 23:20:09 Beanstalk kernel: ata16.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 11 23:20:09 Beanstalk kernel: ata16.00: failed command: READ FPDMA QUEUED Oct 11 23:20:09 Beanstalk kernel: ata16.00: cmd 60/08:00:bf:6c:70/00:00:74:00:00/40 tag 0 ncq 4096 in Oct 11 23:20:09 Beanstalk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 11 23:20:09 Beanstalk kernel: ata16.00: status: { DRDY } Oct 11 23:20:09 Beanstalk kernel: ata16.00: failed command: READ FPDMA QUEUED Oct 11 23:20:09 Beanstalk kernel: ata16.00: cmd 60/c0:08:60:00:00/01:00:00:00:00/40 tag 1 ncq 229376 in Oct 11 23:20:09 Beanstalk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 11 23:20:09 Beanstalk kernel: ata16.00: status: { DRDY } Oct 11 23:20:09 Beanstalk kernel: ata16: hard resetting link Oct 11 23:20:10 Beanstalk kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 11 23:20:10 Beanstalk kernel: ata16.00: configured for UDMA/133 Oct 11 23:20:10 Beanstalk kernel: ata16.00: device repo Attached is the full syslog. syslog-2010-10-11.txt
October 12, 201015 yr Oct 11 22:59:23 Beanstalk kernel: ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 22:59:23 Beanstalk kernel: ata16.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133 Oct 11 22:59:23 Beanstalk kernel: ata16.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) Oct 11 22:59:23 Beanstalk kernel: ata16.00: configured for UDMA/133 Oct 11 22:59:23 Beanstalk kernel: scsi 15:0:0:0: Direct-Access ATA WDC WD10EADS-00L 01.0 PQ: 0 ANSI: 5 Oct 11 22:59:23 Beanstalk kernel: sd 15:0:0:0: [sdk] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Oct 11 22:59:23 Beanstalk kernel: sd 15:0:0:0: [sdk] Write Protect is off Oct 11 22:59:23 Beanstalk kernel: sd 15:0:0:0: [sdk] Mode Sense: 00 3a 00 00 Oct 11 22:59:23 Beanstalk kernel: sd 15:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 11 22:59:23 Beanstalk kernel: sdk: sdk1 Oct 11 22:59:23 Beanstalk emhttp: Device inventory: Oct 11 22:59:23 Beanstalk emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host21 (sdl) Hitachi_HDS722020ALA330_JK1170YAH410GP Oct 11 22:59:23 Beanstalk emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host22 (sdm) ST3320620AS_3QF0GZS0 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:00:1f.2-scsi-2:0:0:0 host23 (sdn) SAMSUNG_HD103SJ_S2AEJ1BZ508267 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:00:1f.2-scsi-3:0:0:0 host24 (sdo) WDC_WD15EARS-00Z5B1_WD-WMAVU1419886 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:02:01.0-scsi-0:0:0:0 host0 (sda) WDC_WD20EARS-00S8B1_WD-WCAVY2844247 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:02:01.0-scsi-1:0:0:0 host1 (sdb) SAMSUNG_HD203WI_S1UYJ1LZ306377 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:02:01.0-scsi-2:0:0:0 host2 (sdc) ST32000542AS_9XW05K3T Oct 11 22:59:23 Beanstalk emhttp: pci-0000:02:01.0-scsi-3:0:0:0 host3 (sdd) SAMSUNG_HD203WI_S1UYJ1CZ313622 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:02:01.0-scsi-7:0:0:0 host7 (sde) WDC_WD20EARS-00S8B1_WD-WCAVY2976312 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:03:01.0-scsi-0:0:0:0 host8 (sdf) WDC_WD20EARS-00S8B1_WD-WCAVY1874389 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:03:01.0-scsi-1:0:0:0 host9 (sdg) SAMSUNG_HD203WI_S1UYJ1CZ313616 Oct 11 22:59:23 Beanstalk emhttp: pci-0000:03:01.0-scsi-2:0:0:0 host10 (sdi) ST32000542AS_9XW057XK Oct 11 22:59:23 Beanstalk emhttp: pci-0000:03:01.0-scsi-3:0:0:0 host11 (sdj) Hitachi_HDS722020ALA330_JK1130YAGZRSXT Oct 11 22:59:23 Beanstalk emhttp: pci-0000:03:01.0-scsi-7:0:0:0 host15 (sdk) WDC_WD10EADS-00L5B1_WD-WCAU47901134
October 12, 201015 yr Author Thank you GK20. My first time building a computer and working in a non-Windows environment is quite overwhelming. I was ready to pull everything and boot one drive at a time. So do these error messages usually point a particular component like cable, SATA backplane, disk, or controller?
October 12, 201015 yr Author Also my BIOS has a setting for Serial ATA Native Mode Operation. The two values are Serial ATA and Auto. The default is Auto. Select Serial ATA to use the SATA mode' date=' or select Auto to use the Native Mode for ATA[/quote'] I googled SATA Native Mode and from my understanding, I should select Auto to take advantage of advanced SATA features. Am I correct?
October 12, 201015 yr No, you want to use 'Serial SATA'. This is equivalent to AHCI, which is what you want. Native Mode will make your SATA drive run at IDE speeds, which you don't want.
October 12, 201015 yr Author No, you want to use 'Serial SATA'. This is equivalent to AHCI, which is what you want. Native Mode will make your SATA drive run at IDE speeds, which you don't want. The BIOS also has a separate setting for SATA ACHI which is Enabled or Disabled. I have this set to Enabled. So this is why I am confused by the two settings. According to this Microsoft link, native mode should be used. So did SuperMicro redefined Native Mode?
October 12, 201015 yr Look at how many SATA ports are listed in the BIOS when you switch modes. One mode might only show 4 disks the other 6 or however many your MB has.
October 12, 201015 yr [ According to this Microsoft link, native mode should be used. Win XP does not have any SATA drivers... They did not exist in the marketplace when it was originally written. So... using the "native" mode on the BIOS makes the SATA drive controller emulate an older IDE drive, which does have drivers in Win XP. The option in the BIOS is to allow older Mictosoft products think they are operating with the IDE drive they were originally designed for... (and prevents use of the newer features of the SATA drives) If there was no IDE emulation (native) mode, a Win-XP box would not be able to boot from an SATA drive. Now do you see why Microsoft suggests "native" (IDE emulation) mode? Without it their OS would not be able to use the drive as a boot device. Joe L.
October 12, 201015 yr Author Thanks again Joe. I am setting it to Serial ATA and move on with my build! I spent the whole morning troubleshooting thinking I have a bad SAS backplane. Turned out one of the SFF-8087 reverse breakout cable is defected. I was having drives dropping in and out between boots.
Archived
This topic is now archived and is closed to further replies.