Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.ibm.pc.hardware.storage > #8605

Re: Interpreting diskscan results

From bp@www.zefox.net
Newsgroups comp.sys.ibm.pc.hardware.storage
Subject Re: Interpreting diskscan results
Date 2026-11-04 14:57 +0000
Organization A noiseless patient Spider
Message-ID <11cfh4e$oj14$1@dont-email.me> (permalink)
References <11bt43t$2gksl$1@dont-email.me> <slrn11ekgm2.2dg.jj@iridium.wf32df>

Show all headers | View raw


Jim Jackson <jj@franjam.org.uk> wrote:
> On 2026-10-28, bp@www.zefox.net <bp@www.zefox.net> wrote:
>> A Raspberry Pi 2B self-hosting FreeBSD-current developed what
>> looks like filesystem corruption. Most correspondents suggest
>> that something's wrong with the disk. The only non-destructive
>> test I could find was diskscan, a Linux program available on
>> RasPiOS, which seems to plot read access time vs number of 
>> blocks having that access time. Nothing hugely amiss is apparent,
>> but I'm no expert with diskscan. 
> 
> is smartctl or equiv. available on FreeBSD? You need to try and check 
> the S.M.A.R.T. stats that disks keep nowadays. You may need to 
> do a web search.
> 

Yes, smartmontools are available on FreeBSD. The first few attempts
reported SMART wasn't supported, but eventually a response came back.
It's at
http://www.zefox.net/~fbsd/rpi2/disktrouble/smartctl.log

A correspondent on the FreeBSD mailing lists pointed out a few
bad omens:
  1 Raw_Read_Error_Rate     0x000f   083   056   006    Pre-fail  Always       -       196488790

  5 Reallocated_Sector_Ct   0x0033   099   099   036    Pre-fail  Always       -       386

  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       27847 (91 61 0)

I instead paid attention to 

197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0

and didn't consider three years runtime excessively long.

Evidently, I was mistaken 8-) , thinking there'd be something
like "spare sectors exhausted" or some other explicit message
that the disk was EOL. 

Somewhat curiously, both diskscan and dd if=/dev/da1 of=/dev/null
seemed to indicate no explicit errors. Diskroaster, a FreeBSD port,
reported five errors.

Thanks for writing,

bob prohaska

 

Back to comp.sys.ibm.pc.hardware.storage | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Interpreting diskscan results bp@www.zefox.net - 2026-10-28 15:24 +0000
  Re: Interpreting diskscan results Jim Jackson <jj@franjam.org.uk> - 2026-11-03 20:23 +0000
    Re: Interpreting diskscan results bp@www.zefox.net - 2026-11-04 14:57 +0000
      Re: Interpreting diskscan results not@telling.you.invalid (Computer Nerd Kev) - 2026-11-13 06:49 +1000
        Re: Interpreting diskscan results bp@www.zefox.net - 2026-11-14 01:54 +0000

csiph-web