Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Tejun: thanks for the CC. I'm clueless about what is at fault here. Eamonn: could you please build the latest version of smartmontools from CVS HEAD source and see if the problem exists in that version? Then write back. I don't think this will help but want to eliminate obvious things. Cheers, Bruce On Thu, 13 Sep 2007, Tejun Heo wrote: Eamonn Hamilton wrote: Thanks for that, I checked the disks and sure enough they were in an extended self test, I aborted that and it's all back to normal. the only problem, however, is that the system is already running version 5.37 of the smartmontools package, which is the most recent as I understand it? I don't really want to leave the system with it's disks unmonitored, is there anything I can be doing to prevent this behaviour? Hmmm... That gotta be a different issue then. Cc'ing Bruce and quoting the original report. Eamonn Hamilton wrote: Hi, I'm looking ta a Dell SC440 system for a friend, and it's giving HSM violations at startup. The system itself has an ICH7 chipset, with two seagate ST3160812AS drives attached along with a single ST3400832AS, running kernel 2.6.22 and the ata_piix driver. I'm guessing this isn't good :( Anybody gt any suggestions? The violations are : ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
OK, On Fri, 2007-09-14 at 08:56 -0500, Bruce Allen wrote: ... Eamonn: could you please build the latest version of smartmontools from CVS HEAD source and see if the problem exists in that version? Then write back. I don't think this will help but want to eliminate obvious things. I built the latest version which reports itself as 5.38 from cvs. The results, as you suspected, were no different. The setup : The system is setup with sda and sdb being partitioned as follows : /dev/sda1 * 1 243 1951866 fd Linux raid autodetect /dev/sda2 2441459 9767520 fd Linux raid autodetect /dev/sda314601824 2931862+ fd Linux raid autodetect /dev/sda41825 19452 1415969105 Extended /dev/sda51825729543945776 fd Linux raid autodetect /dev/sda67296 1945297651071 fd Linux raid autodetect raid1 mirrors are then setup between the corresponding partitions on the two disks. The results : using either 5.37 or 5.38, issuing a smartctl -t long on either one of the disk devices allows filesystem access at full speed, and issuing a smartctl -X on the disk returns inside a second. All is well: time dd if=/dev/zero of=file bs=1k count=1024 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.00488519 seconds, 215 MB/s Starting an extended self-test on *both* disks, however, and filesystem access is *extremely* slow, which may be why the violations are happening, although I didn't leave it running long enough to impact the box: time dd if=/dev/zero of=file bs=1k count=1024 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.00505913 seconds, 207 MB/s real0m9.107s user0m0.000s sys 0m0.004s Now, I'm asking the guy who runs the system as to when I can test the smartd, but I'm guessing from this that the results will be exactly the same. Comments? Cheers, Eamonn -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Eamonn Hamilton wrote: Thanks for that, I checked the disks and sure enough they were in an extended self test, I aborted that and it's all back to normal. the only problem, however, is that the system is already running version 5.37 of the smartmontools package, which is the most recent as I understand it? I don't really want to leave the system with it's disks unmonitored, is there anything I can be doing to prevent this behaviour? Hmmm... That gotta be a different issue then. Cc'ing Bruce and quoting the original report. Eamonn Hamilton wrote: Hi, I'm looking ta a Dell SC440 system for a friend, and it's giving HSM violations at startup. The system itself has an ICH7 chipset, with two seagate ST3160812AS drives attached along with a single ST3400832AS, running kernel 2.6.22 and the ata_piix driver. I'm guessing this isn't good :( Anybody gt any suggestions? The violations are : ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Hi Tejun, Please disable or upgrade smartd. Thanks for that, I checked the disks and sure enough they were in an extended self test, I aborted that and it's all back to normal. the only problem, however, is that the system is already running version 5.37 of the smartmontools package, which is the most recent as I understand it? I don't really want to leave the system with it's disks unmonitored, is there anything I can be doing to prevent this behaviour? Cheers, Eamonn -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Eamonn Hamilton wrote: Hi, I'm looking ta a Dell SC440 system for a friend, and it's giving HSM violations at startup. The system itself has an ICH7 chipset, with two seagate ST3160812AS drives attached along with a single ST3400832AS, running kernel 2.6.22 and the ata_piix driver. I'm guessing this isn't good :( Anybody gt any suggestions? The violations are : ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Please disable or upgrade smartd. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
HSM violation on bootup, ICH7 + ata_piix 2.6.22
Hi, I'm looking ta a Dell SC440 system for a friend, and it's giving HSM violations at startup. The system itself has an ICH7 chipset, with two seagate ST3160812AS drives attached along with a single ST3400832AS, running kernel 2.6.22 and the ata_piix driver. I'm guessing this isn't good :( Anybody gt any suggestions? The violations are : ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) ata1: soft resetting port ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 ata1: EH complete Cheers, Eamonn -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
