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