missing filesystem

[réjean]

Hi all!

I am presently using a live USB Linux Mint trying to repair my filesystem

I have very little luck so far;

 

mint / # blkid
mint / # lsblk
mint / # fsck
fsck from util-linux 2.20.1
fsck.ext4: Unable to resolve 'UUID=f0220344-2591-42e6-baf6-e6be49be4071'
mint / # fsck /dev/sda
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext2: No such file or directory while trying to open /dev/sda
Possibly non-existent device?
mint / # fsck /dev/sdb
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext2: No such file or directory while trying to open /dev/sdb
Possibly non-existent device?
mint / #

 

Now I know the partitions and their content are still there;

 

so any suggestion anyone? Like I said in the other post I reinstalled Linux Mint 17 last night hoping it would solve the problem. The installation went well. Grub was installed on /dev/sda but upon rebooting I got the following;

 

Verifying DMI Pool Data...
error: no such device: e2f44f52-8fd1-42ca-a661-9f4ad3f86a79.
Entering rescue mode
grub rescue>

Edited July 20, 2015 by réjean

[securitybreach]

This error means that your using the wrong UUID.

error:no such device: e2f44f52-8fd1-42ca-a661-9f4ad3f86a79

 

Run blkid to find the correct one.

[réjean]

Thanks josh!

Now what next?

 

mint@mint ~ $ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="System Reserved" UUID="eaa8c559-8024-4c8f-914b-8cbf464b6d51" TYPE="ext4"
/dev/sda2: UUID="47387537-47f2-4568-a284-9f25dd5bea8f" TYPE="ext4"
/dev/sda5: UUID="f0220344-2591-42e6-baf6-e6be49be4071" TYPE="ext4"
/dev/sda6: UUID="f7c60a6b-e33b-45c1-b201-44c22763fb9e" TYPE="swap"
/dev/sda7: UUID="443E317E38E48AC0" TYPE="ntfs"
/dev/sda8: UUID="349286d9-8878-4184-b72c-9e5e0eb65da0" TYPE="ext4"
/dev/sda9: UUID="3f6efbd4-f3fc-43dd-872c-2ee4305edc10" TYPE="ext4"
/dev/sda10: UUID="c7b8ba1f-6e0f-426c-8676-d13d836abf69" TYPE="ext4"
/dev/sda11: UUID="cf78ad89-6415-48f8-b9dc-93401c01c180" TYPE="ext4"
/dev/sda12: UUID="0e5a3c08-8c60-4141-a232-95acc51ef912" TYPE="ext4"
/dev/sda13: UUID="9cfd579a-1e91-4bba-a4c9-d2a10a0d74af" TYPE="ext4"
/dev/sda14: UUID="5498d2cf-9d68-4f8d-9ca2-8240974d5b37" TYPE="ext4"
/dev/sda15: UUID="cafc9f4a-a7b9-4d46-91d3-e08a816800fb" TYPE="ext4"
/dev/sda16: UUID="98abcdf8-436a-4d9b-a9fd-612b33f8e42c" TYPE="ext4"
/dev/sda17: UUID="f2504d90-fded-4aac-8d1d-00da1c9ab495" TYPE="ext4"
/dev/sda18: UUID="ae2a887f-a535-42c9-8974-40a9797b3808" TYPE="ext4"
/dev/sdb1: UUID="FEE828A9E82861DF" TYPE="ntfs"
/dev/sdb5: UUID="02E456D9E456CE93" TYPE="ntfs"
/dev/sdb6: UUID="8814195614194898" TYPE="ntfs"
/dev/sdc1: LABEL="Linux Mint 17.2 MATE 64-bit" TYPE="iso9660"
/dev/sdc2: SEC_TYPE="msdos" UUID="3006-9304" TYPE="vfat"
mint@mint ~ $

 

I tried;

mint mint # mkdir /mnt/mint
mint mint # mount f0220344-2591-42e6-baf6-e6be49be4071 /mnt/mint
mount: special device f0220344-2591-42e6-baf6-e6be49be4071 does not exist
mint mint # 

 

getting better;

mint mint # mount -t ext4 /dev/sda5 /mnt/mint
mint mint # 

 

and;

mint mint # os-prober
/dev/sda1:openSUSE 13.2 (x86_64):SuSE:linux
/dev/sda11:Ubuntu 14.04.2 LTS (14.04):Ubuntu:linux
/dev/sda14:Mageia 5 (5):Mageia:linux
/dev/sda16:PCLinuxOS:PCLinuxOS:linux
/dev/sda17:Manjaro Linux (0.8.13):ManjaroLinux:linux
/dev/sda5:Linux Mint 17.2 Rafaela (17.2):LinuxMint:linux
/dev/sdb1:Windows 7 (loader):Windows:chain
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
mint mint #

 

but;

mint mint # grub-install /dev/sda
grub-probe: error: failed to get canonical path of `/cow'.
Installing for i386-pc platform.
grub-install.real: error: failed to get canonical path of `/cow'.
mint mint # update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
mint mint #

 

and I have;

mint ~ # df
Filesystem	 1K-blocks    Used Available Use% Mounted on
/cow			 4087716   92780   3994936   3% /
udev			 4076344	  12   4076332   1% /dev
tmpfs			 817544    1436    816108   1% /run
/dev/sdc		 1664640 1664640		 0 100% /cdrom
/dev/loop0	   1622912 1622912		 0 100% /rofs
none				   4	   0		 4   0% /sys/fs/cgroup
tmpfs		    4087716	   4   4087712   1% /tmp
none			    5120	   0	  5120   0% /run/lock
none			 4087716	  76   4087640   1% /run/shm
none			  102400	  36    102364   1% /run/user
/dev/sda5	   22029812 4958936  15928760  24% /mnt/mint
/dev/sda1	   32380312 7013604  24293376  23% /mnt/suse

Edited July 20, 2015 by réjean

[securitybreach]

You cannot reinstall grub from the livecd environment without chrooting into whatever installation you want to install grub from

sudo mount /dev/sda1 /mnt

sudo chroot /mnt

sudo update-grub2

 

Replace sda1 with whatever partition your trying to install grub from.

[réjean]

I tried installing and using "boot repair"

 

...
E: Some index files failed to download. They have been ignored, or old ones used instead.
mint ~ # apt-get install -y boot-repair && boot-repair
Reading package lists... Done
Building dependency tree	  
Reading state information... Done
The following extra packages will be installed:
 boot-sav glade2script
Suggested packages:
 mbr mdadm clean-ubiquity boot-info os-uninstaller
Recommended packages:
 pastebinit boot-sav-extra efibootmgr
The following NEW packages will be installed:
 boot-repair boot-sav glade2script
0 upgraded, 3 newly installed, 0 to remove and 150 not upgraded.
Need to get 446 kB of archives.
After this operation, 2,925 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu/ trusty/main glade2script all 3.2.2~ppa47~saucy [42.3 kB]
Get:2 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu/ trusty/main boot-sav all 4ppa33 [392 kB]
Get:3 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu/ trusty/main boot-repair all 4ppa33 [11.6 kB]
Fetched 446 kB in 1s (284 kB/s)	   
Selecting previously unselected package glade2script.
(Reading database ... 175257 files and directories currently installed.)
Preparing to unpack .../glade2script_3.2.2~ppa47~saucy_all.deb ...
Unpacking glade2script (3.2.2~ppa47~saucy) ...
Selecting previously unselected package boot-sav.
Preparing to unpack .../boot-sav_4ppa33_all.deb ...
Unpacking boot-sav (4ppa33) ...
Selecting previously unselected package boot-repair.
Preparing to unpack .../boot-repair_4ppa33_all.deb ...
Unpacking boot-repair (4ppa33) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Setting up glade2script (3.2.2~ppa47~saucy) ...
Setting up boot-sav (4ppa33) ...
Setting up boot-repair (4ppa33) ...
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

[réjean]

I still have a problem with cow;

 

mint ubuntu # cd /mnt/suse
mint suse # ls
bin   dev  home  lib64	   mnt  proc	    root  sbin	 srv  tmp  var
boot  etc  lib   lost+found  opt  read-write  run   selinux  sys  usr
mint suse # grub-install --root-directory=mnt/suse/boot /dev/sda
grub-probe: error: failed to get canonical path of `/cow'.
Installing for i386-pc platform.
Installation finished. No error reported.
mint suse # update-grub2
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
mint suse #

[securitybreach]

Did you try to chroot in and repair as noted above?

[réjean]

Yes !

 

mint@mint ~ $ sudo mount /dev/sda1 /mnt

mint@mint ~ $ sudo chroot /mnt

:/ # sudo update-grub2

sudo: update-grub2: command not found

:/ #

 

[code]

[securitybreach]

Well that looks like you do not have grub installed on that partition.

 

Personally I would just install a distro and have grub find the other distros versus trying to fix this mess. You will probably not fix this anyway so you may as well take the easy route. Unless you have some file you need, I would wipe it all.

[Hedon James]

Yes !

 

mint@mint ~ $ sudo mount /dev/sda1 /mnt
mint@mint ~ $ sudo chroot /mnt
:/ # sudo update-grub2
sudo: update-grub2: command not found
:/ #

 

A little above my pay grade, as I don't completely understand what you're doing, and I'm a little lost with your bazillion partitions, but 2 quick comments which may help or may have absolutely nothing to do with your issue:

 

1. isn't a hash prompt indicative of "root" users? why are you typing "sudo" when you're already root

2. while you may have version 2 of grub, I believe the package is just called grub; if you're already root, you want to type

 

update-grub

if you're a regular user with admin privileges, you want to type

 

sudo update-grub

 

If neither of the above are helpful, I believe Yanni's Boot Repair package would be helpful here, which can be installed from a Live environment:

http://www.ubuntugeek.com/boot-repair-simple-tool-to-repair-frequent-boot-problems.html

 

I would give that a shot before I take up SB on his advice. JMO...

[amenditman]

HedonJames nailed it. As usual, syntax errors will kill what you are trying to do.

[réjean]

Yeah! Boot repair worked!

I don't know why it didn't this morning but this time it did. I'm replying from PCLinuxOS but I saw all the entries in the bootloader and I assume the MBR has been fixed completely. Thanks everyone!

I can tell you 2 things;

1. I have 2X 1tb hd with a 500 GB storage partition on each and I'll make sure my important stuff is in both.

2. I will unplugged the hd I use the most (sda) before I attempt to install Arch and install it on the other drive which as only Win XP which is broken and Win 7 which I use only for playing games once in a while.

about the syntax; I used 'sudo' only once as root after I had chrooted and it was kindda out of despair.

[securitybreach]

good deal

[Hedon James]

Yeah! Boot repair worked!

I don't know why it didn't this morning but this time it did. I'm replying from PCLinuxOS but I saw all the entries in the bootloader and I assume the MBR has been fixed completely. Thanks everyone!

I can tell you 2 things;

1. I have 2X 1tb hd with a 500 GB storage partition on each and I'll make sure my important stuff is in both.

2. I will unplugged the hd I use the most (sda) before I attempt to install Arch and install it on the other drive which as only Win XP which is broken and Win 7 which I use only for playing games once in a while.

about the syntax; I used 'sudo' only once as root after I had chrooted and it was kindda out of despair.

 

we've all been there once or twice. and when I say "we", what I really mean is "me". glad you got it worked out, as that would have a real beast to start over and reconstruct!

[V.T. Eric Layton]

Trash my mbr? H3LL NO! Ain't never done that... more than 10 or 50 times.

[securitybreach]

Trash my mbr? H3LL NO! Ain't never done that... more than 10 or 50 times.

 

Yeah but most of us are not dealing with 10+ distros... It's a lot easier with 1 or 2 OSs

[V.T. Eric Layton]

Once I got the hang of tending to all the animals on my distro farm back then, I was OK. I actually haven't trashed an mbr since around 2006 sometime. Now watch... now that I've said that, I'll trash the one on my shop system when I try to install that FreeBSD I downloaded/burned the other night.

[Hedon James]

Once I got the hang of tending to all the animals on my distro farm back then, I was OK. I actually haven't trashed an mbr since around 2006 sometime. Now watch... now that I've said that, I'll trash the one on my shop system when I try to install that FreeBSD I downloaded/burned the other night.

 

oh, you have sooo jinxed yourself! might wanna bookmark this thread and have your favorite LiveCD on standby!

[réjean]

Trash my mbr? H3LL NO! Ain't never done that... more than 10 or 50 times.

 

Yeah but most of us are not dealing with 10+ distros... It's a lot easier with 1 or 2 OSs

Well only 6 to be precise with their own /home partition each plus a 500 Gb storage. I didn't care too much about the dozen or two .iso files I keep for playing in Virtual Box but it's the rest I was most concerned about ( photos from friends and relatives, bookmarks, etc.) I used to put them on a DVD every 6 months or so but with 2 Tb hds I thought I was ok until I realized that I should have them duplicated on each hard drive in case I have to format a whole drive. Boot Repair is definitely a software to keep in mind if something similar happens again, which it will.

[securitybreach]

Well I have a bunch of OSs and distros in vbox:

 

[réjean]

Once I got the hang of tending to all the animals on my distro farm back then, I was OK. I actually haven't trashed an mbr since around 2006 sometime. Now watch... now that I've said that, I'll trash the one on my shop system when I try to install that FreeBSD I downloaded/burned the other night.

 

oh, you have sooo jinxed yourself! might wanna bookmark this thread and have your favorite LiveCD on standby!

and remember about Boot Repair. I used to be able to repair my problems with http://www.supergrubdisk.org/ (never heard of Rescatux before but it looks cool) but this time it wouldn't work for me. Also before he passed away we ( or I should say me because he saved my butt so many times) had Bruno to come to the rescue ( not that you, Eric, Josh and many others are not doing your best. I really appreciate your help and dedication).

[réjean]

Well I have a bunch of OSs and distros in vbox:

 

 

Wow That's a lot too. Is there any way I can get Win 10 (for free) and, like you, just use it in Vbox when my friends and relatives decide to switch to it and mess up there machine, so I can help them. Like I said at the beginning of this thread or the other one I do have Win 7 on the 2nt hd but use it only to play a few games and never online so I don't really need Win 10 for myself.

[securitybreach]

Well you can still get the technical preview and if you have a Windows 7-8.1 license, you can get the upgrade for free.

[réjean]

Thanks! I do have the technical preview.

[Hedon James]

Well I have a bunch of OSs and distros in vbox:

 

 

I love your dark theme! Very easy to read, plus it looks cool! I also note your Mac OSX Mavericks VM. I've had a hard time installing that one, but not sure we can talk about it here. If we can't, can we PM? Just looking to compare notes and tips & tricks...if we can. I don't want to violate TOS here.

[securitybreach]

Well I an at work now but I'll hit you up when I get hone around 2200cst

[V.T. Eric Layton]

Well I have a bunch of OSs and distros in vbox:

 

 

Virtual doesn't count, you wuss techie.

[securitybreach]

I see no point in having multiple distros installed versus virtually running them. Heck most servers nowadays are virtual

 

If you have the power, why not use it?

[burninbush]

Yeah! Boot repair worked!

I don't know why it didn't this morning but this time it did. I'm replying from PCLinuxOS but I saw all the entries in the bootloader and I assume the MBR has been fixed completely. Thanks everyone!

I can tell you 2 things;

1. I have 2X 1tb hd with a 500 GB storage partition on each and I'll make sure my important stuff is in both.

2. I will unplugged the hd I use the most (sda) before I attempt to install Arch and install it on the other drive which as only Win XP which is broken and Win 7 which I use only for playing games once in a while.

about the syntax; I used 'sudo' only once as root after I had chrooted and it was kindda out of despair.

 

 

Great news!

 

Now that it's working again, this would be a good time to take copies of the MBR sector from both disks, and store them on a usbstick.

 

Ideal situation is to find some old but still good usbstick, maybe 512mb, and install onto it a copy of Puppy or Porteus. Test that it boots well, and store your mbr backups on it, along with whatever other important boot files [menu.lst, grub.cfg, etc]. Then put it away and you'll have a first response the next time your mbrs get trashed.

 

#dd if=/dev/sda of=tera1.mbr bs=512 count=1

#dd if=/dev/sdb of=tera2.mbr bs=512 count=1

 

and to restore just reverse the if and the of labels, for example

 

#dd of=/dev/sda if=tera1.mbr bs=512 count=1

 

and if you later change anything in the partition layouts, then do a new mbr capture.

Edited July 22, 2015 by burninbush

[V.T. Eric Layton]

I see no point in having multiple distros installed versus virtually running them. Heck most servers nowadays are virtual

 

If you have the power, why not use it?

 

Feel the force, Luke!