Adrian  writes:
> I'm having some fun and games with a new SSD connected to a Pi via
> USB. This has happened two days running, I've tried re-partitioning
> and re-formating the disk, but to no avail.
>
> I've got the disc partitioned and formatted (ext4), and then I mount
> it. So far so good.  After about 4 hours of copying data to it from an
> existing HDD (which it is intended to replace), I get a series of
> messages informing me that the disc is read only.
>
> e2fsck informs me :
>
> e2fsck: No such file or directory while trying to open /dev/sdb1
> possible non-existent device?
>
> I've also seen it suggest :
>
> Attempt to read block from filesystem resulted in short read whilst
> trying to open /dev/sdb1
> could this be a zero-length partition?
>
> If I connect the disc to my Ubuntu box, all seems well, it mounts and
> I can read/write to it.
>
> On top of this, when I try to remount it, mount -a doesn't give any
> errors, but the mount disappears almost immediately, as does the mount
> point (/media/extdisc2)
>
> From /var/log/messages :
>
> Jul 17 14:33:35 ffoilpi1 kernel: [79524.954860] usb 1-1.2: reset
> high-speed USB device number 7 using dwc_otg
> Jul 17 14:33:36 ffoilpi1 kernel: [79525.937346] sd 1:0:0:0: [sdb]
> UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
> Jul 17 14:33:36 ffoilpi1 kernel: [79525.937389] sd 1:0:0:0: [sdb]
> Sense Key : 0x2 [current]
> Jul 17 14:33:36 ffoilpi1 kernel: [79525.937469] sd 1:0:0:0: [sdb]
> ASC=0x3a ASCQ=0x0
> Jul 17 14:33:36 ffoilpi1 kernel: [79525.937500] sd 1:0:0:0: [sdb] CDB:
> opcode=0x2a 2a 00 4f 84 7b 70 00 00 10 00

There is a fault with either the disk, or its connectivity, or its
power. (Is it powered over the USB connection to the host or is it
separately powered?)

https://www.suse.com/support/kb/doc/?id=7006510 is a starting point for
interpreting these messages.

--
https://www.greenend.org.uk/rjk/

--- SoupGate-Win32 v1.05