MicroSD
I've started this documentation to record what's on (some of) my MicroSD cards. New MicroSD cards on top. New images on top.
Note: when writing MicroSD images via the USB adapter, especially on tact, first chown the device for your user and then use 'dd' from your own account, running 'dd' as root is way too risky, one wrong character and you can hose your operating system!
S7
2023-11-06-184522
Raspberry Pi OS (64-bit) on 'glam'.
2023-11-06-181924
Ubuntu Server 22.04.3 LTS (64-bit) on 'glam'.
2023-10-31-123455
Raspberry Pi OS on 'glam'.
S6
2022-02-23-181041
This is the stock MicroSD image that arrived with the Raspberry Pi Model 4 B+ for 'glimmer'.
S5
2023-11-17-072241
I think this MircoSD card might be broken. Won't get detected properly on 'hawk'.
2023-10-28-122400
Tried to install Raspbian for glam but imaging with Raspberry Pi Imager on 'hawk' failed.
2022-02-21-040253
This card was in 'beauty' and I think had Raspbian installed. 'beauty' was an RPi 3B+ which died and is being replaced with a new 4B+.
S4
2021-09-10-165338
This is a 32GB card that came with my TOMLOV DM10 microscope. It is presently in the microscope.
S3
S3 is SanDisk 64GB Extreme Pro Micro SD Card, slated for use in the new Raspberry Pi 4B 'knowledge'.
2023-11-17-072208
I installed Raspberry Pi 64-bit for 'knowing'.
2021-08-23-235713
I installed a configured 'knowledge' on this RPi today. I used the Ubuntu Server 20.04 LTS image from the RPi burning app on my MacBook Pro 'condor' to write the image, and then most of the config was done with salt stack.
S2
S2 is 16GB.
2023-10-28-124917
Installed 64-bit Raspberry Pi OS for 'glam' using Raspberry Pi Imager on 'hawk'.
2022-02-23-181705
I'm not entirely sure what used to be on this card, but now I've imaged it with Ubuntu 20.04 LTS for use in 'glimmer'.
2020-09-03-035827
This image created below is invalid because I wrote the .xz file to the device not the .img file.
------------------- Thu Sep 03 03:11:58 jj5@tact:/home/jj5/desktop/download $ sudo dd bs=1M conv=fdatasync status=progress of=/dev/sde if=freedombox-stable-free_buster_a20-olinuxino-lime2-armhf.img.xz 597+1 records in 597+1 records out 626319792 bytes (626 MB, 597 MiB) copied, 40.1217 s, 15.6 MB/s ------------------- Thu Sep 03 03:23:54
I checked the signature and I think the file downloaded okay...
------------------- Thu Sep 03 03:44:01 jj5@tact:/home/jj5/desktop/download $ gpg --verify freedombox-stable-free_buster_a20-olinuxino-lime2-armhf.img.xz.sig gpg: assuming signed data in 'freedombox-stable-free_buster_a20-olinuxino-lime2-armhf.img.xz' gpg: Signature made Sat 29 Aug 2020 23:14:58 AEST gpg: using RSA key 013D86D8BA32EAB4A6691BF85D4153D6FE188FC8 gpg: Good signature from "FreedomBox CI (Continuous Integration server) <admin@freedombox.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 013D 86D8 BA32 EAB4 A669 1BF8 5D41 53D6 FE18 8FC8 ------------------- Thu Sep 03 03:44:26
S1
S1 is 32GB.
2020-09-03-035838
This fixed the issue I was having because I was writing the .xz file to the device not the uncompressed .img file.
------------------- Thu Sep 03 03:52:35 jj5@tact:/home/jj5/desktop/download $ dd bs=1M conv=fdatasync status=progress of=/dev/sde if=freedombox-stable-free_buster_a20-olinuxino-lime2-armhf.img 3974103040 bytes (4.0 GB, 3.7 GiB) copied, 153 s, 26.0 MB/s 3800+0 records in 3800+0 records out 3984588800 bytes (4.0 GB, 3.7 GiB) copied, 189.873 s, 21.0 MB/s ------------------- Thu Sep 03 03:56:01
2020-09-03-031838
This didn't work because I wrote the .xz file to the device... :P
------------------- Thu Sep 03 03:09:49 jj5@tact:/home/jj5 $ sudo chown jj5:disk /dev/sde ------------------- Thu Sep 03 03:11:10 jj5@tact:/home/jj5/desktop/download $ dd bs=1M conv=fdatasync status=progress of=/dev/sde if=freedombox-stable-free_buster_a20-olinuxino-lime2-armhf.img.xz 597+1 records in 597+1 records out 626319792 bytes (626 MB, 597 MiB) copied, 31.0405 s, 20.2 MB/s ------------------- Thu Sep 03 03:11:58