Announcement

**Wheel Inventor** · Jan 31, 2015, 11:52 AM

Don't worry be hapy

Should I be worried about this?

I'm not - at here:

~$ sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000acd20

Device Boot Start End Blocks Id System
/dev/sda1 * 63 512007614 256003776 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 512007615 1024015229 256003807+ 83 Linux
Partition 2 does not start on physical sector boundary.
/dev/sda3 1024015230 1536022844 256003807+ 83 Linux
Partition 3 does not start on physical sector boundary.
/dev/sda4 1536022906 1953520064 208748579+ 5 Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5 1536022908 1556505719 10241406 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 1556505783 1576988594 10241406 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 1576988658 1597471469 10241406 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 1597471533 1617954344 10241406 83 Linux
Partition 8 does not start on physical sector boundary.
/dev/sda9 1617954408 1638437219 10241406 83 Linux
/dev/sda10 1638437283 1658920094 10241406 83 Linux
Partition 10 does not start on physical sector boundary.
/dev/sda11 1658920158 1679402969 10241406 83 Linux
Partition 11 does not start on physical sector boundary.
/dev/sda12 1679403033 1699885844 10241406 83 Linux
Partition 12 does not start on physical sector boundary.
/dev/sda13 1699885908 1703982419 2048256 82 Linux swap / Solaris
Partition 13 does not start on physical sector boundary.
/dev/sda14 1703982483 1953520064 124768791 83 Linux
Partition 14 does not start on physical sector boundary.

AskUbuntu - Partition does not start on physical sector boundary?: http://askubuntu.com/questions/15699...ector-boundary

After the format, I find my user permissions are not sufficient to use it. What do I need to do to make this work?

How are you trying to use it ?
From the fstab ?: https://help.ubuntu.com/community/Fstab

**oshunluvr** · Jan 31, 2015, 03:56 PM

If your drive performance isn't suffering, ignore the error. If it seems slow, you have to reformat to fix it - maybe a shrink and move will fix it. Gparted should be able to move the partition start to the 1MB boundry.

You didn't include all the drive data from fdisk, but if it's an Advanced Format drive like Wheel Inventor's is; basically, you need to start the first partition at at byte divisible by 4096 - any sector number divisible by 8: 64 is good, 63 isn't.

If it's an older format drive, 2048 is a good first sector using fdisk (MBR format). If you use gdisk instead (GPT format) all sectors will align when you create them.

If all this confuses you, post the full output of fdisk -l.

**oshunluvr** · Jan 31, 2015, 03:58 PM

@Wheel Inventor: That looks like a GPT formatted drive, thus the fdisk output is erroneous. What's the result of gdisk -l

**Jeremy_Ray** · Jan 31, 2015, 04:37 PM

Here's the full output of fdisk -l -

Code:

Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000cbee4

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    83714047    41856000   83  Linux
/dev/sda2        83716094   117229567    16756737    5  Extended
/dev/sda5        83716096   117229567    16756736   82  Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00017ea0

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63  1953520064   976760001   83  Linux

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00082ee7

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1           16065  1953520064   976752000   83  Linux
Partition 1 does not start on physical sector boundary.

I'm not sure how, but I've been using the 2nd hard drive without an entry in fstab. I believe I asked for help here years ago when I built this computer, and we set it up another way. But, here is fstab as it currently stands (I've attempted to add both the 2nd and 3rd hard drives) -

Code:

# /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>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=5943b45e-6969-4340-8ba9-af2fa8799a48 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=aec62e39-a897-43fc-930a-20da0c3b6b01 none            swap    sw              0       0

#UUID=b0ef4b51-acaf-4b46-a13a-efe53957dd40 /media          ext4    errors=remount-ro 0       2

UUID=c02bdb95-bfb3-4846-a499-e016ce1009dd /media          ext4    errors=remount-ro 0       2

b0ef4b51-acaf-4b46-a13a-efe53957dd40 is the 2nd hard drive, which worked before without the fstab entry. c02bdb95-bfb3-4846-a499-e016ce1009dd is the 3rd hard drive.

I got strange results when I added the entry for the 2nd hard drive. If I went into Dolphin and clicked on the entry for the third hard drive, it would take me to the contents of the 2nd hard drive.

With the entry for the 2nd hard drive commented out, I can access both hard drives through Dolphin, but there is a folder for the 2nd hard drive on the third hard drive, which wasn't there before and shouldn't be there. I.E., if I click on the entry for the 3rd hard drive, there are three folders - lost+found, documents (I created this one as a test), and jeremy (inside of which is an entry for the 2nd hard drive). I didn't create the latter, it appeared on its own after I commented out the line for the 2nd hard drive in fstab and rebooted the computer.

I'm sure there is a better way to do this but everything is functional. I haven't put any big files on hard drive 3 to see how fast it is.

**oshunluvr** · Jan 31, 2015, 04:48 PM

sudo blkid -o list -c /dev/null will show all the UUID's you have if you need to check them.

You can't mount two filesystems to the same mount location in fstab like that. You have to install and use mhddfs to do that.

You don't need to put files on it: hdparm will give results;

sudo hdparm -tT /dev/sdc

Do it for all the drives and compare.

Back to your original issue: your sdc drive is indeed an "Advanced Format" drive as you can see by these lines:

Code:

Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

So either ignore the error or use Gparted to re-align the partition so the error goes away.

**Jeremy_Ray** · Jan 31, 2015, 06:37 PM

Originally posted by oshunluvr View Post

sudo blkid -o list -c /dev/null will show all the UUID's you have if you need to check them.

You can't mount two filesystems to the same mount location in fstab like that. You have to install and use mhddfs to do that.

You mean, put them both in /media? What should I have done instead? / only?

I ran hdparm on all the drives -

Code:

/dev/sdc:
 Timing cached reads:   9216 MB in  2.00 seconds = 4611.31 MB/sec
 Timing buffered disk reads: 614 MB in  3.00 seconds = 204.53 MB/sec
jeremy@jeremy-GA-990FXA-UD3:~$ sudo hdparm -tT /dev/sdb

/dev/sdb:
 Timing cached reads:   8846 MB in  2.00 seconds = 4426.21 MB/sec
 Timing buffered disk reads: 328 MB in  3.00 seconds = 109.32 MB/sec
jeremy@jeremy-GA-990FXA-UD3:~$ sudo hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   8886 MB in  2.00 seconds = 4445.87 MB/sec
 Timing buffered disk reads: 592 MB in  3.00 seconds = 197.32 MB/sec

As far as I can tell, sdc is doing good. I'm surprised sda isn't doing better given it's a solid state drive and the others are hard disks.

**vinnywright** · Jan 31, 2015, 10:04 PM

Originally posted by Jeremy_Ray View Post

You mean, put them both in /media? What should I have done instead? / only?

you half to have a specific mount point for each drive ,,,,,,,,,,,,,,,,, like

Code:

#UUID=b0ef4b51-acaf-4b46-a13a-efe53957dd40 /media/disk1          ext4    errors=remount-ro 0       2

UUID=c02bdb95-bfb3-4846-a499-e016ce1009dd /media/disk2          ext4    errors=remount-ro 0       2

and those directories (disk1,disk2)((the name can be whatever you want))must already exist in /media or /mnt or anywhere elce you like ,,,,,,,I use /mnt as was the tradition in the old day's

VINNY

**oshunluvr** · Jan 31, 2015, 11:26 PM

Also, if you mount ANYTHING to /media expect some trouble. udev uses /media to mount removable stuff like usb thumb drives. It will create a subfolder of your user name than another subfolder of the device name, label, or UUID.

When you boot, /media is empty (or should be). Then you insert a thumb drive and /media will look like:

Code:

/media
  /jeremy
    /SanDisk

So udev would make those directories on whatever you have mounted there or fail. Not a good idea to use a system directory to mount stuff. That's what /mnt is for and I suggest using subfolders of your own creation there and nowhere else or make a unique location not already used by the system, like /data or whatever.

If you want sdb and sdc mounted together, install mhddfs. Then make two mounting locations:

sudo mkdir /mnt/sdb
sudo mkdir /mnt/sdc

Then make a new place to mount them together:

sudo mkdir /mnt/media

Mount the drives there in /etc/fstab:

Code:

UUID=b0ef4b51-acaf-4b46-a13a-efe53957dd40 /mnt/sdb          ext4    errors=remount-ro 0       2
UUID=c02bdb95-bfb3-4846-a499-e016ce1009dd /mnt/sdc          ext4    errors=remount-ro 0       2
mhddfs#/mnt/sdb,/mnt/sdc /mnt/media fuse defaults,allow_other 0 0

Then they will mount together. I've never tried this so if you do, let us know how it works out.

**Wheel Inventor** · Feb 01, 2015, 01:28 AM

@Wheel Inventor: That looks like a GPT formatted drive,...

No - mbr.

:~$ gdisk -lGPT fdisk (gdisk) version 0.8.8

Problem opening -l for reading! Error is 2.
The specified file does not exist!

:~$ sudo blkid
..
/dev/sda1: LABEL="AudioVideo" UUID="db112040-6415-4614-b353-624d5eb9bd45" TYPE="ext4"
/dev/sda2: LABEL="Images" UUID="6374569b-646c-45c7-9e09-35c72e20e10d" TYPE="ext4"
/dev/sda3: LABEL="Building" UUID="bc02b2ec-13fb-448b-83b5-d497010b5f7c" TYPE="ext4"
..

**oshunluvr** · Feb 01, 2015, 07:39 AM

Yeah - I went back and looked closer - missed the "Extended" partition the first time.

**Jeremy_Ray** · Feb 01, 2015, 09:01 AM

I created new directories in mnt and editted my fstab. Everything appears to be working fine. I had to chmod 777 the third hard drive to use it. I know that's a bad thing. I tried 770 but apparently the file doesn't know I'm a user. What is the right way to set the permissions?

**oshunluvr** · Feb 01, 2015, 09:19 AM

What are the permissions of the stuff in it?

The "normal" way it should mount is with ownership=root:root and permission drwxr_xr_x. This allows everyone to look in. Then the folders within should be owned by you and thus wouldn't need 777.

If you're not the owner of everything on the drive, you can make it so:

cd /mnt/sdc
sudo chown 1000:1000 -R *

**oshunluvr** · Feb 01, 2015, 09:22 AM

@Wheel: BTW - cool blkid command is;

sudo blkid -o list -c /dev/null

This clears any cache so you always get the most current UUID's and puts the info in a neat little list. I just put the above command in my aliases as "blkid" so I only have to type 5 letters...

**Jeremy_Ray** · Feb 01, 2015, 11:38 AM

Originally posted by oshunluvr View Post

What are the permissions of the stuff in it?

The "normal" way it should mount is with ownership=root:root and permission drwxr_xr_x. This allows everyone to look in. Then the folders within should be owned by you and thus wouldn't need 777.

If you're not the owner of everything on the drive, you can make it so:

cd /mnt/sdc
sudo chown 1000:1000 -R *

Doesn't the drive itself have permissions? I wasn't able to create or delete files on it before.

Announcement

Setting up third hard drive

Setting up third hard drive

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment