Ubuntu :: Safe To Change Fstab UUID Entry For The System To /dev/sdb4?
Nov 13, 2010
is it safe to change fstab UUID entry for the system to /dev/sdb4? and after editing fstab, is there a script or command I need to run to release lock or update mount information? edit: I see not correct, and therefore not safe,but is there a format to tell linux to use /dev/sda1 instead of UUID= or label= .
all of a sudden my pc decided no to start anymore.YOu might be aware of the ide/sata driver problem, well it was the problem. I reinstalled grub with suse dvd and it went ok. Pc working properly. But then i tried to fix this once for all and changed the fstab options from /dev-by-id to uuid (all partitions : swap, /, /home etc ).Is uuid a definite solution ?Why is the pc not able to start from there ?
Since i moved the partitions with uuid option in fstab and even after reinstalling grub the pc is not starting anymore . It gives me the boot menu (linux suse/failsafe) and then a black screen left with no keyboard nor mouse available.
I cloned one of my hard drives to another, using Acronis True Image Home 2011.In the process, of course, fstab got copied verbatim from old to new.I then, using a livecd on a flash drive, mounted the new drive, went into fstab and rewrote the UUID's, using the numbers I'd gotten previously by doing sudo blkid.Now, the new drive had the UUID's revealed by that command.Then, I used boot-repair, from yannubuntu, to make that drive bootable, since it wasn't after the cloning and after the fstab rewrite.The drive is bootable, and it's mountable from a flash drive, or from the old drive.
I can access files either way.the fstab file on the new drive still has the old numbers, yet when I ran boot-repair, it apparently changed the UUID's for sectors 1 and 5 on the new drive.fstab seems to be irrelevant at this point, yet everything I read about it indicates that it is not only relevant, but necessary.I don't understand how I can be accessing the drive when the fstab contains UUID's that are no longer pertinent to any hardware on my system.
I've had two hd's in my box forever. for more space and backup reasons. Well I have started running the Debian Squeeze distro since December. I've had many issues, some are still unresolved. but now I'm running into major headaches with the fstab. Specifically dealing with/wondering why UUID's are used instead of the old /dev/hd? I was a little annoyed when I tried Kubuntu to find /dev/sd? used instead of /dev/hd? but that was workable. But the UUID's are a nightmare. Here's my problem.
My main box is finally giving up the ghost. The mobo is dying. So in order to do some tests I took my hd bundle (my two hard drives with their cables) physically out of the box and temp installed them in a test box. I wanted to do some benchmark and other tests. I got all kinds of errors. I found that the system wasn't recognizing the UUID's listed in fstab. My concern is when the new mobo gets here next week I won't simply be able to plug the hd's in like I always have been and just let Linux reconfigure itself (Debian used to be good about this). I really don't want to have to clean reinstall if it's not needed.
So for this I have two questions. WHY developers decided to drop using /dev/hd? or even /dev/sd? ?
And is it possible to revert fstab's listings back to the old /dev/hd? settings. In debian fstab had lines commented out showing how each partition was listed in it's /dev/hd? status during install.
I'm getting really sick of all these archane changes in ALL aspects of linux that don't seem to have any good explaination or need.
For reasons long and unique, I want to disable UUID in my recent Ubuntu 10.4 install, and use the old fashioned /dev/sda1 /dev/sdb3 etc. method. I had this "all fixed" under GRUB (pre-2) on Ubuntu 8.04 and it has served well and bug free for years. (Warning: I use old stable hardware - others may have disasters.) But with GRUB2, the task seems more complicated. (This guide me make the backups I haven't done since the fresh install 2 weeks ago.)
Is the following process complete, necessary, and accurate... Edit the file /etc/default/grub to remove the # in the line... #GRUB_DISABLE_LINUX_UUID="true" ... making sure to add the two " if missing .....
Copy nearly the entire /boot/grub/grub.cfg file into /etc/grub.d/40_custom and then... Comment out every line that says... search --no-floppy --fs-uuid --set (etc.)
Change every line that says... linux /boot/vmlinuz-2.x.yy-zz-generic root=UUID=(etc.) into... linux /boot/vmlinuz-2.x.yy-zz-generic root=/dev/sda1 Edit /etc/fstab and change every instance of UUID=(etc.) to the appropriate drive and partition e.g. /dev/sda1
edit /etc/initramfs-tools/conf.d/resume and change RESUME=UUID=(etc.) into RESUME=/dev/sda1 Run update-grub
Do all the above, every time I do a kernel upgrade. (Is it important to do all the above before or after rebooting for an upgrade?) Am I correct, succinct, and complete in the above process? Any mistakes? Any omissions?
I have ntfs partition installed bran new ubuntu system. I have some problem with unrar utf8 character zip files.Then i change my fstab file that uses files in D:ubuntudisks oot.disk and i added with out no fearless Code: ,utf8 and after all now i can't boot my linux system it does not allow me to change anything in fstab file. Although i use as a prefix sudo or as a root "sudo -i" commands I dont have any right to change it.
Simple. UUID is apparently limited to a single UUID to be defined. Example UUID="DEB0-0001","3338-3164" separated with a comma is not working.
What could be the linux alternatives for pluging several UUID disks? How to bypass when there is a CF card and a reader box, since blkid gives no UUID ?
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.
But now I'm trying to figure out how to make it auto mount on boot. I understand I need to add a new entry to /etc/fstab, so I perform: $ sed -i '$ a/dev/xvdf /mnt/mongo xfs defaults 1 1' /etc/fstab But, after reboot, it seems that the auto mount didn't work. The device didn't appear in the df -h list.
How do I make an entry in fstab for my mp3 player if connected but won't cause errors if not connected. If I plug the player in after boot it mounts on /dev/sdd, but if it's plugged in before boot it mounts on /dev/sda. I would like it to always mount on /dev/sdd. Plus if I reboot into my Natty install, from maverick, with the player plugged in it won't even boot. When mp3 player connected after boot.
I just went from Jaunty to Maverick. I booted Maverick and manually mounted my Windows Network drives by clicking on the appropriate "mount" command in the directory /media.I then created an fstab file like I did in Jaunty. Here is the smb mount command that I had in the fstab file. I had a file with the user id and password in the credentials file.Code://???.???.??.?public_p/media/servername smbfs credentials=root,dmask=0777,fmask=0777 0 0This provided me access to my server for the past 18 months.I modified the fstab file for Maverick which was working fine for 3 days so I would automatically mount the server drives.
I have a disk that is formatted as NTFS (from Windows 7 - dual boot with Ubuntu Studio). This is not a boot disk, just an extra disk for data. I would like it to be available to both OS's. In Ubuntu, I went to System -> Administration -> Disk Utility and saw the disk. I clicked on the volume name and clicked Mount. I would like this always mounted when I restart Ubuntu. It was mounted as /media/Data2 (/dev/sdc5).What is the best/preferred way to format the entry in /etc/fstab?
One entry I have put in fstab results in the failure of a partition to be mounted at boot time. I get the message:
Code: The disk drive for /media/WinXP is not ready yet or not present. Continue to wait; or Press S to skip mounting or M for manual recovery If I choose M and enter the command: Code:mount -t ntfs /dev/sdb1 /media/WinXP then I get no error message, but the partition still doesn't seem to be mounted, when boot completes.
I don't understand this failure. I have created my fstab file using UUIDs to boot Ubuntu on my dual boot machine. It works fine, booting from the hard-disk which is Master on my Secondary IDE channel. For Ubuntu booting the MBR and grub menu are on this disk. The default is to boot Ubuntu , but with an option to select Windows Xp.
As an aside, I can set an option in my BIOS to make the Master disk on the Primary IDE channel the first disk, rather than the second disk. Then the system boots from the MBR on this Primary IDE channel and boots only to WinXP. That works fine.
When running Ubuntu I use space on the Windows disk (on the Primary IDE channel) to hold backups of key Ubuntu files in case I loose Ubuntu - as I did for the past few days. So, to mount this partition I inserted this line into my fstab:
Code: UUID=0e4851c44851ab6b/media/WinXPntfsnosuid, nodev, allow_other00 I know the UUID is correct because I have checked it with blkid. But the partition is not mounted at boot time. I don't even get an icon for the partition on my desk top. It appears in the 'places' menu, as unmounted, but mounts as soon as I click on it. However, this causes some of my linux apps, which want to load and save to this partition, to post an error message until I have manually mounted it via clicking on it in the Places menu. I want to avoid this manual step by having the partition automatically loaded at boot time. What am I doing wrong?
I am trying to mount a smb share on an ubuntu machine and for the life of me I can't figure out the fstab entry. The server is running fine and the windows machines can map their shares fine, I just cant figure out the fstab entry for an ubuntu box.at this point the fstab looks like this(although I have tried many variations)
i want to mount NTFS by normal users so i used the following entry in fstab /dev/sda6 /media/Mostafa ntfs-3g noauto,exec,rw,user 0 0 however when i try to mount the partition i get the following error Unable to mount Mostafa
Error mounting: mount exited with exit code 1: helper failed with: Error opening '/dev/sda6': Permission denied Failed to mount '/dev/sda6': Permission denied Please check '/dev/sda6' and the ntfs-3g binary permissions, and the mounting user ID. More explanation is provided at NTFS-3G Questions at Tuxera
when i starting the server..it is coming to maintenence mode and saying repair file system...because /home1 was not found in /etc/fstab.. when i tried to remove the entry from fstab for /home..it is read only!!
I am running SUSE 11.1 on a 80Gig IDE HDD, I have added a 160 SATA HDD which I wish to use as storage. fdisk reports it as /dev/sda1 - W95 fat 32 LBA. What would the fstab entry be to make the disk mount automatically on boot, so that it shows on the desktop ready for use.
I have centos 5.3 installed. I plugged in a WD usb external HD, Icon is showing up on desktop everything is working formatted with ext3. I would like to have an entry for this in my /etc/fstab file, and I need to know how to enable Quotas on some files on it.
I run a headless Ubuntu 8.04 server, which acts as a web, email and file server. I am sticking with 8.04 as it is a LTS release and will upgrade to the next LTS when it is released.
I have two external USB drives, that I need to mount at boot. I have been using /etc/fstab up until now, with the following entries:
Code:
However, as I gather from doing searches is quite common, occasionally I get an error during boot (causing the system to drop to a recovery shell) because the USB drives take time to wake up and the system hasn't found them by the time it reads /etc/fstab.
From doing searches, it seems there is nothing you can do to fstab to fix this, so you need to mount them using an rc.local script instead, using:
Code:
The problem is, as I have two USB drives, their /dev/sdxx location changes between boots. I thus want to use UUID codes as I do in fstab, however I haven't found anything about this.
Does anyone know how I can use the mount command and UUID to mount a drive in rc.local and what options I have to use the mount the drive with the same options that I am using in my fstab entry? Obvisouly, I can't refer back to fstab using the mount command, because then I will still get the boot error issue if they are listed in fstab. And there is no space internally for the USB drives as there is already two internal drives.
I have an SiI hardware SATA RAID card, with two 500GB disks in mirrored RAID configuration. When I first plugged them in and set it up, things seemed to work ok, but on boot the raid controller told me that the RAID needed rebuilding, and it would happen automatically after POST. So I didn't worry about it, and the drive mounted fine, and it's been that way for years. I just went in and manually on-line rebuilt the RAID in the controller's BIOS, and now when I boot into Ubuntu, both disks show up in fdisk, but neither show up in /dev/disk/by-uuid. Am I missing something?
I spent all day learning some concepts of Samba which I left while preparing for RHCE.One of them is how to permanently mount (fstab entry) windows shared folder.Manually mount command is running fine for me.
I have, as I have in the past, copy/pasted a partition using gparted to get a working OS to another place.
I have always done this in the past to a different drive. Never paid much attention to the UUID.
This time I did it on the same drive. The partitions have the same UUID. This is not a good thing.
The copied OS boots and mounts fine as I edited the fstab to go by /dev/sdxy (where x is the drive and y the partition). My grub uses a custom menu using symbolic menu entries so it goes by the partition definition instead of UUID too.
I would really like to change the UUID on that partition.
Been doing some installations in a newly upgraded machine where I'm setting up two instances of 8.2 in slightly different configurations.Installing from netinst AMD64 DVD with firmware non-free. First installation goes smooth as then the second changes the UUID of the swap partition, meaning that the first then can't find it. To add insult to injury the second installation doesn't install GRUB in the MBR of the HDD.
Nothing different or special about the installation which is standard graphical with manual allocation of previously set up partitions. I don't touch the swap drive in the partitioner - just point to the correct partitions for / and /home as I want them. This is exactly as I've done before, many times.Setup asks me if I want to install GRUB in MBR and I answer "No" (because it would otherwise load in MBR of sda where I want it on sdb) then point to sdb in the next screen. Again really nothing different to what I've done dozens of times.
I've just upgraded my wife's netbook to UNR 9.10. This seemed to go well and the netbook has been working fine since. Yesterday my daughter used the netbook with out any issues, but when my wife tried it halted during boot with:
Swap waiting for UUID: xxxxxxxxxxxxxx
After a couple of reboots it started working fine, but looking at /etc/fstab the entry for swap is different to the UUID shown in blkid Do I just update fstab with the UUID from blkid?
I am very much new to Linux programming. My question is Is there any way to read UUID of a device or partition in linux programatically. Is there any c/c++ API for user-space applications. I found some commands "sudo vol_id --uuid /dev/sda1", "sudo blkid", "ls -l /dev/disk/by-uuid/". But all are commands which we need to run in terminal. But i need to achieve this from a c/c++ program. Can some one help me in this problem.(FYI: I need to read uuid of root filesystem ("/") where Linux has been installed.)
Around with my Login default screen and set my login to "Ubuntu (Safe Mode)". Now, it seems as if the system does not grant me the authority to change it back to another default login.