Results 1 to 10 of 10
Hi everybody,
After crash my grub by taping on windows recovery, i can not mount /home.
My problem is than my UUID is not valid anymore. In fact during the ...
- 07-27-2011 #1Just Joined!
- Join Date
- Sep 2010
- Location
- Europe
- Posts
- 6
UUID and /home
Hi everybody,
After crash my grub by taping on windows recovery, i can not mount /home.
My problem is than my UUID is not valid anymore. In fact during the installation i did'nt create a real partition for my /home.

Can i find the good UUID not by (/dev/disk/......) or recover my /home datas?
Thanks in advance.
- 07-27-2011 #2Not understanding your statement here. Did you do a full Windows recovery which wiped Ubuntu and Grub. If so. Ubuntu is gone.After crash my grub by taping on windows recovery
In Ubuntu terminal you can find UUID byCan i find the good UUID not by (/dev/disk/......)
Further reference is atCode:sudo blkid
https://help.ubuntu.com/community/UsingUUIDLinux Registered User # 475019
Lead,Follow, or get the heck out of the way
AntiX,Puppy,Ubuntu,Windows 7=(cuz of scooters)
Open CourseWare for Linux Geeks
- 07-28-2011 #3Just Joined!
- Join Date
- Sep 2010
- Location
- Europe
- Posts
- 6
Thanks for the quick reply.
My / and swap partition is OK, i can boot and use it. It's just about my /home.
I Did not create a /dev/sdaXX for, so my /home is somewhere on the / partition. I'm just looking for the good UUID to mount /home.
- 07-28-2011 #4
If you didnt create a partition for /home, then you dont need to mount it. So you also dont need a uuid.
You say, your / is ok. Are you sure you didnt accidentally delete /home?
Other that that, can you post the output of
Code:fdisk -l
You must always face the curtain with a bow.
- 07-28-2011 #5Just Joined!
- Join Date
- Sep 2010
- Location
- Europe
- Posts
- 6
- 07-28-2011 #6Again: If you didnt create a partition, then there is no uuidMy problem is than my UUID is not valid anymore. In fact during the installation i did'nt create a real partition for my /home.
To clarify that, can you paste the output of
Code:fdisk -l and cat /etc/fstab
You must always face the curtain with a bow.
- 07-28-2011 #7Just Joined!
- Join Date
- Sep 2010
- Location
- Europe
- Posts
- 6
fdisk -l and blkid
See below the requested commands
Code:fdisk -l /dev/sda1 1 1530 12289693+ 1c W95 FAT32 (LBA) /dev/sda2 * 1531 15255 110246062+ 7 HPFS/NTFS /dev/sda3 15256 17162 15317977+ 83 Linux /dev/sda4 17164 38913 174706844+ 5 Extended /dev/sda5 19933 38913 152464882+ 7 HPFS/NTFS
Code:blkid /dev/sda1: LABEL="RECOVERY" UUID="3C98-AC5D" TYPE="vfat" /dev/sda2: LABEL="VistaOS" UUID="44E2B7CFE2B7C388" TYPE="ntfs" /dev/sda3: UUID="25bd86b1-1f80-47f4-8838-96e5c5549842" TYPE="ext4" /dev/sda5: LABEL="DATA" UUID="76F001CA34454B1F" TYPE="ntfs"
- 07-28-2011 #8
Ok, there is only one linux partition, presumably containing the system.
What do these say?
Code:cat /etc/fstab ls -la /home
You must always face the curtain with a bow.
- 07-28-2011 #9Just Joined!
- Join Date
- Sep 2010
- Location
- Europe
- Posts
- 6
Code:ls -la /home/ total 8 drwxr-xr-x 2 root root 4096 2010-08-14 04:34 . drwxr-xr-x 22 root root 4096 2011-05-31 23:41 .. root@patbook:~# more /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda4 during installation UUID=25bd86b1-1f80-47f4-8838-96e5c5549842 / ext4 errors=remount -ro 0 1 # /home was on /dev/sda7 during installation UUID=81b71cb3-cd64-458d-9483-dad93620a8ad /home ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=97bde84f-1cc1-4b4f-bf4d-d6e7b0ab60e0 none swap sw 0 0
- 07-28-2011 #10Linux Guru
- Join Date
- Oct 2007
- Location
- Tucson AZ
- Posts
- 1,946
Your fstab output shows there was a /home partition on sda7 and a swap partition on sda6 at the time of installation. Your fdisk output shows neither of these partitions. If you had created a user patinio during installation your should have seen that in the output of the ls -la /home/ command. Without knowing what happened prior to getting this problem it would be difficult to diagnose.


Reply With Quote
