Andre Hedrick wrote:
> Yeah "smartctl" does not work, but reading the correct 48-bit logs does.
>
> All I stated was you are using the wrong tool to extract the needed
> information.
So which tool(s) do I need for getting at the 48-bit log data? If I
need a spec doc to decode a binary block of data I can deal with that.
Prefer not to, but...
I did a full surface read scan of the disk and it turned up no errors.
As for how I got the SMART data dump I enabled SMART on the drive then
dumped the data a few minutes later.
- Bryan
Bryan,
The one nobody has written in closed form as of to date.
Basically it is a DNE (does not exist).
The infrastructure is just now being laid into place now so, it will take
some time to code out the rest of the internals to allow standard UI
access.
I have my own suite of "private" tools, and they will not be released.
There are possible patent issues, and licensing problems.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Sun, 26 Jan 2003, Bryan Andersen wrote:
>
>
> Andre Hedrick wrote:
> > Yeah "smartctl" does not work, but reading the correct 48-bit logs does.
> >
> > All I stated was you are using the wrong tool to extract the needed
> > information.
>
> So which tool(s) do I need for getting at the 48-bit log data? If I
> need a spec doc to decode a binary block of data I can deal with that.
> Prefer not to, but...
>
> I did a full surface read scan of the disk and it turned up no errors.
>
> As for how I got the SMART data dump I enabled SMART on the drive then
> dumped the data a few minutes later.
>
> - Bryan
>