Fedora :: Grub Used The Standard Drive Notation Such As /dev/sdax Instead Of The Current UUID?
Jul 14, 2010
I've been away from Fedora for a long time, since FC3/4. I seem to recall that at that time grub in Fedora used the standard drive notation such as /dev/sdax instead of the current UUID. Can anyone tell me why this change was made?
Seems to me that using UUIDs presents severe problems if a drive has to be replaced as the restore media (we all backup, don't we?) would not work without modification. How does one determine trhe UUID of a new drive to change the restore media? Sounds like a chickenand-egg routine. There must be some way which I haven't run accross yet. I do notice through experimentation that the standard notation still works, at least in /etc/fstab.
I've got a weird bug sinds I've updated to 11.4. On boot, the main hard drive isn't recognized as /dev/sda but it changes from time to time (probably according to other removable medias plugged in or not). It has been sdb, sde... but not sda anymore.
The trouble is that it boots and then it tries to find /dev/sda2 (the root partition). As it doesn't find it asks me sether he should take "SAMSUNG...whathever...-part2". Answering Yes solves the problem. But then, if I change in Grub the /dev/sde2, it still keeps changing of name. How could I have my hard drive back to /dev/sda2 ?
when my grub references the UUID for the root= parameter, I get a kernel crash. If I change the root= parameter to /dev/<partition>, grub boots without a problem (f13 64-bit)
I'd like to install Lucid on a spare hard drive I have, so I can do my bit for testing it. I have a feeling that if I just burn the latest alpha .iso and install from that, it will replace my current GRUB, whereas I would prefer to simply add the Lucid install as an option in my current GRUB.
Of course I might be wrong, I just wanted to check before I went ahead with it. I was unable to find the info I needed via searching.
Something wrong regarding grub2 (on 9.10). Yesterday everything worked fine and has done for several months. I didn't mess with anything yet when I booted from grub today it informed me that my UUID doesn't exist and that it's given up waiting for root device. I should also mention that it no longer does the 3 second count down either (not sure if thats significant). I can boot into my other linux and windows without issue. This only seems to affect all the ubuntu boot option. This is all way beyond me but I've searched around and tried the fix where you add all_generic_ide to the boot command but that didn't work. I also worked out how to check the UUID but the number look alright.
grub.cfg and blkid below: # DO NOT EDIT THIS FILE # It is automatically generated by /usr/sbin/grub-mkconfig using templates from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ### if [ -s /boot/grub/grubenv ]; then have_grubenv=true load_env fi .....
I am running Wheezy as my main OS in the first drive in my desktop. I use the 2nd drive for data. I am trying to add another OS to multiboot. When I ran grub-update in Wheezy, I am getting device letter for the root device instead of UUID in grub.cfg, in the os-prober section. Like this
I changed my menu.lst to use root=UUID=<long uuid string> instead of the good old root=/dev/sd...
I did that because, if I boot with a usb drive attached to my computer, sda become sdb and therefor nothing works anymore since my friend Kernel can't mount it's root partition. BTW, it works wonders using the UUIDs. The story darkens each time there is a kernel update, dist-upgrade resets my menu.lst back using the /dev/sd... format. and BANG... no more booting again. I am good to change my menu.lst back each time.
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.
Just added a DVD drive to a machine which had no drive before. When I boot I get the error about being unable to find the root drive by its UUID. If I unplug the DVD drive it boots as normal.
I'm guessing the root drive is getting a new name i.e /dev/sda2 instead of sda1 and thus a new UUID. How can I add the drive and fix the UUID issue in grub?
I have a Nook ebook reader and would like it to automatically open a certain application when I plug it in.As standard it just opens a nautilus file browser.I cannot find any settings that will let me associate a drive name/uuid with a certain application and google results came up saturated with how to make bootable USB drives.The only solution I actually found was to make a .autorun script in the root of the drive to start my application, but it still requires user interaction and is not ideal since I would like to implement this across several machines with different users/applications.
Is there something special I have to do to get grub to use UUID's? I am putting a couple of extra drives into a 9.10 system (default installation) with a SCSI drive for the OS. That SCSI drive was sda when I built the machine but of course gets bumped when I add these other drives. The fstab file contains UUID's. All attempts to boot with the other drives attached fail.
I have an mdadm linear array of 4 500GB drives. One of them had a few bad sectors, so I've dd'ed it to a new one (conv=noerror), and tried to start my array. Mdadm refuses, saying, "mdadm: /dev/md4 assembled from 3 drives - not enough to start the array."I had diffed different samples from different positions on the source and the mirror drive and confirmed they were identical. Checking the superblocks confirms three old drives still having their superblocks as expected, while the newly mirrored one has,
daniel@lnxsrv:~$ sudo mdadm --misc --examine /dev/sdf1 mdadm: No md superblock detected on /dev/sdf1. - and, daniel@lnxsrv:~$ sudo blkid /dev/sdf1
[code]....
As before. The mirror apparently has no uuid, but the original does. To confirm my sanity, I did,
How can the uuid not be the same when bit-for-bit from the very first byte of the drive, covering MFT etc., these two drives are identical according to diff?
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 have a Dell ZINO HD and dual booted fine prior to 10.04. Grubs seems to not identify the Win7 OS partition correctly. According to Disk utility DEV/SDA1 is a DELL utility partition, DEV/SDA2 is the RECOVERY partition, DEV/SDA3 is my Win7 OS partition...and DEV/SDA5 is my Linux partition. Ubuntu boots fine... but with GRUB using SDA2 (HD0,2) for win7 I cannot boot to it... is there a fix?
The following is in my GRUB.CFG file ### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows 7 (loader) (on /dev/sda2)" {
I have Ubuntu 11.04 on a hard drive that has Windows 7 as well. I just obtained another hard drive and want to move Ubuntu and all of the contents therein to the new drive, so I can have one drive dedicated solely for Windows (for the family) and Ubuntu on the other. The current drive is a SATA drive and the new is an IDE if that makes a difference.
Problem: I have installed two Ubuntu servers, 10.04 32-bit and 10.10 64-bit, in a multi-boot environment (also have FDOS and WinXPsp3). The 64-bit will not boot because grub can't find the UUID for the disk with the 64-bit system.
Brief Background: Installed 10.04 LTS two months ago with no problems. 10.04 is in a primary partition on hda with FDOS.
Installed 10.10 (64-bit) in a new primary partition on the same hd. The install seemed to go ok, but the MBR and the fs on the 10.04 were corrupted; could not boot. Restored drive, and rebuilt grub.
Installed 10.10 on separate hd (hdb). In grub step all OS's were recognized so I pointed the grub to hda. Grub failed to boot.
Rebuilt grub from 10.04 on hda. All systems recognized but 10.10 will not boot because it says it cannot locate the UUID specified.
Compared the grub.cfg for both systems, the UUID specified for hdb is the same. Also, when I mount the drive for 10.10 on the 10.04 system the drive UUID is consistent.
I know I must be missing some thing, but I know not what. Have searched and can't find any clues. All other OS's boot ok.
Hardware: AMD64 4GB, 2 internal IDE drives (hda and hdb), 1 internal SATA (hdc WinXP), various USB and Firewire Drives (no bootable systems).
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.
'ls -l' gives me the permissions in the long format - drwxr-xr-x format. Is there a way i can get the permissions in a form i can use in a bash script? the only form i can imagine of is the octal one... something like '755' for the above, but i dont know what would give me such an output.... are there other methods to consider while using (rather comparing) them in a script?
I've recently started learning linux OS, and the most confusing for me is the notation in man pages or command synopsis. I was looking for some kind of guide describing it, but couldn't find any. Thing get even worse when there is no standard notation and it looks different from one command to another. In other words, I just want to understand what all these brackets '[ ]', dots like '...' pipelines '|', italic or UPPERCASE words, etc mean at all. I can't tell the difference between [DIRECTORY...] and [FILE]... What does it mean when there are three dots inside the brackets or outside of them? And so on. To conclude, all I need is a comprehensive description for the notation syntax adopted in linux world.
I have two drives on my Lenovo computer. On #1 I have installed Fedora 12. On #2 I have Fedora 9 with a not functioning GRUB bootlloader. I would like to copy a number of directories/files from #2 to #1 but I can't see the #2 drive on #1. What to do?
I have windows on my box, I have fedora 14 on my external that goes through my usb. Grub is installed on my usb. Since the only thing stored on my external was fedora i really didn't have to do much to it. just go into bios and boot from usb. Now that im using fedora more, Id like to add Vista to my choices. I guess the numbers change once your using an external drive. Ive read some of the problems like mine but they didn't quite do it. Im going to inclose 2 screen shots of my drives/partitions and my grub.conf.
# grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
Is anyone aware of a program which will open .mus music notation files or convert them to .xml files? I have several files from FINALE which I would like to open in Linux, but Linux distros will not allow FINALE to run. .xml files will open in MuseScore.
I just tried to install F13. I can't install grub to any drive other than that which F13 gets installed on. When I click on the drop-down menu, only /dev/sdd is available.
I have created usb stick from which I install fedora. The bootloader is on the MBR of the usb stick and I want to put it onto the harddrive.I have tried running grub and setting up the MBR on the hard drive, but attemts to load the kernel fail with "Error 15: File not found".
I have some checksums.md5 verification files from an ntfs external drive, but using windows notation: instead of /, spaces between file names (not escaped), reserved shell characters (like (, &, ', to name a few). The checksums.md5 has a bunch of checksums and filenames:
[code]...
I want to use this checksums.md5 to verify the files that I've copied to my machine: but I'm on a Linux, so I need to convert the names inside checksums.md5 from Windows to Linux to use the md5sum utility from the shell. The first line in my example would become: f12f75c1f2d1a658dc32ca6ef9ef3ffc My Windows & Files (2010)/[bak]/testing.wmv Is there some application for this (converting a file listing, from windows cmd notation, to linux shell notation) or will I need to create a bash script using sed that just "replaces" what is "wrong" with the filenames
I'm trying to figure out how to change the tomboy saving notation (.note) to (.txt). I'm fairly new to Linux so I may be wrong in thinking this is possible. However, if it is possible, a finger in the right direction would be appreciated.
PS: if it isn't possible, maybe there is a way to change the name of the actual .note files in ~/.local/share/tomboy/ to something more readable. Right now they show up like this:
8e824ab7-ba6f-4018-b74d-1a5a245a60bd.note Which is of course makes it difficult to determine which file I'm actually looking at.
I have installed Fedora-9 and i customized my kernel. But i did a big mistake in the last steps while customizing. Unfortunately i have executed below shell cmd. grub-install /dev/sda windows drive is not visible But /dev/sda3 is a windows vista file system, now sda3 file system is not in visible for both in linux and also vista OS. How can i retrieve my data back in vista sda3. Here is the info of system
$ su -c '/sbin/fdisk -l' Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
I have 2 CPUs Which are Intel and AMD based. I used F9 before and didnt have any issues while I removed the hdd that I'd installed F9 on INTEL based and then put my hdd on my AMD based cpu. Well it booted and ran perfectly no issues came up.And then I've done the upgrade to F10 (clean install on INTEL). I do the same case above.But I got error msgs it said that the UUID cannot be found (I was using label on F9 fstab and worked fine).
I put back my hdd to intel based cpu and then try to edit my fstab and menu.lst (change UUID to LABEL). WOW I thought by changing UUID from fstab and menu.lst would resolve my problem but it doesnt solve anything. My devices (sda1/2/3, /boot, and /home) cannot be reconized.Well do you guys know how to change UUID to LABEL? and what exactly my problem?
