| 1 |
On Wednesday, December 09, 2015 03:19:45 AM John Runyon wrote: |
| 2 |
> I recently received and installed a 3TB drive. Before formatting it, I |
| 3 |
> zeroed the first GiB (dd if=/dev/zero of=/dev/sdb bs=1M count=1024). |
| 4 |
> Then formatted with gdisk. |
| 5 |
> |
| 6 |
> Both gdisk and parted report the partition table correctly as containing a |
| 7 |
> ~1MB (empty) sdb1 and ~2.7TB sdb2 (with a protective MBR). However, on boot, |
| 8 |
> only one partition is recognized: the 1MB sdb1. And yet after running |
| 9 |
> partprobe, sdb2 will magically appear. |
| 10 |
> |
| 11 |
> I've managed to work around this for now with a /etc/local.d/ file that |
| 12 |
> just does "partprobe; mount /home" but I'd like to figure out the underlying |
| 13 |
> cause... Has anyone ever run into this before? |
| 14 |
> |
| 15 |
> # grep sdb /var/log/messages |
| 16 |
> Dec 9 01:38:49 precision kernel: [ 1.224703] sd 1:0:0:0: [sdb] |
| 17 |
> 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Dec 9 01:38:49 |
| 18 |
> precision kernel: [ 1.228246] sd 1:0:0:0: [sdb] 4096-byte physical |
| 19 |
> blocks Dec 9 01:38:49 precision kernel: [ 1.230017] sd 1:0:0:0: [sdb] |
| 20 |
> Write Protect is off Dec 9 01:38:49 precision kernel: [ 1.231765] sd |
| 21 |
> 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support |
| 22 |
> DPO or FUA Dec 9 01:38:49 precision kernel: [ 1.245054] sdb: sdb1 |
| 23 |
> Dec 9 01:38:49 precision kernel: [ 1.247172] sd 1:0:0:0: [sdb] Attached |
| 24 |
> SCSI disk Dec 9 01:38:57 precision kernel: [ 23.777108] sdb: sdb1 |
| 25 |
> Dec 9 01:38:58 precision kernel: [ 25.120921] EXT4-fs (sdb2): mounted |
| 26 |
> filesystem with ordered data mode. Opts: (null) |
| 27 |
> |
| 28 |
> # gdisk -l /dev/sdb |
| 29 |
> GPT fdisk (gdisk) version 1.0.1 |
| 30 |
> |
| 31 |
> Partition table scan: |
| 32 |
> MBR: protective |
| 33 |
> BSD: not present |
| 34 |
> APM: not present |
| 35 |
> GPT: present |
| 36 |
> |
| 37 |
> Found valid GPT with protective MBR; using GPT. |
| 38 |
> Disk /dev/sdb: 5860533168 sectors, 2.7 TiB |
| 39 |
> Logical sector size: 512 bytes |
| 40 |
> Disk identifier (GUID): 0A8A7DB1-45D0-44DD-AACB-1A4957077401 |
| 41 |
> Partition table holds up to 128 entries |
| 42 |
> First usable sector is 34, last usable sector is 5860533134 |
| 43 |
> Partitions will be aligned on 2048-sector boundaries |
| 44 |
> Total free space is 2014 sectors (1007.0 KiB) |
| 45 |
> |
| 46 |
> Number Start (sector) End (sector) Size Code Name |
| 47 |
> 1 2048 4095 1024.0 KiB 8300 Linux filesystem |
| 48 |
> 2 4096 5860533134 2.7 TiB 8300 Linux filesystem |
| 49 |
> |
| 50 |
> # parted -l |
| 51 |
> [...] |
| 52 |
> Model: ATA ST3000DM001-1ER1 (scsi) |
| 53 |
> Disk /dev/sdb: 3001GB |
| 54 |
> Sector size (logical/physical): 512B/4096B |
| 55 |
> Partition Table: gpt |
| 56 |
> Disk Flags: |
| 57 |
> |
| 58 |
> Number Start End Size File system Name Flags |
| 59 |
> 1 1049kB 2097kB 1049kB Linux filesystem |
| 60 |
> 2 2097kB 3001GB 3001GB ext4 Linux filesystem |
| 61 |
> [...] |
| 62 |
|
| 63 |
How old is the BIOS in your system? |
| 64 |
|
| 65 |
Older systems have issues recognizing disks larger than 2TB, Linux has a |
| 66 |
history of being able to ignore that. I am not sure how that works with boot- |
| 67 |
disks though. |
| 68 |
|
| 69 |
-- |
| 70 |
Joost |
Archives