Date: Sat, 21 Nov 2020 22:28:05 +0100 From: Polytropon <freebsd@edvax.de> To: Ralf Mardorf <ralf-mardorf@riseup.net> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: usb harddisk not working Message-ID: <20201121222805.e9780bba.freebsd@edvax.de> In-Reply-To: <20201121215420.3f14f459@archlinux> References: <b677a42e-a351-7fd5-24e8-770b251d6ba5@arcor.de> <20201121204425.86d9c6b1.freebsd@edvax.de> <20201121214216.2c46a95a@archlinux> <20201121215420.3f14f459@archlinux>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 21 Nov 2020 21:54:20 +0100, Ralf Mardorf wrote: > On Sat, 21 Nov 2020 21:42:16 +0100, Ralf Mardorf wrote: > >On Sat, 21 Nov 2020 20:44:25 +0100, Polytropon wrote: > >>So when in doubt, manually run fsck on the device. > > > >I "only" need to run fsck for an external drive's hfs+ partition used > >to share data between an iPad and a Linux PC. Without running fsck I > >get IO errors as if the drive is broken. I never made this experience > >with other file systems or when using hfs+ with just one operating > >system. > > Oops, > > I didn't finish the mail. What I want to point out is, that if the ufs > partition is used with FreeBSD and no other operating system, but > unclean, then probably something similar to a power loss happened, > probably something caused by the USB controller's firmware. Exactly according to my own experience: I once had a USB disk enclosure with disk that would randomly disconnect, which is not good for a mounted UFS filesystem and caused said unclean dismounting, resulting in the inability for a new automatic re-mount. The disk itself was not the reason, it worked fine after extraction, and installation in a different enclosure. Other than firmware issues, device power (voltage drop due to insufficient current supply) could be a problem. This _might_ involve faulty cables, but is not limited to that; it could be cheap USB ports (one power controller for all, so overall drawn current is added from all connected devices) on the system board. The use of fsck sould only be needed if there was an accidental unclean dismount, preventing automatic re-mount. The system log will contain the relevant information. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201121222805.e9780bba.freebsd>