February 6, 20179 yr I have experienced several disk errors in the last months and am therefore keeping a very close eye to my syslog. I am especially looking for any sata errors which might point in the direction of an issue with my supermicro sata cards. I know notice something very peculiar. It looks I get sata errors in my log every time after the Fix Common Problems plugin becomes active... See below: Feb 5 06:52:10 Tower root: Fix Common Problems Version 2017.01.28 Feb 5 06:52:10 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 06:52:10 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 06:52:10 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 06:52:10 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 06:52:10 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 06:52:10 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 06:52:10 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 06:52:10 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 06:52:14 Tower root: Fix Common Problems: Warning: inotify-tools set to install ** Ignored Feb 5 07:39:59 Tower root: Fix Common Problems Version 2017.02.03b Feb 5 07:39:59 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 07:39:59 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 07:39:59 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 07:39:59 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 07:39:59 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 07:39:59 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 07:39:59 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 07:39:59 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 07:40:05 Tower root: Fix Common Problems: Warning: inotify-tools set to install ** Ignored Feb 5 07:41:28 Tower root: Fix Common Problems Version 2017.02.03b Feb 5 07:41:28 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 07:41:28 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 07:41:28 Tower kernel: sas: ata11: end_device-1:4: cmd error handler Feb 5 07:41:28 Tower kernel: ata11.00: request sense failed stat 50 emask 0 Feb 5 07:41:28 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 07:41:28 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 07:41:28 Tower kernel: sas: ata7: end_device-1:0: cmd error handler Feb 5 07:41:28 Tower kernel: ata7.00: request sense failed stat 50 emask 0 Feb 5 07:41:33 Tower root: Fix Common Problems: Warning: inotify-tools set to install ** Ignored Isn't that weird ? I cannot imagine how or what the both would have something to do with each other..
February 6, 20179 yr Nothing to do with FCP, except that FCP attempts a write to every drive spun up drive (and will spin up spun down drives if you set the option). There is something going on with 2 drives in the system (controller, cabling, etc)
February 6, 20179 yr ATA7 and ATA11.. Are those disks 7 and 11 ? No. From Main you can click on the little disk icon next to each disk and it'll bring up the log for the drive and you can figure out which ATA # each drive relates to.
February 6, 20179 yr Author I did not know that, thanks... ! However... The specific ATA7 / ATA11 I cannot find in the text: Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 4096-byte physical blocks Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write Protect is off Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Mode Sense: 00 3a 00 00 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 06:50:48 Tower kernel: sdh: sdh1 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Attached SCSI disk Feb 5 06:50:48 Tower kernel: BTRFS: device fsid 0fa92bc7-6f6a-401b-bfcc-6de8a5ff26d3 devid 1 transid 16262 /dev/sdh1 Feb 5 06:51:05 Tower emhttp: WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 (sdh) 5860522532 Feb 5 06:51:05 Tower kernel: mdcmd (: import 7 sdh 5860522532 0 WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 Feb 5 06:51:05 Tower kernel: md: import disk7: (sdh) WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 size: 5860522532 Feb 5 06:51:06 Tower emhttp: shcmd (24): /usr/local/sbin/set_ncq sdh 1 &> /dev/null Feb 5 06:51:06 Tower emhttp: shcmd (25): echo 128 > /sys/block/sdh/queue/nr_requests
February 6, 20179 yr I did not know that, thanks... ! However... The specific ATA7 / ATA11 I cannot find in the text: Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 4096-byte physical blocks Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write Protect is off Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Mode Sense: 00 3a 00 00 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 06:50:48 Tower kernel: sdh: sdh1 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Attached SCSI disk Feb 5 06:50:48 Tower kernel: BTRFS: device fsid 0fa92bc7-6f6a-401b-bfcc-6de8a5ff26d3 devid 1 transid 16262 /dev/sdh1 Feb 5 06:51:05 Tower emhttp: WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 (sdh) 5860522532 Feb 5 06:51:05 Tower kernel: mdcmd (: import 7 sdh 5860522532 0 WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 Feb 5 06:51:05 Tower kernel: md: import disk7: (sdh) WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 size: 5860522532 Feb 5 06:51:06 Tower emhttp: shcmd (24): /usr/local/sbin/set_ncq sdh 1 &> /dev/null Feb 5 06:51:06 Tower emhttp: shcmd (25): echo 128 > /sys/block/sdh/queue/nr_requests My system it did (at least last time I needed to look at it) You can go through the syslog and it'll definitely be there when its discovering the drives near the top EDIT: It might not show it in the log if you've already reset the server... Not sure and at work...
February 6, 20179 yr Community Expert I did not know that, thanks... ! However... The specific ATA7 / ATA11 I cannot find in the text: Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] 4096-byte physical blocks Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write Protect is off Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Mode Sense: 00 3a 00 00 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 06:50:48 Tower kernel: sdh: sdh1 Feb 5 06:50:48 Tower kernel: sd 1:0:2:0: [sdh] Attached SCSI disk Feb 5 06:50:48 Tower kernel: BTRFS: device fsid 0fa92bc7-6f6a-401b-bfcc-6de8a5ff26d3 devid 1 transid 16262 /dev/sdh1 Feb 5 06:51:05 Tower emhttp: WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 (sdh) 5860522532 Feb 5 06:51:05 Tower kernel: mdcmd (: import 7 sdh 5860522532 0 WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 Feb 5 06:51:05 Tower kernel: md: import disk7: (sdh) WDC_WD60EFRX-68MYMN1_WD-WXM1H840FLU7 size: 5860522532 Feb 5 06:51:06 Tower emhttp: shcmd (24): /usr/local/sbin/set_ncq sdh 1 &> /dev/null Feb 5 06:51:06 Tower emhttp: shcmd (25): echo 128 > /sys/block/sdh/queue/nr_requests Is that the complete snippet from clicking on disk7? Note that disk7 will probably not be ata7 but it should be some ata#.
February 6, 20179 yr Author This is the complete text... I see no indication of an ATA? anywhere.. I do see SDH and DISK7 ..
February 6, 20179 yr Community Expert As Squid said, you should be able to figure it out from syslog during drive discovery. Search syslog for ata7 and you will eventually see it associated with a drive serial number, then search later for that serial number and you should see it associated with a drive number.
February 6, 20179 yr Author Found it... ATA7 is my second parity disk. ATA11 is my primairy parity disk
Archived
This topic is now archived and is closed to further replies.