Error Failed To Get Canonical Path Of /dev/root
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more
Error Failed To Get Canonical Path Of /cow
about Stack Overflow the company Business Learn more about hiring developers or posting ads grub-install error failed to get canonical path of /cow' with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu
Grub-probe Error Failed To Get Canonical Path Of /cow
users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top grub failed to get canonical path of aufs Cannot update grub with parameters on live USB up vote 24 down vote favorite 5 I have booted from a live USB ("Try Ubuntu"), that also has a persistent option set (I used LiLi to create one) to do some tests for this pcie hotplug issue I'm having. I'm trying to test some boot paramaters (like in this question) by doing this sudo nano /etc/default/grub sudo update-grub The problem is that grub-install error failed to get canonical path of that last command gives me this: /usr/sbin/grub-probe: error: failed to get canonical path of /cow. It looks like /cow is the file-system that is mounted on /, according to: :~# df Filesystem 1K-blocks Used Available Use% Mounted on /cow 4056896 2840204 1007284 74% / udev 1525912 4 1525908 1% /dev tmpfs 613768 844 612924 1% /run .... Is there a way for me to run update-grub? grub2 12.10 live-usb share|improve this question edited Jul 3 at 13:27 P Smith 440113 asked Oct 28 '12 at 13:53 Nanne 4,51832245 Having this same problem when running update-grub as original poster. When trying to mount /cow, gives error "mount: special device /cow does not exist" Any ideas? –user279868 May 9 '14 at 18:00 This one worked for me: How can I repair grub? (How to get Ubuntu back after installing Windows?) –JJD May 12 '14 at 20:47 Running grub-mkconfig with the proposed command from here showed the error for me. bugs.debian.org/cgi-bin/bugreport.cgi?bug=736928 –x29a Oct 9 '14 at 12:02 add a comment| 1 Answer 1 active oldest votes up vote 35 down vote accepted You'll need to do a bit of remounting and remapping. After booting the liveCD, we'll mount the Ubuntu partition to /mnt with: sudo mount /dev/sd*# /mnt wher
Sign in Pricing Blog Support Search GitHub This repository Watch 36 Star 15 Fork 18 zfsonlinux/grub Code Issues 13 Pull requests 0 Projects 0
Failed To Get Canonical Path Of Airootfs
Pulse Graphs New issue GRUB fails to resolve canonical path to device, grub install error failed to get canonical path of aufs uses invalid partition and fails to detect zfs #5 Open seletskiy opened this Issue Dec 31, 2013 ·
Grub-install Failed To Get Canonical Path Of Airootfs
45 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 18 participants seletskiy commented Dec 31, 2013 Let's suppose following scenario: I've http://askubuntu.com/questions/207663/cannot-update-grub-with-parameters-on-live-usb want to create zpool that use entire device /dev/sda: # ls -al /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001 lrwxrwxrwx 1 root root 9 Dec 31 15:46 /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001 -> ../../sda I'm using by-id path to disk while creating zpool: # zpool create zroot /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001 # zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 ata-QEMU_HARDDISK_QM00001 https://github.com/zfsonlinux/grub/issues/5 ONLINE 0 0 0 errors: No known data errors # zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 110K 3.91G 30K /zroot zroot is mounted into /zroot. So, trying to grub-probe: # grub-probe /zroot grub-probe: error: failed to get canonical path of `/dev/ata-QEMU_HARDDISK_QM00001'. Wut? So, GRUB detected that /zroot is a ZFS (otherwise, how did it know about ata-QEMU stuff?), but if fails to resolve correct path to device. OK, let's try to fix it in a dirty way: # ln -s /dev/sda /dev/ata-QEMU_HARDDISK_QM00001 # grub-probe /zroot grub-probe: error: unknown filesystem. # grub-probe -vv /zroot grub-core/kern/fs.c:56: Detecting zfs... grub-core/osdep/hostdisk.c:319: opening the device `/dev/sda' in open_device() grub-core/fs/zfs/zfs.c:1183: label ok 0 grub-core/fs/zfs/zfs.c:1183: label ok 1 ... grub-core/kern/fs.c:78: zfs detection failed. Didn't work. Hmmm... Looks like grub-probe tries to read from /dev/sda. Take a look: # zdb -l /dev/sda -------------------------------------------- LABEL 0 -------------------------------------------- failed to unpack label 0 -------------------------------------------- LABEL 1 -------------------------------------------- failed to unpack label 1 -------------------------------------------- ... # fdisk -l /dev/sda Device Start End Size Type /dev/sda1 2048 8370175 4G Solaris /usr & Apple ZFS /dev/sda9 8370176 8386559 8M Solar
Posts: 31 Reinstalling Grub This MIGHT be a simple fix, but I'm hoping to get someone else's opinion before I unleash any more demons on my computer. I'm trying to fix GRUB. I'll post some background info to explain exactly what has gone wrong:I decided to do the "update" to https://bbs.archlinux.org/viewtopic.php?id=201380 Windows 10 on my laptop. After it downloaded about 2%, I got the blue screen of death. It rebooted and thankfully Windows still booted up perfectly fine. Still, I decided that I'd had enough of Windows for the time being, so I chose to forget about the Windows 10 update and to go back to trusty Arch instead. But after I tried booting up Arch, I got some nasty error messages. I didn't write them down (and kicking myself failed to for that), but it was something terrible like "/dev/sda does not exist." And then I got the infamous:Bailing out, you are on your own. Good luck.followed by the BusyBox shell prompt."/dev/sda" is an ssd with Arch on "/dev/sda1" (ext4) and Windows 7 on "/dev/sda2" (ntfs). I haven't done any major updates on Arch in the past couple of days, no kernel updates or anything. Before trying to run the Windows 10 update, I double checked that everything on my Arch failed to get partition was working and I backed up my most important files to another drive (thankfully).I had a flash drive of Fedora 22, so I booted that up and ran "fdisk -l" to make sure that my ssd hadn't quit working. The output looked exactly as it should, so I'm guessing that the drive itself still works fine. I thought maybe there was a problem with GRUB, so I tried reinstalling it through the flash drive:sudo mount /dev/sda1 /mnt sudo grub2-install --root-directory=/mnt /dev/sda^ This command reported Installation finished. No errors detected.This method has worked for me before (on Ubuntu, at least), but after booting up, I just get a GRUB prompt. I had the idea that maybe the "grub2-install" command in Fedora is different than the "grub-install" command that Arch uses. Is that possible? If so, I have an Xubuntu iso on another computer and can make a bootable flash drive from it right now. Would it be worth a try to run the above commands through an Xubuntu flash drive (replacing "grub2-install" with "grub-install")? Would it be better to download an iso of Arch and run some chroot commands to reinstall GRUB? Or is there a better option I'm not thinking of?I haven't booted up Windows in months and have had 0 problems with my computer. But as soon as I do, Windows kills it. Unbelievable. Last edited by GreenRaccoon23 (2015-08-22 06:07:24) Offline #2 2015-08-22 0