Hello all,
So, how you people mark/label your micro-SD cards to keep them apart ?
I keep them in the micro SD -> SD adapters when not in use. They're big enough to write on or take a sticky label.
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
I keep them in the micro SD -> SD adapters when not in use.
On 17/10/2022 07:17, R.Wieser wrote:
Hello all,I keep them in the micro SD -> SD adapters when not in use. They're big enough to write on or take a sticky label.
So, how you people mark/label your micro-SD cards to keep them apart ?
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled)[quote]
On 2022-10-17, R.Wieser <address@not.available> wrote:
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label >> (would make the whole to thick to fit into the RPi's slot) and I've not been >> able to find a pen thats able to reliable write on the (mostly black
backside) of the card (the written text is easy to rub off, even after a
couple of hours)
I've been trying to keep the cards apart to meticulously putting them back >> into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
A short code on each (A01, A02 etc), written on the front with a very fine sharpie, and a database / spreadsheet / text file / notepad (the physical kind) to record what each code means. Just a letter or number would be fine if you don't have many.
Guys,
Why is it that you don't read the *whole* message before responding ?
[quote=me]
I've been trying to keep the cards apart to meticulously putting them back >> into their SD card "pockets" (which I do have labeled)[quote]
Yes, *I KNOW* how to put those micro-SD cards into (a bigger) something that >I /can/ label and have done so. Thats not the problem. What is is when
they are *NOT* inside those somethings.
Like when having just removed one from my RPi. Should I just put it into
the first empty "pocket" that I can find and hope that whatever it is
labeled with is whats actually on the micro-SD card ? Thats not a
question if, but just when that will go wrong*. :-(
* and with Murphies Law in mind that will happen when I can least use it >and/or causes the biggest damage.
IOW, even if I put the actual, long description on the "pocket" I still need >to match the micro-SD card up with its own "pocket".
... for which some method of labeling the micro-SD card is needed. :-)
Regards,
Rudy Wieser
I spy a market opportunity - micro-SD cards with a tiny
e-in display on them-
you write a file in the root partition to control it.
On my Samsung micro SDcards, those are red-white colored,
perhaps using an engraving pen (I have one too).
Else I just stick it in the laptop with adaptor and see what is on it.
1) most of my micro-SD cards are plain black with white lettering, so a dark-colored sharpie would be almost invisible (I already tried)
2) When writing on the plastic the "ink" doesn't really seem to dry, and can easily be rubbed off (I tried several pens)
A short code on each (A01, A02 etc), written on the front with a very
fine sharpie
3) A big problem: I don't think I can write as small as what you showed in that image you posted without making an unrecognisable mess outof it. :-\
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
On 2022-10-17, R.Wieser <address@not.available> wrote:
1) most of my micro-SD cards are plain black with white lettering, so a dark-colored sharpie would be almost invisible (I already tried)
2) When writing on the plastic the "ink" doesn't really seem to dry, and can
easily be rubbed off (I tried several pens)
Use "Tipp-ex" as a primer? Or white spray paint?
So, how you people mark/label your micro-SD cards to keep them apart ?
But a 40 card holder with a writeable lid thingie.
(e.g. https://www.amazon.co.uk/Water-Resistant-Nintendo-Organizer-Protector-Carabiner/dp/B07Z1S1TS5/ref=sr_1_11
)
Learn discipline when taking out and replacing cards
I'd use a dot of coloured paint. Wipe the majority of it off so it
doesn't leave a blob with any thickness.
http://panteltje.com/pub/SD_card_pencil_markins_IXIMG_0880.JPG
and then store in this transparent thing from ebay:http://panteltje.com/pub/SDcard_card_transparent_storage_IXIMG_0886.JPG
Jan,
On my Samsung micro SDcards, those are red-white colored,
Thats the other problem : I've got exactly *one* micro-SD card which is
/not/ plain black with white lettering.
perhaps using an engraving pen (I have one too).
An *engraving* pen ? One that goes /into/ whatever surface you apply it on >(etching it) ? I don't think that the plastic (over the chip) on either the >front or back is thick enough for that ...
Else I just stick it in the laptop with adaptor and see what is on it.
Ahem suggested something that made me think of the same. Alas, my PC only >shows the "recovery" partition (of a NOOBS installation), and when I put the >adapter in the RPi only see the "boot" and "root" partitions. :-\
Regards,
Rudy Wieser
On 17 Oct 2022 14:12:02 +0100 (BST)
Theo <theom+news@chiark.greenend.org.uk> wrote:
I'd use a dot of coloured paint. Wipe the majority of it off so it
doesn't leave a blob with any thickness.
Hmm how well does nail varnish work ?
3) A big problem: I don't think I can write as small as what you showed in that image you posted without making an unrecognisable mess outof it. :-\
Nev,
I keep them in the micro SD -> SD adapters when not in use. They're big
enough to write on or take a sticky label.
Yeah, I wrote I (try to) do the same. But just imagine /somehow/ having forgotten that and asking yourself which of the two, three is which ...
This also works, pencil writing on the SDcard adaptor
I dunno, dmesg shows /dev/sdc1 and /dev/sdc2 on my laptop
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
So, how you people mark/label your micro-SD cards to keep them apart ?
0.5mm mechanical pencil and very abbreviated names. This is far from
perfect - it rubs off over time.
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
I've done the same, with pencels and "sharpie's". And yes, thats >pretty-much the problem I have too : it rubs off/smears out /way/ too
easily. :-(
I've not tried, but given what you've tried that hasn't worked, have you considered a quick blast of spray paint to create a writable surface? If
you want something more controllable, perhaps a thin coat of white-out (remember that from typing class?) would work.
Check office supply (or art supply) stores for a silver or gold
fine point "paint" marker.
Didn't really want to attach itself to the (smooth, shiny) surface I
tried them on, and, after having dried, effectivily crumbled off when
touched normally.
Does roughening the surface with fine sandpsaper (aka flourpaper) help?
Dennis,
Check office supply (or art supply) stores for a silver or gold fine
point "paint" marker.
Yep, tried those too. :-)
Didn't really want to attach itself to the (smooth, shiny) surface I tried them on, and, after having dried, effectivily crumbled off when touched normally.
But I think I found a workable solution in using the (plastic, ratherNeat, though it might make the uSD little thick to go into some
thin) labels produced by a hand-held Dymo LetraTag.
sockets I've seen.
I've not tried that. But I rather not as I've got little idea in how
thick that that plastic layer is and presuming I could easily destroy
the chip - or even just the microscopic wires connecting it to the rest.
But I think I found a workable solution in using the (plastic, rather
thin) labels produced by a hand-held Dymo LetraTag.
And added, rather large, pre (next to being able to easily removethem) : I do not need to try to scribble the text myself. :-)
By the way, I've tried to the label on both the back and the front side. While putting them on the front side seems to make it a bit more
difficult to put the card into the RPi slot, I'm a bit hesitant to put
them on the back (where they do not seem to give as much trouble), as
that moves the cards contacts further away from the contacts on the RPi
...
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
On Mon, 17 Oct 2022 13:10:48 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:
But a 40 card holder with a writeable lid thingie.
(e.g.
https://www.amazon.co.uk/Water-Resistant-Nintendo-Organizer-Protector-Carabiner/dp/B07Z1S1TS5/ref=sr_1_11
)
Learn discipline when taking out and replacing cards
Never drop it!
On 17/10/2022 13:44, Ahem A Rivet's Shot wrote:
On Mon, 17 Oct 2022 13:10:48 +0100 The Natural PhilosopherThat's punch cards!
<tnp@invalid.invalid> wrote:
But a 40 card holder with a writeable lid thingie.
(e.g.
https://www.amazon.co.uk/Water-Resistant-Nintendo-Organizer-Protector- Carabiner/dp/B07Z1S1TS5/ref=sr_1_11
)
Learn discipline when taking out and replacing cards
Never drop it!
:-) My Desktop runs windows. No 'dmesg' on it.
But I've just taken a look at what 'dmesg' shows on my RPi, and am afraid that I do not even understand a quarter of it. Sorry.
Why not learn
On 20-10-2022 11:37, mm0fmf wrote:
Why not learn
Well, it is Rudy.
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on
label (would make the whole to thick to fit into the RPi's slot) and
I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub
off, even after a couple of hours)
Ask a question and then keep poking holes in any replies.
My reply about using WSL etc. was hopefully for people other than Rudy who may find it helpful to have a free Linux machine on their Windows machine
to help them with their Pi endeavours.
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
On 20/10/2022 10:37, mm0fmf wrote:
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
How is this done? I recently tried and found the following problem:
<https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk>
---
Prerequisites
You will need to be on Windows 11 Build 22000 or later to access this feature. You can join the Windows Insiders Program to get the latest
preview builds.
---
I have Windows 10, incompatible with W11. Can I do it?
My non windows solution has always been to plug the SD card adapter into
a USB socket of one of my other rPis.
On 21/10/2022 11:45, Pancho wrote:
On 20/10/2022 10:37, mm0fmf wrote:
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
How is this done? I recently tried and found the following problem:
<https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk>
---
Prerequisites
You will need to be on Windows 11 Build 22000 or later to access this
feature. You can join the Windows Insiders Program to get the latest
preview builds.
---
I have Windows 10, incompatible with W11. Can I do it?
My non windows solution has always been to plug the SD card adapter
into a USB socket of one of my other rPis.
Easiest thing is to boot a linux live CD or live USB or install virtual
box and have a linux virtual machine. Then you aren't handicapped by Microsofts inadequacies.
On 20/10/2022 10:37, mm0fmf wrote:
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
How is this done? I recently tried and found the following problem:
<https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk>
---
Prerequisites
You will need to be on Windows 11 Build 22000 or later to access this feature. You can join the Windows Insiders Program to get the latest
preview builds.
---
I have Windows 10, incompatible with W11. Can I do it?
My non windows solution has always been to plug the SD card adapter into
a USB socket of one of my other rPis.
On 21/10/2022 11:45, Pancho wrote:
On 20/10/2022 10:37, mm0fmf wrote:
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
How is this done? I recently tried and found the following problem:
<https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk>
---
Prerequisites
You will need to be on Windows 11 Build 22000 or later to access this
feature. You can join the Windows Insiders Program to get the latest
preview builds.
---
I have Windows 10, incompatible with W11. Can I do it?
My non windows solution has always been to plug the SD card adapter
into a USB socket of one of my other rPis.
Don't know. The Windows machines here are all Win10 Pro or Win10
Enterprise. WSL and/or WSL2 install fine on W10. Try it and see if it
works.
If it doesn't automount, you just have to manually mount it with
the right fstype, not the end of the world.
You can probably use Cygwin to achieve the same end but WSL/WSL2 seem to install with less effort IMHO.
On 23/10/2022 12:33, mm0fmf wrote:
On 21/10/2022 11:45, Pancho wrote:
On 20/10/2022 10:37, mm0fmf wrote:
On 17/10/2022 19:25, R.Wieser wrote:
:-) My Desktop runs windows. No 'dmesg' on it.
So install WSL on the Windows system and you can use that to
* automount Flash media plugged into the Windows computer
* read the Linux filesystems with ls
How is this done? I recently tried and found the following problem:
<https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk>
---
Prerequisites
You will need to be on Windows 11 Build 22000 or later to access this
feature. You can join the Windows Insiders Program to get the latest
preview builds.
---
I have Windows 10, incompatible with W11. Can I do it?
My non windows solution has always been to plug the SD card adapter
into a USB socket of one of my other rPis.
Don't know. The Windows machines here are all Win10 Pro or Win10
Enterprise. WSL and/or WSL2 install fine on W10. Try it and see if it
works.
Yes, I have WSL2, I use WSL2 regularly.
If it doesn't automount, you just have to manually mount it with the
right fstype, not the end of the world.
Mount what exactly?
AIUI, The hypervisor on Windows (e.g. Hyper-V, Virtual Box) has tended
to get devices handed to it by Windows. If Windows cannot handle a
device, such as an Ext4 USB, Windows will not make the device available
to the hypervisor.
Now, some hypervisors enable hardware passthru, which may make things
such as the USB device directly available to the VM. I've played with
this in the past and generally found it to be a pain.
You can probably use Cygwin to achieve the same end but WSL/WSL2 seem
to install with less effort IMHO.
It sounds suspiciously like a wild goose chase.
Yes, *I KNOW* how to put those micro-SD cards into (a bigger) something
that I /can/ label and have done so.
Thats not the problem.
What is is when they are *NOT* inside those somethings.
Hello all,
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Besides the surface of the card being tiny, you can't use a stick-on label (would make the whole to thick to fit into the RPi's slot) and I've not been able to find a pen thats able to reliable write on the (mostly black backside) of the card (the written text is easy to rub off, even after a couple of hours)
I've been trying to keep the cards apart to meticulously putting them back into their SD card "pockets" (which I do have labeled), but would really
like the be able to mark the micto-SD cards themselves.
So, how you people mark/label your micro-SD cards to keep them apart ?
Regards,
Rudy Wieser
Look for "paint pen fine tip"
Amazon has dozens of examples. Not very expensive either.
2) I can put a file on the card using an RPi, but I than can't read it under >Windows - and vice-versa. Making it a lot less usefull.
Yes, *I KNOW* how to put those micro-SD cards into (a bigger) something
that I /can/ label and have done so.
Good!
The handiest holder I found is this:
[snip]
Thats not the problem.
Thats not the problem.
What is is when they are *NOT* inside those somethings.
One fellow suggested a "readme" file on the SD card itself
so they're kinda self-identifying.
The bottom line:
I agree that they're too small to label at home.
Jan,
I have an USB card reader, can be used on your running PI to check any
cards.
Yes, you can - but as mentioned only the "boot" and "root" partitions are auto-mounted when its inserted, both the Windows "W95" FAT16 and FAT32 partitions stay invisible.
Under Windows I can not see the Linux "boot" and "root" partitions at all, and only one of the "W95" FAT16 and FAT32 partitions (not yet sure which
one, likely the first, FAT16 one).
And although I'm, as written, quite sure that the RPi can access the "W95" FAT16 and/or FAT32 partitions, I'm not at all sure how I can do that in an easy fashion (a shell script perhaps?).
I might try to figure it out some day, but currently I'm happy with being able to physically label it.
Regards,
Rudy Wieser
I have an USB card reader, can be used on your running PI to check any
cards.
Jan,
I have an USB card reader, can be used on your running PI to check any
cards.
Yes, you can - but as mentioned only the "boot" and "root" partitions are >auto-mounted when its inserted, both the Windows "W95" FAT16 and FAT32 >partitions stay invisible.
Under Windows I can not see the Linux "boot" and "root" partitions at all, >and only one of the "W95" FAT16 and FAT32 partitions (not yet sure which
one, likely the first, FAT16 one).
And although I'm, as written, quite sure that the RPi can access the "W95" >FAT16 and/or FAT32 partitions, I'm not at all sure how I can do that in an >easy fashion (a shell script perhaps?).
I might try to figure it out some day, but currently I'm happy with being >able to physically label it.
Over time I've acquired a few micro-SD cards for my RPi's, and have a
problem with labeling them.
Jan,
I have an USB card reader, can be used on your running PI to check any cards.Yes, you can - but as mentioned only the "boot" and "root" partitions are auto-mounted when its inserted, both the Windows "W95" FAT16 and FAT32 partitions stay invisible.
Under Windows I can not see the Linux "boot" and "root" partitions at all, and only one of the "W95" FAT16 and FAT32 partitions (not yet sure which
one, likely the first, FAT16 one).
And although I'm, as written, quite sure that the RPi can access the "W95" FAT16 and/or FAT32 partitions, I'm not at all sure how I can do that in an easy fashion (a shell script perhaps?).
I might try to figure it out some day, but currently I'm happy with being able to physically label it.
Regards,
Rudy Wieser
Check out "Linux Reader" from www.diskinternals.com
I started using QR codes printed on a labelling machine
Although that could certainly work, its also means that you would always
need the QR code scanning hardware and a computer pulling up the associated information active/running. Not really something I would be doing for a once-in-a-while (might be weeks apart) situations.
Thank you for the suggestion though.
Regards,
Rudy Wieser
Your phone may already have the "QR scanning hardware" and you could keep
the associated information on your Web site.
The QR code could be just the URL.
Chris,
Check out "Linux Reader" from www.diskinternals.com
Thanks. As it so happens I, while looking for something simpler than WSL, found it too. Might even try to use it. :-)
On the other hand, the RPi /should/ be able to access a W95 FAT16/32 partition without the need of any additional software ...
I just do:
sudo mount /dev/sda1 /mnt
and then poke around in /mnt to see what's there. Then:
sudo umount /mnt
Theo,
I just do:
sudo mount /dev/sda1 /mnt
and then poke around in /mnt to see what's there. Then:
sudo umount /mnt
Thanks. I guessed as much, but had nothing to go on.
And I read somewhere I had to create that "mnt" directory first ? You do
not seem to do so.
And a question : do you know wat happens when you (try to) eject the USB dongle containing the uSD card you just mounted a partition of ? I would not like to have either the boot uSD or the mounted one trashed.
Chris,
Check out "Linux Reader" from www.diskinternals.com
Thanks. As it so happens I, while looking for something simpler than WSL, found it too. Might even try to use it. :-)
On the other hand, the RPi /should/ be able to access a W95 FAT16/32 partition without the need of any additional software ...
Theo,
I just do:
sudo mount /dev/sda1 /mnt
and then poke around in /mnt to see what's there. Then:
sudo umount /mnt
Thanks. I guessed as much, but had nothing to go on.
And I read somewhere I had to create that "mnt" directory first ? You do
not seem to do so.
And a question : do you know wat happens when you (try to) eject the USB dongle containing the uSD card you just mounted a partition of ? I would not like to have either the boot uSD or the mounted one trashed.
Regards,
Rudy Wieser
And I read somewhere I had to create that "mnt" directory first ?
You do not seem to do so.
Most distros already have an empty /mnt directory there, ready for
something to be mounted.
...And a question : do you know wat happens when you (try to) eject the
USB dongle containing the uSD card you just mounted a partition of ?
If you use the desktop environment 'eject' button, it may or may not
remove the mountpoints.
If in doubt, 'sync' to ensure anything unwritten is flushed to the disc before removing it.
In the above it's done as root, and a regular user won't be able
to unmount something mounted by root, so the eject complains
something is still using the device.
This is all superstructure though - as root you can mount a drive
partition any damn where you please, even to the point of screwing up
your machine if e.g. you decide to mount it over /bin!!!!
So, either unmount or flush. I had hoped to hear (for sure) that under raspberian the "eject" would automatically unmount first. The less stuff you have to remember the better.Eject is equivalent to unmount on any device that doesnt have a physical
TNP,
And a question : do you know wat happens [snip]
umount /mnt
Yes, thats what theo already said. I was asking about what happens when you forget to do so.
/mnt may or may not be created by default - I think /media/<username> is
often used to mount removable drives at least on my desktop linux
Both can ofcourse be checked.
On my RPi :
/mnt is present and seems to be empty.
When I inserted an USB adapter for a second uSD card it was mounted on /media/pi
Hmm... Can't sudo mount anything on /mnt (owned by root), but can on /media/pi
dmseg was suggesting to do e2... something (I assume an chkdisk equivalent) on sda7, and now that partition isn't auto-mounted anymore. Oh well, I didn't pick that card for nothing. :-)
Regards,
Rudy Wieser
And a question : do you know wat happens [snip]
umount /mnt
/mnt may or may not be created by default - I think /media/<username> is often used to mount removable drives at least on my desktop linux
TNP,
And a question : do you know wat happens [snip]
umount /mnt
Yes, thats what theo already said. I was asking about what happens when you >forget to do so.
/mnt may or may not be created by default - I think /media/<username> is
often used to mount removable drives at least on my desktop linux
Both can ofcourse be checked.
On my RPi :
/mnt is present and seems to be empty.
When I inserted an USB adapter for a second uSD card it was mounted on >/media/pi
Hmm... Can't sudo mount anything on /mnt (owned by root), but can on >/media/pi
dmseg was suggesting to do e2... something (I assume an chkdisk equivalent) >on sda7, and now that partition isn't auto-mounted anymore. Oh well, I >didn't pick that card for nothing. :-)
Well unless yuou pull the live card out of its socket, nothing.
On my RPi :that is because it was mounted by pi the user not root.
/mnt is present and seems to be empty.
When I inserted an USB adapter for a second uSD card it was mounted on
/media/pi
Hmm... Can't sudo mount anything on /mnt (owned by root), but can onshould be able to
/media/pi
e2fsck?
Means the partition is not internally consistent
What I always do is:
if dmesg shows say sdb2
mkdir /mnt/sdb2
mount /dev/sdb2 /mnt/sdb2
cd /mnt/sdb2 to view whts there
This seems to be common practice and never caues problems
when finsished with that partition do
umount /dev/sdb2
Jan,
What I always do is:
if dmesg shows say sdb2
mkdir /mnt/sdb2
mount /dev/sdb2 /mnt/sdb2
cd /mnt/sdb2 to view whts there
This seems to be common practice and never caues problems
when finsished with that partition do
umount /dev/sdb2
:-)
I was just asking NTP the question how I can extract the name of the >to-be-mounted partition from the partition itself (mimicking what automount >does). But if that can't be done that one is a good second-placer.
... wait, now I think of it, the to-be-mounted partitions ID is unique,
while a partitions name doesn't need to be. Hmmm... There is perhaps >something to be said for that "common practice". :-)
I just decided that I dislike the way I have to first create a directory to >be able to mount a partition on it, and after unmounting having to remove >that directory again.
I've just taken a peek at the man pages for both
mount and unmount, but have not been able to spot anything which automates >it. Have I overlooked something ?
Or perhaps a better question : can I invoke automount in some way for it ?
Theo,
And I read somewhere I had to create that "mnt" directory first ?
You do not seem to do so.
Most distros already have an empty /mnt directory there, ready for
something to be mounted.
Ah. Understood.
...And a question : do you know wat happens when you (try to) eject the
USB dongle containing the uSD card you just mounted a partition of ?
If you use the desktop environment 'eject' button, it may or may not
remove the mountpoints.
Thats currently what I know too. "it may or may not". :-)
If in doubt, 'sync' to ensure anything unwritten is flushed to the disc
before removing it.
So, either unmount or flush.
I had hoped to hear (for sure) that under
raspberian the "eject" would automatically unmount first. The less stuff you have to remember the better.
In the above it's done as root, and a regular user won't be able
to unmount something mounted by root, so the eject complains
something is still using the device.
I had not considered that. Hmm... Not being able to eject some removable
USB stick "root" forgot to take with him. Oh well. I guess nothing a shutdown won't solve. :-)
Regards,
Rudy Wieser
If you created /mnt/sdb2 or something like that,
no need to remove it after unmounting
ls -rtl shows last one used last, often saves looking through a list.
There are so many tricks...
At least the command line speaks (sort of) English,
much better than pushing around on a rat or mouse or whatever.
Using automount was dis-encouraged for security reasons last
time I heard about it.
People would find an USB stick in the parking lot of the company,
plug it in, it auto-mounted and installed some virus that send all
company data to some adversary.
People would find an USB stick in the parking lot of the company,
plug it in, it auto-mounted and installed some virus that send all company data
to some adversary.
I never use automount.
e2fsck?Yep, thats the one.
Means the partition is not internally consistentThat is what I guessed from that message (and the errors shown below it in dmesg) too. What I didn't expect that it would be running for half an hour and, in the end, throwing the towel in the ring leaving me with an trashed partition / unusable installation.
Currently I can't even manually mount the partition anymore. 🙁
One other question : Automount creates, before mounting the partition, a folder with with a name ("boot", "root") it probably gets from the to-be-mounted partition itself.
same (so I can take a swing at creating a simple bash script for it) ?
Regards,
Rudy Wieser
On a sunny day (Tue, 25 Oct 2022 21:45:38 +0200) it happened "R.Wieser" <address@not.available> wrote in <tj9e8k$1m6g$1@gioia.aioe.org>:
TNP,
And a question : do you know wat happens [snip]
umount /mnt
Yes, thats what theo already said. I was asking about what happens when >>you forget to do so.
/mnt may or may not be created by default - I think /media/<username>
is often used to mount removable drives at least on my desktop linux
Both can ofcourse be checked.
On my RPi :
/mnt is present and seems to be empty.
When I inserted an USB adapter for a second uSD card it was mounted on >>/media/pi
Hmm... Can't sudo mount anything on /mnt (owned by root), but can on >>/media/pi
dmseg was suggesting to do e2... something (I assume an chkdisk
equivalent) on sda7, and now that partition isn't auto-mounted anymore.
Oh well, I didn't pick that card for nothing. :-)
What I always do is:
if dmesg shows say sdb2 mkdir /mnt/sdb2 mount /dev/sdb2 /mnt/sdb2 cd /mnt/sdb2 to view whts there
Have you ever tried to play an FPS game *without* pushing a dead opossum around ? :-p
No ALWAYS unmount the file system. The "sync" flush is an extra step. As
far as I know "umount" does what sync does before it unmounts the
filesystem anyway.
As
far as I know "umount" does what sync does before it unmounts the
filesystem anyway.
Jan,
If you created /mnt/sdb2 or something like that,
no need to remove it after unmounting
I also considered that, but would not like to have all those empty folders >there.
ls -rtl shows last one used last, often saves looking through a list.
... Though that would certainly help finding the mounted partition back (I >was also thinking about that).
There are so many tricks...
At least the command line speaks (sort of) English,
much better than pushing around on a rat or mouse or whatever.
Have you ever tried to play an FPS game *without* pushing a dead opossum >around ? :-p
(Not that I'm a gamer myself mind you).
Using automount was dis-encouraged for security reasons last
time I heard about it.
It came as part of my RPi OS installation, and I don't mind at all.
People would find an USB stick in the parking lot of the company,
plug it in, it auto-mounted and installed some virus that send all
company data to some adversary.
There is a reason why my RPi is, apart from when needed for a particular >experiment, allways offline. Though in my case I considered the threat to >possibly come from the other direction.
On Wed, 26 Oct 2022 05:37:22 GMT, Jan Panteltje wrote:
On a sunny day (Tue, 25 Oct 2022 21:45:38 +0200) it happened "R.Wieser"$ df -h
<address@not.available> wrote in <tj9e8k$1m6g$1@gioia.aioe.org>:
TNP,
And a question : do you know wat happens [snip]
umount /mnt
Yes, thats what theo already said. I was asking about what happens when >>> you forget to do so.
/mnt may or may not be created by default - I think /media/<username>
is often used to mount removable drives at least on my desktop linux
Both can ofcourse be checked.
On my RPi :
/mnt is present and seems to be empty.
When I inserted an USB adapter for a second uSD card it was mounted on
/media/pi
Hmm... Can't sudo mount anything on /mnt (owned by root), but can on
/media/pi
dmseg was suggesting to do e2... something (I assume an chkdisk
equivalent) on sda7, and now that partition isn't auto-mounted anymore.
Oh well, I didn't pick that card for nothing. :-)
What I always do is:
if dmesg shows say sdb2 mkdir /mnt/sdb2 mount /dev/sdb2 /mnt/sdb2 cd
/mnt/sdb2 to view whts there
works well if you just want to see what storage devices are mounted, their sizes and free space.
TNP,
Currently I can't even manually mount the partition anymore.No, that's part of the spec
Duh. What I ment to say is that e2fsck action, suggested by dmesg and /supposedly/ fixing whatever was wrong with that partition (if anything, 'cause it worked before), rendered it untouchable (read: trashed it). I will likely have to reformat and reimage the card.
No, it doesn't
These folders are created on the root partition itself as part of the
installation.
A bit of misunderstanding : I was talking about the uSD card in an USB adapter. When its inserted into the RPi it gets auto-mounted as "boot" and "root" subdirectories in the /media/pi directory. When ejecting the
adapter those "boot" and "root" folders disappear again. So, where does
the RPi get /those/ "boot" and "root" names from ?
I am not 100% clear on what exactly is your situation, but at some level
you need enough of a working system to run e2fsck on whatever partition
you have that is wonky.
All my actions where done on the uSD card in the USB adapter. And it was e2fsck which trashed that partition to begin with and than threw the towel.
I don't think that running it a second time time will help.
Regards,
Rudy Wieser
Opossum :-) no I am no gamer, do not even know what FPS game is..
but after I did beat the local champion in chess last century
and he got really upset I have not played chess anymore, he
accused me of strange moves
I can do more with a 18F14K22 Microchip PIC that it seems others
need raspies for.
I do not see added value in the complexity modern desktop add.
Currently I can't even manually mount the partition anymore.No, that's part of the spec
No, it doesn't
These folders are created on the root partition itself as part of the installation.
I am not 100% clear on what exactly is your situation, but at some level
you need enough of a working system to run e2fsck on whatever partition
you have that is wonky.
So, where does the RPi get /those/ "boot" and "root" names from ?Ah, ok. That is probably part of the Pis own software doing that.
I suppose you could reinstall using the DD method and see if it works, my
gut tells me it probably wont..
TNP,
So, where does the RPi get /those/ "boot" and "root" names from ?Ah, ok. That is probably part of the Pis own software doing that.
"Probably" ? :-)
The question is if I can retrieve such a name myself - from an unmounted partition ofcourse.
I really should take the time to figure out how a standard install works though. I've already got the 2020-02-13-raspbian-buster.img file
downloaded, but do not have any idea what to expect after I DD that to an
uSD card. And that makes me hesitant. :-\
Regards,
Rudy Wieser
On 26/10/2022 16:20, R.Wieser wrote:
TNP,
So, where does the RPi get /those/ "boot" and "root" names from ?Ah, ok. That is probably part of the Pis own software doing that.
"Probably" ? :-)
The question is if I can retrieve such a name myself - from an unmounted
partition ofcourse.
blkid and lsblk will give info about unmounted but connected partitions
as well as mounted partitions.
On a raspberry pi (u)SD card after writing the RPi image there are 2 partitions, one FAT32 labelled 'boot' and one ext4 labelled 'root'. The
boot prtition can be read on any Windows machine. Both partitons can be
read on any Linux/Unix machine.
I really should take the time to figure out how a standard install works
though. I've already got the 2020-02-13-raspbian-buster.img file
downloaded, but do not have any idea what to expect after I DD that to an
uSD card. And that makes me hesitant. :-\
You can use balenaEtcher or Unetbootin (or similar) to write the image
to an SD card. There is no need for hesitance.
(However dd will (should) work too.)
Get a newer image! https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2022-09-26/2022-09-22-raspios-bullseye-armhf.img.xz
Regards,
Rudy Wieser
In my case using a NOOBS install there are four partitions
blkid and lsblk will give info about unmounted but connected partitions as well as mounted partitions.
The boot prtition can be read on any Windows machine. Both partitons can
be read on any Linux/Unix machine.
but do not have any idea what to expect after I DD that to an
uSD card. And that makes me hesitant. :-\
There is no need for hesitance.
Get a newer image!
Chris,
blkid and lsblk will give info about unmounted but connected partitions as >> well as mounted partitions.
Thanks. lsblk seems to be the one which can, when asked nicely, output the partition label.
The boot prtition can be read on any Windows machine. Both partitons can
be read on any Linux/Unix machine.
In my case using a NOOBS install there are four partitions (ignoring the Extended partition which can't be mounted). Two FAT (off of which Windows ofcourse only wants to show one, 'cause removable media) and two Linux partitions (which are the ones that get auto-mounted). Accessing one of the FAT partitions from within the RPi takes more work.
NOOBS partitioning (I have never used it!!) caters for more than one OS installation (AFAICS), so has >2 partitions. It includes a recovery
partition and a NOOBS data partition.
For an explanation, see this pdf - https://www.brobwind.com/wp-content/uploads/2015/12/NOOBS-partitioning-explained-%C2%B7-raspberrypi_noobs-Wiki-%C2%B7-GitHub.pdf
The biggest problem is that even that "Micro QR" is a 15x15 grid,
making, on a 9x9mm surface, its squares less than a mm across ...
On 25/10/2022 14:12, R.Wieser wrote:
umount /mnt
And I read somewhere I had to create that "mnt" directory first ? You do
not seem to do so.
And a question : do you know wat happens when you (try to) eject the USB
dongle containing the uSD card you just mounted a partition of ? I would >> not like to have either the boot uSD or the mounted one trashed.
/mnt may or may not be created by default - I think /media/<username> is often used to mount removable drives at least on my desktop linux
On 26/10/2022 12:14, Martin Gregorie wrote:
$ df -h
works well if you just want to see what storage devices are mounted, their sizes and free space.
Not on a pi. df -h reports "/dev/root mounted on /"
There is no /dev/root.
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 26/10/2022 12:14, Martin Gregorie wrote:
$ df -h
works well if you just want to see what storage devices are mounted, their >>> sizes and free space.
Not on a pi. df -h reports "/dev/root mounted on /"
There is no /dev/root.
That's because the root partition is supplied by UUID on the command line
(on a Pi 1 running Pi OS from about a week ago):
$ cat /proc/cmdline
coherent_pool=1M snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=Composite-1:720x480@60i vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 console=ttyAMA0,115200 console=tty1 root=PARTUUID=c5881c32-02 rootfstype=ext4 fsck.repair=yes rootwait
Because it's mounted by UUID rather than a device node, the path is
nominally /dev/root but that isn't a device node that needs to exist.
However, separately the UUID can be resolved:
$ ls -l /dev/disk/by-partuuid/
total 0
lrwxrwxrwx 1 root root 15 Sep 22 01:36 c5881c32-01 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Sep 22 01:35 c5881c32-02 -> ../../mmcblk0p2
Basically, I think this is because the bootloader (GPU etc) is selecting which partition to use as the rootfs and supplying it as a cmdline flag, rather than being set by device node in the Linux world.
Theo
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 36:52:26 |
| Calls: | 7,932 |
| Calls today: | 2 |
| Files: | 12,998 |
| Messages: | 5,805,537 |
