Hello,
currently I have three pi's booting from an usb-stick. Today I updated the Arch on two of this pi's and I get the following boot error.
$this->bbcode_second_pass_code('', 'device descriptor read/64 error -110')
At first I thought, as with many others, according to Google, it was somehow due to the power supply or the slot of the USB stick.
When I was at a loss I thought about updating the second pi and restarting it. There I have now also the same problem.
Now I have the power supply and the slot no longer in suspicion but the USB stick. There I had fdisk output the information of the USB stick and executed an fsck.
$this->bbcode_second_pass_code('', 'Festplatte /dev/sdc: 29,42 GiB, 31583109120 Bytes, 61685760 Sektoren
Festplattenmodell: Transcend 32GB
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x0fab0e4e
Gerät Boot Anfang Ende Sektoren Größe Kn Typ
/dev/sdc1 * 2048 204799 202752 99M c W95 FAT32 (LBA)
/dev/sdc2 204800 61685759 61480960 29,3G 83 Linux')
$this->bbcode_second_pass_code('', 'markus@markus-pc:~$ sudo fsck /dev/sdc1
[sudo] Passwort für markus:
fsck von util-linux 2.34
fsck.fat 4.1 (2017-01-24)
/dev/sdc1: 210 files, 19141/50579 clusters
markus@markus-pc:~$ sudo fsck /dev/sdc2
fsck von util-linux 2.34
e2fsck 1.45.3 (14-Jul-2019)
root: sauber, 39409/1921360 Dateien, 424155/7685120 Blöcke')
Now with both sticks these were successful and have not thrown any errors or have carried out a cleaning. Since I now doubt that two USB sticks are defective, I suspect that it was the update. Because I would still like to post the logs here because I can't imagine that it might be due to the kernel.
How can I pull the boot logs from the USB stick? Also, does anyone have the same problem or any idea why?
Many greetings
Volker