Re: 'smart' status on new laptop

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        that's a Seagate SATA disk.
-Brian

On Jan 24,  8:31pm, "Steven M. Bellovin" wrote:
} Subject: Re: 'smart' status on new laptop
} On Thu, 24 Jan 2008 21:25:58 +0100
} "Daniel Horecki" <shinden%linux.pl@localhost> wrote:
} 
} > On Jan 24, 2008 8:30 PM, Steven M. Bellovin <smb%cs.columbia.edu@localhost>
} > wrote:
} > >
} > > On Thu, 24 Jan 2008 19:21:22 +0100
} > > Bernd Ernesti <netbsd%lists.veego.de@localhost> wrote:
} > >
} > > > On Thu, Jan 24, 2008 at 01:50:30PM +0000, Steven M. Bellovin
} > > > wrote:
} > > > > Here's the output of 'atactl smart status' on a fairly new
} > > > > laptop. Some of the figures look suspect, such as the hours
} > > > > powered on... Might it be a word size issue?  I'm running
} > > > > -current/amd64.
} > > >
} > > > Is this a seagate drive?
} > > > Smart is know to be broken on there drives.
} > > >
} > > Truthfully, I don't know, nor do I see anything on NetBSD to tell me
} > > (I've looked at smartctl, atactl, and dmesg -- anything else?)  I
} > > haven't pulled the drive out yet to look at the physical label...
} > > The model number starts with ST; I have vague recollections that
} > > that's true for Seagate drives, but I thought Lenovo favored
} > > Hitachi disks.
} > 
} > Try smartctl -i /dev/wd0d
} > 
} 
} Per my note, I'd already tried smartctl:
} 
}       evice Model:     ST9160823AS
}       Serial Number:    5NK0CZ7N
}       Firmware Version: 3.CMC
}       User Capacity:    160,041,885,696 bytes
}       Device is:        Not in smartctl database [for details use: -P showall]
} 
} and dmesg:
} 
} wd0 at atabus0 drive 0: <ST9160823AS>
} wd0: drive supports 16-sector PIO transfers, LBA48 addressing
} wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
} wd0: 32-bit data port
} wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
} wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100)
} (using DMA)
} 
} 
}               --Steve Bellovin, http://www.cs.columbia.edu/~smb
>-- End of excerpt from "Steven M. Bellovin"