partuuid issue

[Fintan]

This is my fault. I tried to resize a partition with the KDE partition manager and it was interrupted/stopped by a power break.

Anyway at boot I got a Job started on /dev/xxxxxxx. I looked that up with my phone and found a partial solution involving: sudo -H nano /etc/fstab where I proceeded to comment out the /dev/ wich was causing the hangup. It turned out to be my /Data partition which I was trying to resize.

Now I can boot back into Kubuntu.

Here is my blkid:

fintan@fintan-HP-Pavilion-dv6-Notebook-PC:~$ sudo blkid
[sudo] password for fintan:
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/sda1: UUID="6e56d231-d990-45dc-866b-98440349083a" TYPE="ext4" PARTUUID="00061549-01"
/dev/sda2: UUID="171802f7-58ce-42ae-a46b-f2838af70a77" TYPE="ext4" PARTUUID="00061549-02"
/dev/sda3: PARTUUID="00061549-03"
/dev/sda5: LABEL="Media" UUID="cc363feb-3783-4195-8d90-faee31f64e98" TYPE="ext4" PARTUUID="00061549-05"
/dev/sda6: UUID="5626e36a-e819-46ea-839f-7e8043f66954" TYPE="swap" PARTUUID="00061549-06"
/dev/sda7: UUID="c919460a-b081-4c81-82eb-aa3275dc7ace" TYPE="ext4" PARTUUID="00061549-07"
/dev/sda8: LABEL="Media2" UUID="405c7e1d-95e7-4745-98f7-49b46339456d" TYPE="ext3" PARTUUID="00061549-08"
fintan@fintan-HP-Pavilion-dv6-Notebook-PC:~$

/dev/sda3: PARTUUID="00061549-03" this is the partition I need back.

How can I generate a new UUID? And is the data gone? Irreversibly?

Any help really greatly appreciated!

[oshunluvr]

Likely it's gone if this occurred during a resize operation. You might be able to recover the partition with testdisk but at least some of your data is gone.

I know hindsight is 20/20 but you should never ever mess with a partition unless you have a full backup of everything on it.

[Snowhog]

You can try changing the fstab entry from using the UUID to the device: /dev/sda3

[Fintan]

Thanks guys. I knew it was risky. My fault all the way.

Do I need a live usb for testdisk?

You can try changing the fstab entry from using the UUID to the device: /dev/sda3

Have not done that for ages. Will try that.

Cheers
Fred

[oshunluvr]

testdisk can run from your install. Try what Snowhog suggested first, then run testdisk and see if it detects the partition.

[Fintan]

Ok.

My new fstab: /Data in red

# /etc/fstab: static file system information.
#
# Use 'blkid' 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>
# / was on /dev/sda1 during installation
UUID=6e56d231-d990-45dc-866b-98440349083a / ext4 errors=remount-ro 0 1
/dev/sda3 /Data ext4 defaults 0 2
# UUID=870450d7-d898-441c-9f0f-2084807b6fd2 /Data ext4 defaults 0 2
# /Media was on /dev/sda5 during installation
UUID=cc363feb-3783-4195-8d90-faee31f64e98 /Media ext4 defaults 0 2
# /Media2 was on /dev/sda8 during installation
UUID=405c7e1d-95e7-4745-98f7-49b46339456d /Media2 ext3 defaults 0 2
# /home was on /dev/sda2 during installation
UUID=171802f7-58ce-42ae-a46b-f2838af70a77 /home ext4 defaults 0 2
# swap was on /dev/sda6 during installation
UUID=5626e36a-e819-46ea-839f-7e8043f66954 none swap sw 0 0

[Fintan]

Well guys. I had to reinstall and all my major data is fubared. Now I have a problem with permissions on the partitions I set during install.
I tried this:
sudo chown -R $USER:$USER /dev/sda9

But nada.

Any ideas.

[oshunluvr]

Devices don't have permissions. File systems do. You can either set permissions in /etc/fstab for some file systems or modify the mount point with chown. For example, if /dev/sda9 in mounted at /Media2 you would do:

sudo chown -R $USER:$USER /Media2

or more technically correct:

sudo chown -R $(id -u):$(id -g) /Media2

[jlittle]

(I know I'm a bit late with this, but someone one day might find this thread.)

You don't have to use UUIDs in /etc/fstab. I much prefer labels (LABEL=whatever). To get things going, the device file name for the partition will do, f. ex. /dev/sda9. UUIDs are used by default because those names can change if the hardware changes, typically because a device has been added or removed, or cables swapped around. The device file name was the original Unix usage.

[Fintan]

(I know I'm a bit late with this, but someone one day might find this thread.)

You don't have to use UUIDs in /etc/fstab. I much prefer labels (LABEL=whatever). To get things going, the device file name for the partition will do, f. ex. /dev/sda9. UUIDs are used by default because those names can change if the hardware changes, typically because a device has been added or removed, or cables swapped around. The device file name was the original Unix usage.

Thank You! But yeah too late.

So, you mean this as fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
/ was on /dev/sda1 during installation
#UUID=6e56d231-d990-45dc-866b-98440349083a / ext4 errors=remount-ro 0 1
/dev/sda3 /Data ext4 defaults 0 2
# UUID=870450d7-d898-441c-9f0f-2084807b6fd2 /Data ext4 defaults 0 2
/dev/sda5 during installation
#UUID=cc363feb-3783-4195-8d90-faee31f64e98 /Media ext4 defaults 0 2
/dev/sda8 during installation
#UUID=405c7e1d-95e7-4745-98f7-49b46339456d /Media2 ext3 defaults 0 2
/home was on /dev/sda2 during installation
#UUID=171802f7-58ce-42ae-a46b-f2838af70a77 /home ext4 defaults 0 2
/dev/sda6 during installation
#UUID=5626e36a-e819-46ea-839f-7e8043f66954 none swap sw 0 0

??