I did not see any 4.5 forums so i posted here..

 

I am somewhat new to unraid and linux but looking at the syslogs i noticed that i have a lot of errors (see below). it is saying that it is on "ata4" does this mean that it is the 4th drive? if so and i have drives sdb, sdc, sdd and sde the problem drive will be sde?

 

Apr 13 06:21:53 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:53 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:53 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:53 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:53 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:53 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:53 NAS kernel: ata4.01: configured for UDMA/33

Apr 13 06:21:53 NAS kernel: ata4: EH complete

Apr 13 06:21:54 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:54 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:54 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:54 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:54 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:54 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:55 NAS kernel: ata4.01: configured for UDMA/33

Apr 13 06:21:55 NAS kernel: ata4: EH complete

Apr 13 06:21:56 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:56 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:56 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:56 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:56 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:56 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:56 NAS kernel: ata4.01: configured for UDMA/33

 

thanks

James

We would need to see the entire syslog to get an idea, but you can search through it yourself to find out what drive ata4 is referring to.

We would need to see the entire syslog to get an idea, but you can search through it yourself to find out what drive ata4 is referring to.

 

sorry i guess i missed the important parts 

 

so if i understand this, looking at the log the entry "sd 4:0:1:0:" refers to "ata4.01" which is device sde?

 

here is what is just after the above lines..

Apr 13 06:21:56 NAS kernel: ata4.01: configured for UDMA/33

Apr 13 06:21:56 NAS kernel: sd 4:0:1:0: [sde] Unhandled sense code

Apr 13 06:21:56 NAS kernel: sd 4:0:1:0: [sde] Result: hostbyte=0x00 driverbyte=0x08

Apr 13 06:21:56 NAS kernel: sd 4:0:1:0: [sde] Sense Key : 0x3 [current] [descriptor]

Apr 13 06:21:56 NAS kernel: Descriptor sense data with sense descriptors (in hex):

Apr 13 06:21:56 NAS kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 13 06:21:56 NAS kernel: 05 cb 86 b8

Apr 13 06:21:56 NAS kernel: sd 4:0:1:0: [sde] ASC=0x11 ASCQ=0x4

Apr 13 06:21:56 NAS kernel: sd 4:0:1:0: [sde] CDB: cdb[0]=0x28: 28 00 05 cb 86 b8 00 00 08 00

Apr 13 06:21:56 NAS kernel: end_request: I/O error, dev sde, sector 97224376

Apr 13 06:21:56 NAS kernel: Buffer I/O error on device sde, logical block 12153047

 

thanks

James

I did not see any 4.5 forums so i posted here..

 

I am somewhat new to unraid and linux but looking at the syslogs i noticed that i have a lot of errors (see below). it is saying that it is on "ata4" does this mean that it is the 4th drive? if so and i have drives sdb, sdc, sdd and sde the problem drive will be sde?

 

Apr 13 06:21:53 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:53 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:53 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:53 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:53 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:53 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:53 NAS kernel: ata4.01: configured for UDMA/33

Apr 13 06:21:53 NAS kernel: ata4: EH complete

Apr 13 06:21:54 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:54 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:54 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:54 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:54 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:54 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:55 NAS kernel: ata4.01: configured for UDMA/33

Apr 13 06:21:55 NAS kernel: ata4: EH complete

Apr 13 06:21:56 NAS kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 13 06:21:56 NAS kernel: ata4.01: failed command: READ DMA

Apr 13 06:21:56 NAS kernel: ata4.01: cmd c8/00:08:b8:86:cb/00:00:00:00:00/f5 tag 0 dma 4096 in

Apr 13 06:21:56 NAS kernel: res 51/40:00:b8:86:cb/00:00:00:00:00/f5 Emask 0x9 (media error)

Apr 13 06:21:56 NAS kernel: ata4.01: status: { DRDY ERR }

Apr 13 06:21:56 NAS kernel: ata4.01: error: { UNC }

Apr 13 06:21:56 NAS kernel: ata4.01: configured for UDMA/33

 

thanks

James

In any case, those are media errors, so you might want to get smart reports on your drives.  At least one of them will probably have some re-allocated sectors.  (If not, it could be a symptom of a bad or loose cable to a drive)

 

Joe L.

We would need to see the entire syslog to get an idea, but you can search through it yourself to find out what drive ata4 is referring to.

 

sorry i guess i missed the important parts 

 

so if i understand this, looking at the log the entry "sd 4:0:1:0:" refers to "ata4.01" which is device sde?

You figured it out...

Joe L. thanks...

 

I have another question.. my drives finished pre-clearing last night and i was using unmenu and installed the mail notification package and set it up to mail when there was an error. this morning i looked at the syslog from unmenu and below is all i found, why is it pretty much empty?. also does anyone know why the system is going out to mail.google.com?

 

Apr 14 04:40:01 NAS syslogd 1.4.1: restart.
Apr 14 04:47:03 NAS sSMTP[32322]: Creating SSL connection to host
Apr 14 04:47:03 NAS sSMTP[32322]: SSL connection using RC4-MD5
Apr 14 04:47:04 NAS sSMTP[32322]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 21sm69266ywh.17)
Apr 14 05:47:02 NAS sSMTP[32440]: Creating SSL connection to host
Apr 14 05:47:02 NAS sSMTP[32440]: SSL connection using RC4-MD5
Apr 14 05:47:03 NAS sSMTP[32440]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 6sm83378ywd.53)
Apr 14 06:47:02 NAS sSMTP[32558]: Creating SSL connection to host
Apr 14 06:47:03 NAS sSMTP[32558]: SSL connection using RC4-MD5
Apr 14 06:47:04 NAS sSMTP[32558]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 ha13sm65963ibb.3)
Apr 14 07:18:10 NAS unmenu[1282]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory
Apr 14 07:18:56 NAS unmenu[1282]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory
Apr 14 07:23:27 NAS unmenu[1282]: ls: cannot access /boot/custom/etc/rc.d/*: No such file or directory

 

 

thanks

James

 

Joe L. thanks...

 

I have another question.. my drives finished pre-clearing last night and i was using unmenu and installed the mail notification package and set it up to mail when there was an error. this morning i looked at the syslog from unmenu and below is all i found, why is it pretty much empty?.

The syslog is moved to syslog.1 at 4:40 in the morning if it has grown over a certain size.  Your prior syslog contents should be found there.

also does anyone know why the system is going out to mail.google.com?

 

Apr 14 04:40:01 NAS syslogd 1.4.1: restart.
Apr 14 04:47:03 NAS sSMTP[32322]: Creating SSL connection to host
Apr 14 04:47:03 NAS sSMTP[32322]: SSL connection using RC4-MD5
Apr 14 04:47:04 NAS sSMTP[32322]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 21sm69266ywh.17)
Apr 14 05:47:02 NAS sSMTP[32440]: Creating SSL connection to host
Apr 14 05:47:02 NAS sSMTP[32440]: SSL connection using RC4-MD5
Apr 14 05:47:03 NAS sSMTP[32440]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 6sm83378ywd.53)
Apr 14 06:47:02 NAS sSMTP[32558]: Creating SSL connection to host
Apr 14 06:47:03 NAS sSMTP[32558]: SSL connection using RC4-MD5
Apr 14 06:47:04 NAS sSMTP[32558]: Authorization failed (535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 ha13sm65963ibb.

Actually, it did not successfully connect.  You need to configure it for your mail host and supply a proper login/password if required

After changing a config option the button on unMENU then changes to "Re-Install" with new values.  You probably did not press it.

 

No problem, just edit the config values, save without changing, and the Re-Install" button will then appear.