I have a USB thumb drive that I just partitioned using the 'fdisk' utility in Linux. Now I am trying to learn the command that will allow me to format the drive as 'fat32' while also setting the disk label on the device as "ocz_usb" when the drive gets mounted. Does anyone know the command I would use that will format the USB drive and properly set the disk label at the same time?
I am a newbie to Linux and I am using CentOs. I am trying to create a new partion on my CentOs VM. I create a new primary partition using fdisk (I use the command fdisk /dev/hda). After I create the partition and use partprobe to write the partition to disk, I try to give the new partition a label. So, I use the command e2label /dev/hda LABEL=test
However, when I enter the command e2label /dev/hda3 , it doesn't display the label for the newly created partition. Am I doing something wrong here? Is the syntax of the e2label command wrong when creating the label for the new partition? Did I miss a step after writing the new partition to disk.
i was trying to re-label my flash drive and i manged to with the help of this command
mlabel -i /dev/sdc1 -s ::test
what does the -i option means cause after i read the manual pages i couldn't find it there. mlabel only takes the "v" "s" "c" switches and no "i" and when I remove the -i option from the whole command don;t work and i can't re-label. its just driving me crazy that every one is using it and no tells what does it do.
I use to know this command but lost it and did not note the entire command on my Linux cheat sheet. Someone once showed me a simple very easy command I could use to simple format a USB flash drive as FAT32 and in the same command also name the label of the drive.I have the device /dev/sdc1 and I am formatting this as FAT32 so it's compatible across multiple systems but also want the drive to have the name 'my_usb'.
I am customizing CentOS and doing the entire procedure through ks.cfg file. Everything is been configured properly except the boot label. I would want Boot label to be customized rather than the default one. Is it possible to achieve this using kickstart?
I realized that my understanding of UUIDs in Linux to specifying hard disk partitions may be erroneous.
The proverbial wisdom is that one should not use hard-coded device specifications in fstab and in the boot menu.lst, such as /dev/sda1 etc. The reason normally given is that if hard disk order changes or the order of partitions change, then the entries will be incorrect since they are hardcoded to partitions following a specific order.
So my understanding was that using hard disk labels, in the form of LABEL=xxxx, or UUIDs in the form of UUID=some-uuid, would prevent these problems when disk order or partition order changed.
I decided to avoid the use of LABEL in case I wanted to change the LABEL on a partition to make the names of partitions more easily identifiable. I then thought that UUID was ideal since it never changed for a partition no matter even if I moved that partition to another drive or added another hard drive and thus changes the order of hard drives on my computer. I essentially thought that once UUID was determined for a partition, it never changed but was somehow part of the partition in the hardware of my computer.
Then I became curious of how a UUID was determined. I did this because I often make backups of partitions on external SATA drives and wanted to make sure that somehow the backup would not duplicate whatever Linux considers the UUID of a partition and present a Linux distribution with two UUIDS which are somehow the same and therefore confuse the Linux distribution to the point that I could not use it. I am aware that UUID means a unique id, but I wanted to make sure I understand how that unique id is determined in Linux. This is especially true since the tool I use to make backups of an entire partition is a Windows application, and not a Linux application, and I wanted to make sure that the backup partition UUID would not duplicate that of an existing partition.
In my very brief research in how a UUID is generated under Linux it appears that it is not something that is part of the hardware of the partition itself but rather a number generated by some parameters of the partition, one of which is the partition order.
If it is, it means to me that if I move a partition from one place to another, even on the same hard drive, or to another hard drive, a Linux distribution will no longer find the partition based on the UUID. In that case it seems as if the UUID is subject to the same weakness as the device specification in fstab and menu.lst in that the order of a partition or the placement of a partition on a particular hard drive will cause the designation to no longer refer to the same partition. In which case it appears to me that only the LABEL parameter is not subject to this weakness and as long as I keep distinct labels for all partitions on my hard drive I could theoretically move them around at will and a Linux distribution will find them correctly. I am aware of course that my computer must always find the boot partition to be able to boot a Linux distribution, so moving Linux parttions where I want them is subject to the ability of my computer to find them from the MBR of my hard drives. But in the main it now appears to me that the best way to insure that moving partitions does not keep a Linux distribution from botting correctly is to use LABEL, and not UUID, in fstab and menu.lst, and of course to make sure that if I decide to change the LABEL of a partition that I must change its entry in fstab and possibly menu.lst before rebooting that distribution.
If I have been wrong in my latest surmises I would appreciate being corrected, as the information I found on UUIDs and how they are generated may not be correct. Also if there is more exact information on exactly how partition UUIDs are generated in Linux I would appreciating anyone pointing it out to me.
Before this partition, I had 6 partition of which /dev/sda6 was the boot partition. I deleted /dev/sda5 partition and hence the earleir /dev/sda6 became /dev/sda5. Now I created two new partitions /dev/sda6 and /dev/sda7.
Due to this change in device label of /dev/sda6 I am not able to boot my computer.
Is there any method to change the disk label of /dev/sda5 to /dev/sda6 ?????
I just installed Fedora15 on my Netbook, I find it simply the best OS for this kind of PC. Anyway I have a little problem, Before install Fedora, I installed Windows 7. Now when I start my Netbook, Grub starts countdown, so far so good, then I press any key to enter OS selector where Windows is shown under "other" I would like to know if I can change the label "other" in "Windows7". Also, can I remove the Countdown and make grub starts by let me select which OS I want to start?
I may have sabotaged my installation beyond repair, but I am nourishing a cautious optimism, as justified below, and would warmly welcome any ideas.Here's the scoop:The harddrive on my Dell Latitude is divided into a number of partitions; I used to run a Windows-Linux dual boot, so I had some EXT3, some NTFS, and some FAT32 partitions, but a few months ago decided to eliminate the windows, and thus converted the ntfs partition into a linux partition. I've been using this newly converted partition for temporary backups; it held no important data. This, at least, was my supposition: yesterday, I decided to change the label on this partition (cosmetic motives), and after cavalierly making the change with GPARTED, I now can't log in.
A few clues about what could be going on:1. The system boots up fine; when I get to the login screen, however, and enter my name and password, I get the following error message: "GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. in any case, it is not possible to log in. Please contact your system administrator."2. All my files are intact (following some advice I saw posted on the forums, I hit cnt + alt + F1 and was able to log in) and as far as I can tell, I am not out of disk space. This gives me hope that maybe I can restore the system without totally reinstalling Ubuntu.That is about all I know. If anyone has any thoughts as to what might be going on, I would be very happy to hear them.
Yeah, I've been messing around with my partitions recently to make them more organized and appealing to my OCD file management habits. My main partition that I use to store all my files and windows programs on was previously labeled "Free" since I installed Ubuntu a few weeks ago and created separate partitions for things, I didn't like the vagueness of the name, so I changed it to "Storage" via GParted Partition Editor.
Yet, for some reason it always changes its self to all capital letters. I label it "Storage", it becomes "STORAGE". I've researched around for others who have similar issues, but they usually ended up with a response similar to "It's Fat32, so it's always capital." I don't see how that's true, considering mine was labeled "Free" for the longest time..
I have a 21GB mounted partition /media/mydata. On my desktop it's labelled as "21 GB Filesystem". When I open it with Nautilus it's called "mydata". Is there a way of changing that label to "mydata" on the desktop?
How do I change the partition label of a drive in openSuse. I am using KDE. I have this howto: Editing FAT32 Partition Labels using mtools But its too long and requires to edit configuration files, when actually for removable media this is a very long cycle.
So I have a Zebra S4M label printer that I have managed to get mostly working under CUPS. To make that work, I have the printer upgraded with the latest firmware, CUPS 1.4.1 with its AppArmor profile disabled and the Zebra EPL/ZPL ppd file that's floating about the internet loaded into cups. The printer is connected via USB to the computer, and is set up in cups using ZPL. The computer acts as a print server for other computers, and everything seems to work ok, with one exception. When the printer runs out of paper or runs out of ink ribbon, the printer stops and displays an error on screen, but CUPS never stops. It keeps taking jobs, sends them to the printer and reports that everything is A-OK. It appears at a certain point, the printer's memory gets full and then CUPS sort of hangs.
But it still doesn't display and errors or stop the quque, it just starts this weird behavior where it eats jobs or combines them into one giant job that it just sits on. What I need is for CUPS to know that the printer is out of paper or ribbon and pause the queue until the error status is clear. I know that this printer is communicating its status in some way, as when it's connected to a windows machine, the print queue stops when the paper runs out. How to get CUPS to recognize the printer status so that I'm not losing jobs? I've tried digging through the debug logs but there doesn't seems to be much help there. I do notice that from time to time CUPS says it's discarding "unused printer status changed" and "unused job progress" events but other than that, nothing I see of interest.
I'm running Ubuntu 10.04 with dual monitors enabled. Technically speaking, everything works just fine. There is one very annoying aesthetic issue, though. There is a label in the top left corner of each display that identifies the monitor (Dell 18", for example). The label does not disappear and is always on top. I had to move my panel to the bottom of the screen just to avoid the label. How can I remove/hide this label?
I'm attempting to set a label for my Windows partition, but it seems risky. Here's a picture of GParted before I attempt to set a label w/ the drive unmounted (wont let me change label when mounted):
After I set a label, the image goes empty as if it will format if I click 'Apply': My question, is it safe to hit apply or will it wipe my drive, and if so, why? In Windows I can just set a label even with the drive mounted.
So I ran a software in both KDE and Gnome respectively and it seems both of them have separate displays. By that I mean, one is displaying a part of the string(a Label) and the other is not displaying the string at all. I will include some relevant information such as the software uses SWT kit. Also the string is displayed perfect in Windows. If it's still not clear I will sum it up in a sentence. I am trying to display a label using SWT kit and, its being displayed correctly on Windows,partially correct on KDE(Half of the string) and not displayed on Gnome.
I have tried GridDat.grabExcessHorizontalSpace=true, but it didn't. how to approach the problem otherwise?
After a recent hard drive replacement, I find that I can no longer boot my Ubuntu partition. It seems that Ubuntu set up GRUB to boot using the disk id, which is no longer valid. I've been using the old GRUB for a number of years, and have always used the LABEL= syntax to assure that the correct partition is booted. There is a dire warning in the /boot/grub/grub.cfg file NOT to edit it. With the old grub, it was just a simple matter to change the menu.lst file. What file DOES get edited to make the change for the new drive? Is there an easy way to get GRUB2 to use the LABEL= form that I know and love? Or is it easier just to reinstall Ubuntu when a drive gets changed?