Puzzle to find which SD card is which
 

I have (4) SD cards.

#1 is 8GB, and came pre-loaded with raspbian noobs.
#2 is 32GB and I successfully copied a raspbian image to it and it is working.
#3 is 32GB, and I think I might have broken a while back.
#4 is 32GB, and I which I don't recall but likely did nothing.

Can you guess which one is which? I "think" I put them in order but am not sure as all 4 of them were mixed up in a small bag. Other than the first one which is obvious, how did you tell?

I will be writing a new image to one of the 32GB SDs and ideally not #2 (the 32GB one with raspbian on it). When I saw the device is sda, I was worried as typically I use another machine to view the SDs and on that machine sda is my hard dirve.
Think the #3 broken one is really broken?

When you look at the below outputs, what information do you find important and how do you interpret it? Are there other applicable commands I should have executed to provide additional information?

Is there a way to get some sort of ID from the cards so I know for sure which one is which?

Thanks

#1#2#3#4Note that I removed some of the RAM entries in the above to reduce clutter.

Usually, the output from "blkid" and/or "lsblk -f" will give you a pretty good idea of what is what.

Thanks rknichols, lsblk -f gives similar information as the others, but is a little more to the point. Thanks. I was previously trying blkid, but it appears to only provide information about the sd card actually being used by the RPi I am access the sd from. Looking through the man,can't seem to figure out how to have it use sda1, etc.

Without mounting the cards and examining the contents there is not much that you can guess from the posted information.

SD #4 Looks like you reformatted the drive with a linux file system.

SD #3 Could be you have not done anything.

SD #2 Looks like it might be the copy of your raspbian system.

SD #1 Looks like a NOOBS installed OS.

Thanks michaelk. Looks like I was right on #1 and #2, but not #3 and #4. How did you come to your conclusion?

PS. I had tried mounting them, but still blkid did not appear to target them.

If you run blkid as root, it should probe all attached devices. When run as a non-root user, it can't do that and has to rely on cached information.

Just a big guess...

It depends on the manufacture but typically drives are formatted as FAT32 if less then 32GB and greater as exFAT or NTFS. The start sector is 8192 which could mean original partition table.

Since the partition ID is 83 and the start sector is 2048 that probably means you created a new partition table and formatted with a linux file system.

What happens when you try to mount 3 & 4?

They're kind of small. Take images of them, then zero them out. Various ways to mount the partitions of a dd image. With partx and other things. Fedora being an odd one with lvm2 stuff. Worst case dd the image back on them if you figure out you wanted it that way in the first place. Otherwise blkid can give details like UUID, LABEL, and such. I tend to zero out storage devices then use $(cmp) to verify that they're still zero. The failed ones fail that check.

I would run with one at a time and put a named file on each that identifies it when all are present.