January 30, 201115 yr Ok, perhaps I'm being a bit paranoid but I wanted to confirm that I could force a CC35 firmware upgrade on a new, unformatted Seagate ST32000542AS 2TB drive using a Gigabyte MB (it's a UD3P so no option to disable HPA that I know of) without worrying about an HPA partition being added? On a similar note, I noticed these lines in my syslog and I'm trying to figure out which drive currently has HPA on it (the Hitachi?): Jan 29 20:11:44 Tower kernel: sas: DONE DISCOVERY on port 0, pid:900, result:0 (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Write Protect is off (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related) Jan 29 20:11:44 Tower kernel: sdb: unknown partition table (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Attached SCSI disk (Drive related) Jan 29 20:11:44 Tower kernel: pata_marvell 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 (Drive related) Jan 29 20:11:44 Tower kernel: pata_marvell 0000:02:00.0: setting latency timer to 64 (Drive related) Jan 29 20:11:44 Tower kernel: scsi2 : pata_marvell (Drive related)Jan 29 20:11:44 Tower kernel: scsi3 : pata_marvell (Drive related) Jan 29 20:11:44 Tower kernel: ata2: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 16 (Drive related) Jan 29 20:11:44 Tower kernel: ata3: PATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 16 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: ATA-8: ST320005XXXX, CC35, max UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 20:11:44 Tower kernel: ata3.01: HPA detected: current 1953523055, native 1953525168 (Minor Issues) Jan 29 20:11:44 Tower kernel: ata3.01: ATA-8: Hitachi HDT721010SLA360, ST6OA31B, max UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.01: 1953523055 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: configured for UDMA/133 (Drive related)Jan 29 20:11:44 Tower kernel: ata3.01: configured for UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: scsi 3:0:0:0: Direct-Access ATA ST320005XXXX CC35 PQ: 0 ANSI: 5 (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 (Drive related)
January 30, 201115 yr Ok, perhaps I'm being a bit paranoid but I wanted to confirm that I could force a CC35 firmware upgrade on a new, unformatted Seagate ST32000542AS 2TB drive using a Gigabyte MB (it's a UD3P so no option to disable HPA that I know of) without worrying about an HPA partition being added? On a similar note, I noticed these lines in my syslog and I'm trying to figure out which drive currently has HPA on it (the Hitachi?): Jan 29 20:11:44 Tower kernel: sas: DONE DISCOVERY on port 0, pid:900, result:0 (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Write Protect is off (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related) Jan 29 20:11:44 Tower kernel: sdb: unknown partition table (Drive related) Jan 29 20:11:44 Tower kernel: sd 0:0:0:0: [sdb] Attached SCSI disk (Drive related) Jan 29 20:11:44 Tower kernel: pata_marvell 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 (Drive related) Jan 29 20:11:44 Tower kernel: pata_marvell 0000:02:00.0: setting latency timer to 64 (Drive related) Jan 29 20:11:44 Tower kernel: scsi2 : pata_marvell (Drive related)Jan 29 20:11:44 Tower kernel: scsi3 : pata_marvell (Drive related) Jan 29 20:11:44 Tower kernel: ata2: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 16 (Drive related) Jan 29 20:11:44 Tower kernel: ata3: PATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 16 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: ATA-8: ST320005XXXX, CC35, max UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 20:11:44 Tower kernel: ata3.01: HPA detected: current 1953523055, native 1953525168 (Minor Issues) Jan 29 20:11:44 Tower kernel: ata3.01: ATA-8: Hitachi HDT721010SLA360, ST6OA31B, max UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.01: 1953523055 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 20:11:44 Tower kernel: ata3.00: configured for UDMA/133 (Drive related)Jan 29 20:11:44 Tower kernel: ata3.01: configured for UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: scsi 3:0:0:0: Direct-Access ATA ST320005XXXX CC35 PQ: 0 ANSI: 5 (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off (Drive related) Jan 29 20:11:44 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 (Drive related) The Hitachi Drive: Jan 29 20:11:44 Tower kernel: ata3.01: HPA detected: current 1953523055, native 1953525168 (Minor Issues) Jan 29 20:11:44 Tower kernel: ata3.01: ATA-8: Hitachi HDT721010SLA360, ST6OA31B, max UDMA/133 (Drive related) Jan 29 20:11:44 Tower kernel: ata3.01: 1953523055 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related)
January 30, 201115 yr Author Thanks for the quick response Joe. I went ahead and forced the firmware update and myMain is reporting the following disk sizes: Should I be concerned or will the size of the RAW disk decrease when I pre-clear it?
January 30, 201115 yr Author Thanks for the reply Brit but I think you missed the point of my last post. I don't have HPA on any of the 2TB Seagate drives already in the array just the 1TB Hitachi. However, I noticed the size of my newest 2TB drive is slightly larger than all of the other drives so I'm wondering if that's an issue for parity or is it just because the drive is RAW unformatted? All of the 2TB Seagates are the ST32000542AS model.
January 30, 201115 yr Author Thanks again Joe! One last thing, since the 1TB Hitachi drive with HPA is currently blank, do I still reconstruct it after I use HDPARM to remove HPA?
January 30, 201115 yr Thanks again Joe! One last thing, since the 1TB Hitachi drive with HPA is currently blank, do I still reconstruct it after I use HDPARM to remove HPA? What do you mean by "blank" 1. Fresh from factory, never written 2. Pre-cleared and not assigned to array 3. Assigned to the array but not formatted 4. Assigned to the array and formatted, but no files written to it. Did I miss one?
January 30, 201115 yr That would be #4...sorry! It is not blank. It has been formatted. Yes, it needs to be re-constructed.
Archived
This topic is now archived and is closed to further replies.