On 9/5/26 12:03, Warner Losh wrote:
On Sun, Aug 23, 2026, 10:37 AM Ian FREISLICH <[email protected] <mailto:[email protected]>> wrote:On 8/23/26 10:55, Christos Margiolis wrote: > On Sun Aug 23, 2026 at 12:05 AM EEST, Ian FREISLICH wrote: >> Hi >> >> I have a USB connected hard drive which powers down when idle. Recently >> (in the last 2 weeks or so) shutdown appears to have stopped waiting for >> the drive to spin up in order to cleanly unmount. I can perform a git >> bisect but the system is relatively slow so if anyone has a change in >> mind that might be the culprit, I can start around that point. >> >> Ian > > Which driver is it using? Anything showing up in dmesg? [router] ~ # usbconfig -d ugen0.2 show_ifdrv ugen0.2: <External SATA Hard Drive Adapter cable PA023U3 Other World Computing> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (224mA) ugen0.2.0: umass0: <ULT-Best Best USB Device, class 0/0, rev 3.00/41.01, addr 1> I started getting these after a kernel built on July 28, but only during the cron.daily job: Jul 31 03:06:53 router kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 43 22 1e 28 00 00 40 00 Jul 31 03:06:53 router kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 03:06:53 router kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 03:06:53 router kernel: (da0:umass-sim0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,1 (Data phase CRC error detected) Jul 31 03:06:53 router kernel: (da0:umass-sim0:0:0:0): Retrying command (per sense data) Jul 31 03:07:01 router kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 43 22 1e 28 00 00 40 00 Jul 31 03:07:01 router kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error Jul 31 03:07:01 router kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition Jul 31 03:07:01 router kernel: (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:4,1 (Logical unit is in process of becoming ready) Jul 31 03:07:01 router kernel: (da0:umass-sim0:0:0:0): Polling device for readinessSo what's the problem here? The drive wasn't ready, we retried without an error is what this log shows me.
This was the only error I could find in /var/log/messages relating to this drive.
The problem is that shutdown doesn't appear to reliably unmount the filesystem cleanly and further during boot, the system continues to multiuser mode despite the mount failure* and the filesystem being specified in /etc/fstab.
*although I'm not sure it even attempts to mount because there's no log or console message regarding mount failure, unclean filesystem etc.
Ian
