[solved] biting off more than I can chew -FDISK

[Snowhog]

Re: biting off more than I can chew -FDISK

Okay. Before I proceed, are you intending to dual-boot from this other HD? I ask because you have it partitioned with root ( / ), home ( /home ), temp ( /tmp), and a swap partitions.

[converted tux]

Re: biting off more than I can chew -FDISK

Not just yet, I wanted to add more space to the pc for kubuntu. The multi boot will be another pc.

which partitions should I get rid of for now, in order to just have more file space?

[oshunluvr]

Re: biting off more than I can chew -FDISK

Wow - your using 1.25tb just for linux?

OK - well the 250gb drive has more than enough room for kubuntu. You could use /dev/sda1 as /home and use /dev/sdb6 as space for a backups or leave /dev/sdb6 as home and store media files on /dev/sda1. You can keep both swaps if you want and set them at equal priorities ( pri=1 as an option in fstab).

[Snowhog]

Re: biting off more than I can chew -FDISK

Not just yet, I wanted to add more space to the pc for kubuntu. The multi boot will be another pc.

which partitions should I get rid of for now, in order to just have more file space?

Just use GParted to reformat the 2nd HD. If you only want more user storage space, then remove/delete all the partitions. Then create a single partition and format it as ext3. Done. This will establish a new UUID for the new drive partition, so when you are finished, you will need to rerun sudo blkid to see what the UUID is for drives partition. We can proceed after that.

[converted tux]

Re: biting off more than I can chew -FDISK

Ok so I reformatted again and now have this.

bryan@Photoframe:~$ sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x21ccb32b

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *      1   120121  964871901  83 Linux
/dev/sda2     120122   121601  11888100  5 Extended
/dev/sda5     120122   121601  11888068+ 82 Linux swap / Solaris

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x333c333b

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1        1    30401  244196001  83 Linux
bryan@Photoframe:~$

And the sudo blkid showed

bryan@Photoframe:~$ sudo blkid | grep sdb
/dev/sdb1: UUID="1c94956f-dc9f-4b5d-86d7-84f0da250c41" SEC_TYPE="ext2" TYPE="ext3"
bryan@Photoframe:~$

[Snowhog]

Re: biting off more than I can chew -FDISK

Okay. First, you need to create a mount-point for this HD. Open a console and type:

sudo mkdir /media/data

Then, edit your /etc/fstab file (as root) and add:

# /dev/sdb1
UUID=1c94956f-dc9f-4b5d-86d7-84f0da250c41 /data ext3 defaults 0 2

Then, in a console, type:

sudo mount -a

Launch Dolphin and you should see the new partiton and be able to read/write to it.

[converted tux]

Re: biting off more than I can chew -FDISK

Ok, I tried what you said and fstab now looks like this.

# /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  defaults    0    0
# / was on /dev/sda1 during installation
UUID=6638e0e3-c43e-4c92-8554-28c6a208730e /        ext4  errors=remount-ro 0    1
# swap was on /dev/sda5 during installation
UUID=391b5b1b-6ebd-41ff-850d-b99ac7c97dc7 none      swap  sw       0    0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
# /dev/sdb1
UUID=1c94956f-dc9f-4b5d-86d7-84f0da250c41 /data      ext3  defaults    0    2

I also ran a fdisk listing and tried again to mount-a this was the result

bryan@Photoframe:~$ sudo fdisk -l
[sudo] password for bryan:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x21ccb32b

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *      1   120121  964871901  83 Linux
/dev/sda2     120122   121601  11888100  5 Extended
/dev/sda5     120122   121601  11888068+ 82 Linux swap / Solaris

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x333c333b

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1        1    30401  244196001  83 Linux

bryan@Photoframe:~$ sudo mount -a
[mntent]: warning: no final newline at the end of /etc/fstab
mount: mount point /data does not exist
bryan@Photoframe:~$

So while I am getting closer I am still not quite there. Maybe I am missing a decimal point somewhere?

[Snowhog]

Re: biting off more than I can chew -FDISK

When you added the new entry to /etc/fstab, you didn't hit return. Re-edit the file and hit return at the end of the added line.

[converted tux]

Re: biting off more than I can chew -FDISK

So I tried to re-edit the fstab and this is what it reads now.

# /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  defaults    0    0
# / was on /dev/sda1 during installation
UUID=6638e0e3-c43e-4c92-8554-28c6a208730e /        ext4  errors=remount-ro 0    1
# swap was on /dev/sda5 during installation
UUID=391b5b1b-6ebd-41ff-850d-b99ac7c97dc7 none      swap  sw       0    0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
# /dev/sdb1
UUID=1c94956f-dc9f-4b5d-86d7-84f0da250c41 /media/data      ext3  defaults    0    2

and fdisk shows this

bryan@Photoframe:~$ sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x21ccb32b

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *      1   120121  964871901  83 Linux
/dev/sda2     120122   121601  11888100  5 Extended
/dev/sda5     120122   121601  11888068+ 82 Linux swap / Solaris

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x333c333b

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1        1    30401  244196001  83 Linux
bryan@Photoframe:~$

and I ran that blkid grep thing again for both sda and sdb this is what came out.

bryan@Photoframe:~$ sudo blkid | grep sda
/dev/sda1: UUID="6638e0e3-c43e-4c92-8554-28c6a208730e" TYPE="ext4"
/dev/sda5: UUID="391b5b1b-6ebd-41ff-850d-b99ac7c97dc7" TYPE="swap"
bryan@Photoframe:~$ sudo blkid |grep sdb
/dev/sdb1: UUID="1c94956f-dc9f-4b5d-86d7-84f0da250c41" TYPE="ext3"
bryan@Photoframe:~$

Sorry for bugging you guys but I just don't get where it is going wrong, and I realize now that I should have made a backup copy of the fstab file but I failed to do so.
Again thank so much for the help you have provided so far.

oh did not mention it, but I can see the drive in dolphin, but when I try to drag and drop a copy of a pic to it I get access denied.

[Snowhog]

Re: biting off more than I can chew -FDISK

...and I realize now that I should have made a backup copy of the fstab file but I failed to do so.

But you did - in a way - when you posted what it was before we began this 'journey.':

# /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 defaults 0 0
# / was on /dev/sda1 during installation
UUID=6638e0e3-c43e-4c92-8554-28c6a208730e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=391b5b1b-6ebd-41ff-850d-b99ac7c97dc7 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

[Snowhog]

Re: biting off more than I can chew -FDISK

Edit the /etc/fstab file, and replace defaults with auto,users,rw,relatime so that the line looks like:

UUID=1c94956f-dc9f-4b5d-86d7-84f0da250c41 /media/data ext3 auto,users,rw,relatime 0 2

[vinnywright]

Re: biting off more than I can chew -FDISK

and dont forget to place your curser at the end of the file and hit enter once or twice to make a proper end of file after you edit it so you dont get that error agin.

bryan@Photoframe:~$ sudo mount -a
[mntent]: warning: no final newline at the end of /etc/fstab
mount: mount point /data does not exist
bryan@Photoframe:~$

and you did make the mount point rite?

/media/data ....?

VINNY

[converted tux]

Re: biting off more than I can chew -FDISK

And once more into the forge.... here is what I did and maybe it has something to do with the way I am doing this but I enter konsole and

bryan@Photoframe:~$ sudo kate
Error: "/var/tmp/kdecache-bryan" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-bryan" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-bryan" is owned by uid 1000 instead of uid 0.
QThreadStorage: Thread 0x96d1c0 exited after QThreadStorage 2147483636 destroyed

This if it isn't clear as mud, it is where I called kate and it opened in another window and allowed me to edit fstab... maybe there is another way to do this but I don't know it yet. Once edited it looks like this.

# /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  defaults    0    0
# / was on /dev/sda1 during installation
UUID=6638e0e3-c43e-4c92-8554-28c6a208730e /        ext4  errors=remount-ro 0    1
# swap was on /dev/sda5 during installation
UUID=391b5b1b-6ebd-41ff-850d-b99ac7c97dc7 none      swap  sw       0    0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
# /dev/sdb1
UUID=1c94956f-dc9f-4b5d-86d7-84f0da250c41 /media/data      ext3  auto,users,rw,relatime    0    2

then I went ahead and tried to mount the disk again typoed it, corrected and ran fdisk and that blkid thing again

bryan@Photoframe:~$ sudo mount-a
sudo: mount-a: command not found
bryan@Photoframe:~$ sudo mount -a

bryan@Photoframe:~$ sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x21ccb32b

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *      1   120121  964871901  83 Linux
/dev/sda2     120122   121601  11888100  5 Extended
/dev/sda5     120122   121601  11888068+ 82 Linux swap / Solaris

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x333c333b

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1        1    30401  244196001  83 Linux


bryan@Photoframe:~$ sudo blkid | grep sda
/dev/sda1: UUID="6638e0e3-c43e-4c92-8554-28c6a208730e" TYPE="ext4"
/dev/sda5: UUID="391b5b1b-6ebd-41ff-850d-b99ac7c97dc7" TYPE="swap"
bryan@Photoframe:~$ sudo blkid | grep sdb
/dev/sdb1: UUID="1c94956f-dc9f-4b5d-86d7-84f0da250c41" TYPE="ext3"
bryan@Photoframe:~$

So now I went to check it in dolphin and it shows the drive but the properties show it having ownership as root and group as root, still cant drop a pic into it without permission denied.

Vinny If the mount point is not changed through the ftstab then no but if it is then I have tried.

[Snowhog]

Re: biting off more than I can chew -FDISK

bryan@Photoframe:~$ sudo kate

NEVER launch a GUI application from the CLI (console) using sudo - NEVER! This is the fastest way to potentially screw up your system.

That said, at least you were editing a file within the root owned area of your OS, and not in your users /home directory.

Quote
bryan@Photoframe:~$ sudo mount -a
[mntent]: warning: no final newline at the end of /etc/fstab
mount: mount point /data does not exist <<<!!
bryan@Photoframe:~$

You didn't follow my instructions. You have to create the mount point. Open a console and type:

sudo mkdir /media/data

Then remount:

sudo mount -a

Then open Dolphin and check it out.

[oshunluvr]

Re: biting off more than I can chew -FDISK

Ok - sorry I've been absent.

You're trying to mount the /dev/sdb1 as a user accessible directory to store photos...right?

I suspect if you do

ls -l /media

you'll see something like

dr-xr-xr-x 8 root root 2048 1999-09-15 18:41 data

so then type

sudo chown -R bryan:bryan /media/data

substitute YOURUSERNAME:YOURPRIMARYGROUPNAME for bryan:bryan