| 1 |
Hi Mick |
| 2 |
|
| 3 |
Mick wrote: |
| 4 |
|
| 5 |
> On Sunday 31 Jul 2016 22:38:22 Jörg Schaible wrote: |
| 6 |
>> Hi Mick, |
| 7 |
>> |
| 8 |
>> Mick wrote: |
| 9 |
>> > On Sunday 31 Jul 2016 19:14:45 Jörg Schaible wrote: |
| 10 |
>> >> Hi Daniel, |
| 11 |
>> >> |
| 12 |
>> >> thanks for your response. |
| 13 |
>> >> |
| 14 |
>> >> Daniel Frey wrote: |
| 15 |
>> >> |
| 16 |
>> >> [snip] |
| 17 |
>> >> |
| 18 |
>> >> > I can only think of two reasons, the kernel on the livecd doesn't |
| 19 |
>> >> > support GPT (which is unlikely) |
| 20 |
>> >> |
| 21 |
>> >> That would be really strange. However, how can I prove it? |
| 22 |
>> > |
| 23 |
>> > If after you boot your systemrescuecd you can list: |
| 24 |
>> > |
| 25 |
>> > /sys/firmware/efi |
| 26 |
>> > |
| 27 |
>> > you have booted into UEFI mode. If not, you have booted into legacy |
| 28 |
>> > BIOS mode. |
| 29 |
>> |
| 30 |
>> This machine has only plain old BIOS. The question is, why one kernel |
| 31 |
>> detects the 3TB partition and the the other one does not. How can I prove |
| 32 |
>> GPT support for the kernel itself. |
| 33 |
> |
| 34 |
> |
| 35 |
> I see. In this case have a look at /proc/config (it may be compressed) or |
| 36 |
> depending on your version of sysrescuecd and kernel choice, have a look |
| 37 |
> here: |
| 38 |
> |
| 39 |
> https://sourceforge.net/p/systemrescuecd/code/ci/master/tree/ |
| 40 |
> |
| 41 |
> then compare your configuration to theirs. The kernel module for GPT is |
| 42 |
> 'CONFIG_EFI_PARTITION' and it must be built in, rather than as a separate |
| 43 |
> module. |
| 44 |
|
| 45 |
Now it's getting weird. |
| 46 |
|
| 47 |
My normal kernel (4.4.6) does not have that flag set. Nevertheless it |
| 48 |
detects the partition. The two kernels (both 4.4.12) of systemrescue have |
| 49 |
that flag. I've tested another machine with kernel that also has the flag |
| 50 |
and it does not detect this partition also. |
| 51 |
|
| 52 |
However, I have another 6TB USB drive and that one has one big partition |
| 53 |
that is detected by both machines. The funny thing is, it reports to have |
| 54 |
only a MBR with one partition of 6TB (same output on both kernels): |
| 55 |
|
| 56 |
================== %< ====================== |
| 57 |
~ # parted /dev/sde print |
| 58 |
Model: WD My Book 1230 (scsi) |
| 59 |
Disk /dev/sde: 6001GB |
| 60 |
Sector size (logical/physical): 4096B/4096B |
| 61 |
Partition Table: msdos |
| 62 |
Disk Flags: |
| 63 |
|
| 64 |
Number Start End Size Type File system Flags |
| 65 |
1 8389kB 6001GB 6001GB primary ext4 |
| 66 |
|
| 67 |
~ # gdisk /dev/sde |
| 68 |
GPT fdisk (gdisk) version 1.0.1 |
| 69 |
|
| 70 |
Partition table scan: |
| 71 |
MBR: MBR only |
| 72 |
BSD: not present |
| 73 |
APM: not present |
| 74 |
GPT: not present |
| 75 |
|
| 76 |
|
| 77 |
*************************************************************** |
| 78 |
Found invalid GPT and valid MBR; converting MBR to GPT format |
| 79 |
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by |
| 80 |
typing 'q' if you don't want to convert your MBR partitions |
| 81 |
to GPT format! |
| 82 |
*************************************************************** |
| 83 |
|
| 84 |
|
| 85 |
Command (? for help): q |
| 86 |
================== %< ====================== |
| 87 |
|
| 88 |
AFAICS this partition works fine, fsck does not report any problem. The |
| 89 |
funny thing is, it should not have been possible, because of the 2GB limit |
| 90 |
of MBR. |
| 91 |
|
| 92 |
??? |
| 93 |
|
| 94 |
- Jörg |
Archives