Disk weirdness

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
Jul 17 14:33:36 ffoilpi1 kernel: [79525.937557] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683705 (offset
0 size 8192 starting block 166760304)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.939007] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.939051] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.939079] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.939108] sd 1:0:0:0: [sdb] CDB:
opcode=0x28 28 00 4c c0 08 08 00 00 08 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.956440] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.956486] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.956513] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.956542] sd 1:0:0:0: [sdb] CDB:
opcode=0x28 28 00 4f c0 08 00 00 00 08 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975711] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975761] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975789] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975817] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7c 58 00 00 d8 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975870] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683706 (offset
0 size 12288 starting block 166760334)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.975988] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683707 (offset
0 size 8192 starting block 166760336)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976067] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683708 (offset
0 size 16384 starting block 166760340)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976162] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683709 (offset
0 size 8192 starting block 166760342)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976200] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683711 (offset
0 size 12288 starting block 166760345)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976241] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683724 (offset
0 size 4096 starting block 166760346)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976279] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683712 (offset
0 size 8192 starting block 166760348)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976316] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683713 (offset
0 size 8192 starting block 166760350)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.976353] EXT4-fs warning (device
sdb1): ext4_end_bio:332: I/O error -5 writing to inode 41683714 (offset
0 size 8192 starting block 166760352)
Jul 17 14:33:36 ffoilpi1 kernel: [79525.978324] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.978368] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.978432] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.978467] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7d 30 00 00 28 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.983726] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.983779] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.983804] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.983833] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7d 58 00 00 d8 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.988628] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.988680] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.988705] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.988734] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7e 30 00 00 c0 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.992751] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.992807] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.992833] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.992861] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7e f0 00 00 a0 00
Jul 17 14:33:36 ffoilpi1 kernel: [79525.997471] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79525.997521] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79525.997546] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79525.997575] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 7f 90 00 00 b0 00
Jul 17 14:33:36 ffoilpi1 kernel: [79526.003355] sd 1:0:0:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 17 14:33:36 ffoilpi1 kernel: [79526.003456] sd 1:0:0:0: [sdb] Sense
Key : 0x2 [current]
Jul 17 14:33:36 ffoilpi1 kernel: [79526.003489] sd 1:0:0:0: [sdb]
ASC=0x3a ASCQ=0x0
Jul 17 14:33:36 ffoilpi1 kernel: [79526.003525] sd 1:0:0:0: [sdb] CDB:
opcode=0x2a 2a 00 4f 84 80 40 00 00 f0 00
and later when trying to remount :
Jul 17 14:51:32 ffoilpi1 kernel: [80601.579571] usb 1-1.2: new high-speed USB
device number 11 using dwc_otg
Jul 17 14:51:32 ffoilpi1 kernel: [80601.722233] usb 1-1.2: New USB device
found, idVendor=174c, idProduct=1153
Jul 17 14:51:32 ffoilpi1 kernel: [80601.722275] usb 1-1.2: New USB device
strings: Mfr=2, Product=3, SerialNumber=1
Jul 17 14:51:32 ffoilpi1 kernel: [80601.722298] usb 1-1.2: Product: AS2115
Jul 17 14:51:32 ffoilpi1 kernel: [80601.722316] usb 1-1.2: Manufacturer:
ASMedia
Jul 17 14:51:32 ffoilpi1 kernel: [80601.722334] usb 1-1.2: SerialNumber:
00000000000000000000
Jul 17 14:51:32 ffoilpi1 kernel: [80601.733269] usb-storage 1-1.2:1.0: USB Mass
Storage device detected
Jul 17 14:51:32 ffoilpi1 kernel: [80601.737779] scsi host5: usb-storage
1-1.2:1.0
Jul 17 14:51:33 ffoilpi1 kernel: [80602.730921] scsi 5:0:0:0: Direct-Access
ASMT 2115 0 PQ: 0 ANSI: 6
Jul 17 14:51:33 ffoilpi1 kernel: [80602.737024] sd 5:0:0:0: Attached scsi
generic sg1 type 0
Jul 17 14:51:33 ffoilpi1 kernel: [80602.738539] sd 5:0:0:0: [sdb] Spinning up
disk...
Jul 17 14:51:36 ffoilpi1 kernel: [80603.739558] ...ready
Jul 17 14:51:36 ffoilpi1 kernel: [80605.760942] sd 5:0:0:0: [sdb] 1953525168
512-byte logical blocks: (1.00 TB/932 GiB)
Jul 17 14:51:36 ffoilpi1 kernel: [80605.761829] sd 5:0:0:0: [sdb] Write Protect
is off
Jul 17 14:51:36 ffoilpi1 kernel: [80605.762849] sd 5:0:0:0: [sdb] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Jul 17 14:51:36 ffoilpi1 kernel: [80605.773417] sdb: sdb1
Jul 17 14:51:36 ffoilpi1 kernel: [80605.778197] sd 5:0:0:0: [sdb] Attached SCSI
disk
Jul 17 14:52:42 ffoilpi1 kernel: [80671.935409] EXT4-fs (sdb1): recovery
complete
Jul 17 14:52:42 ffoilpi1 kernel: [80671.935511] EXT4-fs (sdb1): mounted
filesystem with ordered data mode. Opts: (null)
Jul 17 14:52:50 ffoilpi1 kernel: [80679.691859] usb 1-1.2: USB disconnect,
device number 11
Jul 17 14:52:50 ffoilpi1 kernel: [80679.702064] sd 5:0:0:0: [sdb] Synchronizing
SCSI cache
Jul 17 14:52:50 ffoilpi1 kernel: [80679.702399] sd 5:0:0:0: [sdb] Synchronize
Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Jul 17 14:53:59 ffoilpi1 kernel: [80748.540252] usb 1-1.2: new high-speed USB
device number 12 using dwc_otg
Jul 17 14:53:59 ffoilpi1 kernel: [80748.682866] usb 1-1.2: New USB device
found, idVendor=174c, idProduct=1153
Jul 17 14:53:59 ffoilpi1 kernel: [80748.682914] usb 1-1.2: New USB device
strings: Mfr=2, Product=3, SerialNumber=1
Jul 17 14:53:59 ffoilpi1 kernel: [80748.682934] usb 1-1.2: Product: AS2115
Jul 17 14:53:59 ffoilpi1 kernel: [80748.682954] usb 1-1.2: Manufacturer:
ASMedia
Jul 17 14:53:59 ffoilpi1 kernel: [80748.682971] usb 1-1.2: SerialNumber:
00000000000000000000
Jul 17 14:53:59 ffoilpi1 kernel: [80748.692859] usb-storage 1-1.2:1.0: USB Mass
Storage device detected
Jul 17 14:53:59 ffoilpi1 kernel: [80748.698511] scsi host6: usb-storage
1-1.2:1.0
Jul 17 14:54:00 ffoilpi1 kernel: [80749.691474] scsi 6:0:0:0: Direct-Access
ASMT 2115 0 PQ: 0 ANSI: 6
Jul 17 14:54:00 ffoilpi1 kernel: [80749.698196] sd 6:0:0:0: [sdb] Spinning up
disk...
Jul 17 14:54:00 ffoilpi1 kernel: [80749.701856] sd 6:0:0:0: Attached scsi
generic sg1 type 0
Jul 17 14:54:02 ffoilpi1 kernel: [80750.700268] .
Jul 17 14:54:03 ffoilpi1 kernel: [80752.720217] .ready
Jul 17 14:54:03 ffoilpi1 kernel: [80752.721631] sd 6:0:0:0: [sdb] 1953525168
512-byte logical blocks: (1.00 TB/932 GiB)
Jul 17 14:54:03 ffoilpi1 kernel: [80752.722572] sd 6:0:0:0: [sdb] Write Protect
is off
Jul 17 14:54:03 ffoilpi1 kernel: [80752.723506] sd 6:0:0:0: [sdb] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Jul 17 14:54:03 ffoilpi1 kernel: [80752.734373] sdb: sdb1
Jul 17 14:54:03 ffoilpi1 kernel: [80752.738920] sd 6:0:0:0: [sdb] Attached SCSI
disk
Jul 17 14:54:54 ffoilpi1 kernel: [80804.218369] EXT4-fs (sdb1): recovery
complete
Jul 17 14:54:54 ffoilpi1 kernel: [80804.218429] EXT4-fs (sdb1): mounted
filesystem with ordered data mode. Opts: (null)
Jul 17 14:55:02 ffoilpi1 kernel: [80811.549925] usb 1-1.2: USB disconnect,
device number 12
Jul 17 14:55:02 ffoilpi1 kernel: [80811.557555] sd 6:0:0:0: [sdb] Synchronizing
SCSI cache
Jul 17 14:55:02 ffoilpi1 kernel: [80811.560278] sd 6:0:0:0: [sdb] Synchronize
Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
Loading thread data ...
What are the chances it's a fake with only 1/2 or 1/4 of the stated capacity?
Reply to
Andy Burns
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?)
formatting link
is a starting point for interpreting these messages.
--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell
In message , Andy Burns writes
Thanks.
Possible, but in that case I would have expected it to give me some form of message saying that it was full, rather than all manner of errors.
The SSD is a Samsung which was supplied by Amazon, so I think the chance of it being a fake are small. Faulty perhaps.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
In message , Richard Kettlewell writes
Powered from the PI over USB. The Pi is a 2B using a Pi 2.5A power supply. The HDD has its own power supply, and apart from a keyboard and mouse, the only other item connected to the PI is a DHT22 (thermometer)
Thanks. On the off chance that I'm reading that correctly, the initial error is "Medium not present", with no hints as to the later failure to mount etc.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
Power would be my guess, yes. I had this same trouble a lot at some point, almost making me ditch the whole ecosystem. This was with a 2.5" hdd. The adapter seemed good, 5.1 V and 2.5 A tested. Maybe it didn't handle peaks well. Annoyingly in a way, problems went away completely when I switched to the official adapter which has the same specs.
Reply to
A. Dumas
Adrian,
Reprogramming the SSD's internal controller to work with a (supposedly) larger capacity storage is a lot simpler than modifying it so it /reports/ more, but still stops at the origional size.
Also, the error might make you think the device is faulty somehow, not giving you much to go on (and you trying to figure out what went wrong - giving the counterfeiters time to sell more of the same before they have to jump ship).
By the way: The error might simply be caused by the device "wrapping around" its storage memory and trashing its sectors at the begin of the drive.
Knowing that Amazon delivers stuff from all over the world I would consider that a /bigger/, not a smaller chance. Whats the chance that the origin was not Samsung at all ?
Have you already tried to contact Samsung, providing them with the drives model, make and number ?
Regards, Rudy Wieser
Reply to
R.Wieser
I had a brand (Kingston) SSD go after a year.
--
"When one man dies it's a tragedy. When thousands die it's statistics." 

Josef Stalin
Reply to
The Natural Philosopher
In message , The Natural Philosopher writes
This was on day one !
It could be that it is a genuine almost dead on arrival.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
In message , R.Wieser writes
Given that it was supplied by Amazon, rather than a reseller, I would hope (naively ?) that it is the genuine article.
Not yet, a job for tomorrow I think.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
I don't suppose they gracefully report being full when the data overflows the free space
Reply to
Andy Burns
.
Looks like the drive has dropped out due to lack of power. SSD's are normally fine to self power from the Raspberry Pi, as long as you have a
decent spec'd power supply, and don't have any other high power USB devices, or hats.
---druck
Reply to
druck
In message , Andy Burns writes
As memory serves, it was getting to ~4% capacity.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
Try it on another computer.
Reply to
ray carter
In that case (taking into account that it works with your Ubuntu box) my guess is that the Pi is not delivering enough power to the SSD.
That _is_ the hint. You can?t mount a disk without being able to communicate with it.
--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell
That wouldn?t give USB/SCSI-level errors.
--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell
In message , Richard Kettlewell writes
Strange that it works initially, but stops after a while. The power issue was something I was thinking about earlier, and I'll try it via a powered USB hub, that might help.
But that was appearing when it had been mounted, but it had gone from being read/write to read only, and then vanished altogether. The power issue would explain why ls -l /dev/sd* showed the SSD missing. But how does that explain why the mount point is being rmdir'd.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
In message , Adrian writes
Having spoken to Samsung, it seems that the disk is not compatible with a Pi. When asked if they had one that was, they were unable to answer.
For reference, it was a Samsung MZ-76E1T0B/EU 1 TB 860 EVO Sata III 64L V
Thanks for the various suggestions. Now back to the drawing board.
Adrian
--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian
That's utter rubbish. A disk does not need to be "compatible" with anything except its defined and standardised interface, in this case presumably SATA. It's the same with websites not "supporting" certain browsers. All a site needs to do is offer valid and standards-compliant code -- few do.
So in your case one of the two is broken and has not implemented the interface correctly. I'd like to know, which is it, the Pi or the Samsung? If it should be the Pi, then the fact that many other disks are error-tolerant and work regardless is neither here not there. A broken interface is broken and needs mending, regardless of how well it seems to work under most circumstances.
--




/ \  Mail | -- No unannounced, large, binary attachments, please! --
Reply to
Axel Berger
LOL!
years ago trying to install; Interactive Unix on a 386 PC It got so far and hung with no error message.
I phoned up the UK importers and got a nice asian gentlemen who informed me that 'sorry, the bios, she is incompatible'.
I wasnt sto sure so I phoned Interactive in the USA, and after a bit of blah got on to a supprt chap. 'where is it hanging, Ah, ok, its looking for a maths coprocessor there, have you got one? 'Nope'. Is it jumpered out on the Motherboard? 'I dont know' 'well jumper it out and it should install'
'Are you sure that what is going on?' 'Yep. I wrote the installer'
It installed. I had similar experiences with Cisco., with parts of Sun and with other companiues that are smaller and now forgotten. Getting through to the guy who wrote the ciode...was always guaranteed to get te right answerr.
YOUR answer means, translated from taiwanese or whatever 'I cant be bothered with a complicated support issue so if I tell you its incompatible you will bugger off, right?'
'The BIOS, she is incompatible' became a standing joke around both my company and the PC supplier's. "WE dont jumper out the lack of coprocessor because Windows ignores it anyway"
--
No Apple devices were knowingly used in the preparation of this post.
Reply to
The Natural Philosopher

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.