I just formatted a 3TB linux partition and I've something that I would like to ask...
In a previous formatting cycle I was able to achieve a harddisk with the following layout and /dev/sdb1 via fdisk -l
Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 267350 2147483647+ ee GPT
Today with parted I've created a disk of 3.0TB via "parted /dev/sdb" and which is formatted ext3 and is mounted via /dev/sdb1 on /<whatever>
Using fdisk -l now I see
Disk label type: GPT
Disk Identifier: <something>
Partition start, partition end, size, Type, name
That's it !
I formatted /dev/sdb1
Question: What is the reason that I don't see /dev/sdb1 while using fdisk -l ?
In a previous formatting cycle I was able to achieve a harddisk with the following layout and /dev/sdb1 via fdisk -l
Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 267350 2147483647+ ee GPT
Today with parted I've created a disk of 3.0TB via "parted /dev/sdb" and which is formatted ext3 and is mounted via /dev/sdb1 on /<whatever>
Using fdisk -l now I see
Disk label type: GPT
Disk Identifier: <something>
Partition start, partition end, size, Type, name
That's it !
I formatted /dev/sdb1
Question: What is the reason that I don't see /dev/sdb1 while using fdisk -l ?
In Hardware
Share this post:
Responses (2)
-
Accepted Answer
I tried looking at this yesterday. Some references say later versions of fdisk support GPT, but others say just use parted. I couldn't get to any real conclusion and none of my disks are > 2TB so they are all MBR. I think ClearOS 6x is in the odd position of not being able to install to a GPT disk but it can read one. ClearOS 7.x can install to GPT as well. -
Accepted Answer
Ok...
I seem to see a difference in output..
Parted was done in Clearos 7 while my history was read from a running Clearos 6 server. I copied the content anyway and while rebooting the main server (on ClearOs 6), the disk showed its partition as /dev/sdb1.....
A bit lost what is happening (and would like to know), but it works on the old fstab entries. So problem does not occure in ClearOS
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »