Mike Scott <usenet.16@scottsonline.org.uk.invalid> writes:My bad - I meant 'badblocks'.Richard Kettlewell wrote:Never heard of baddisk, what is that?Mike Scott <usenet.16@scottsonline.org.uk.invalid> writes:>Hi all. I always seem to get impossible problems....>
>
Take a pi4 and two disks - both sata connected by a sata to usb
adapter. One is a small real disk drive, the other a Kingston
SSD. Both have been in the spares cupboard for a while.
>
I put an old arm64 version of bookworm onto the spinner. Works fine.
>
I put the exact same onto the ssd. Won't boot, with messages like
timed out waiting for udev to be empty
or
read error on /dev/sda [details not recorded]
Boot the Pi from the spinning disk (or an SD card) and connect the
SSD to the Pi. See if you can access it and if not, have a look at
the kernel log.
Already did - I ran one full pass with baddisk -w which completed with
zero errors.
Anyway from what you’ve said, Linux on the Pi can’t see the SSD duringYes.
early boot, but can see it when attached to the Pi later. That’s hard to
explain, since it’s the same hardware and the same code looking for it
in each case.
Just to check, did you run your ‘full pass with baddisk’ _on the Pi_, as
requested above?
The problem does look as though it was down to a combo of the ssd plus one particular sata/usb adapter (I have 3). Using dd, I found transfer rates down to <10MB with the ssd and that particular adapter.
The issue does seem to centre around the combo of ssd, that particular adapter, and the pi4. I get decent transfer rates using my desktop with all the adapters; just the pi4 has issues with that one, fine with the other 2.
Anyway, I have a system that has now booted several times without issue, which is great.
Thanks to all for commenting.
--
Mike Scott
Harlow, England
Les messages affichés proviennent d'usenet.