Re: Filesystem errors on armv7 -current

On Oct 26, 2026, at 7:13 pm, bob prohaska <fbsd@www.zefox.net> wrote:

> On Mon, Oct 26, 2026 at 02:03:12PM -0400, Paul Mather wrote:
>> On Oct 25, 2026, at 9:50 pm, bob prohaska <fbsd@www.zefox.net> wrote:
>> 
>>> On Fri, Oct 23, 2026 at 06:27:43PM -0700, bob prohaska wrote:
>>>> 
>>>> The least-intrusive change I can make at this point is replace the
>>>> wallwart on the powered hub running the hard disk. That will change
>>>> only one connection, the barrel jack on the hub. Wiggling it once
>>>> raised the measured voltage on the hub by about 100 mV, so that
>>>> disturbance is already taken into account.
> 
[[...]]
> 
>> If you can attach the drive to a controller that lets you read the S.M.A.R.T. data, that could be instructive.  Values of Reallocated_Sector_Ct, Current_Pending_Sector, and Offline_Uncorrectable attributes can be illuminating in giving an idea of the overall health of the drive.  A non-zero value for Reallocated_Sector_Ct would indicate bad sectors on the drive that have been successfully reallocated.  IIRC, a non-zero value for Current_Pending_Sector would indicate an ongoing attempt to reallocate a bad sector that could point towards the drive being out of spare sectors with which to reallocate.
>> 
> 
> The drive is apparently not SMART compatible, alas.


It would be surprising if the drive is not S.M.A.R.T. compatible.  It would not be very surprising if the USB device/interface the drive is plugged into does not pass through S.M.A.R.T. reporting.  IIRC, it is fairly common for USB enclosures (especially cheaper/consumer ones) not to do this.

Assuming the drive is a SATA drive, are you able to connect it to a SATA interface?  If so, does "smartctl" yield anything?

Cheers,

Paul.