Skip to main content

Label VFAT device (SDHC SD Card)

Solution:
[root@neo ~]# df -h | grep media | grep -v tmp

/dev/sdc1                      31525888  2944800  28581088  10% /media/8288-1391

[root@neo ~]# mlabel -i /dev/sdc1 ::TABLET

[root@neo ~]# df -h | grep media | grep -v tmp
/dev/sdc1                       31G  2.9G   28G  10% /media/TABLET


Issue:
I have a new tablet that I am attempting to script some automated, or event-driven sync mechanism.  I have added a 32 GB SDHC card to the device and enabled the tablet to ask whether it should mount the SD card as a USB device when connected to a PC.  Initially the device was identified as /media/8288-1391

Not a big deal, but I wanted something a bit easier to quickly identify.
 NOTE: This was written around RHEL 6/fedora 16 - things have changed since this time - most significantly the place where it gets mounted.


[root@neo ~]# tail -f /var/log/messages


Feb 18 22:33:55 neo kernel: [28587.481254] scsi 6:0:0:0: Direct-Access     Lenovo   ThinkPad Tablet  0000 PQ: 0 ANSI: 2
Feb 18 22:33:55 neo kernel: [28587.482412] sd 6:0:0:0: Attached scsi generic sg2 type 0
Feb 18 22:33:55 neo kernel: [28587.489779] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Feb 18 22:34:05 neo kernel: [28598.162053] sd 6:0:0:0: [sdc] 63076352 512-byte logical blocks: (32.2 GB/30.0 GiB)
Feb 18 22:34:05 neo kernel: [28598.166042] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 18 22:34:05 neo kernel: [28598.252008]  sdc: sdc1





Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.