Missing parttype in Linux lsblk

User discussion and information resource forum for BootIt Bare Metal.

Missing parttype in Linux lsblk

Postby rustleg » Sat Jan 02, 2016 4:42 am

I installed Linux MX-15 a couple of days ago and I had 2 problems.

First was that it decided to ignore the partition I had chosen for installation, which was an ext4 partition I had previously used for another Linux (Mint). I didn't bother to wipe it as I assumed the installer would ask if I wanted to format it (but it didn't ask) or else just go ahead, which it did. But it didn't install the system in that partition but in the "free space following". It overwrote another hidden Linux partition (I didn't limit primaries) but that wasn't a big issue as I had an image. Obviously this is a problem with the installer rather than BIBM and I'm following it up with the MX-15 (Mepis) folks. One strange quirk about this is that it created a 15GB partition whereas the free space in the MBR was about 24GB between the target root partition and a NTFS data partition. I guess this was probably due to the fact that the hidden Linux partition was being used, but it was the same size as the target partition in front of it so the installer could already have decided to use a 15GB partition size. Any comments on this would be welcome but my question here is about the second problem as follows:

The installer said ""The partition you selected for root appears to be a MS-Windows partition. Are you sure ..." whereas this was in fact an ext4 partition (as explained above). Apparently this is probably due to the installer using lsblk to find the partition type but coming up with blanks on this system:

root@Orac-MX-15:/home/jr# lsblk -lo name,size,fstype,type,parttype,label
NAME SIZE FSTYPE TYPE PARTTYPE LABEL
sda 223.6G disk
sda1 14.7G ext4 part MX-15
sda2 50.8G ntfs part data
sda4 2G swap part MXswap
sdb 1.8T disk
sdb1 97.7G ntfs part 0x7 SYSIMG
sdb2 1.7T ext4 part 0x83 NASback
sr0 1024M rom
root@Orac-MX-15:/home/jr#

Unfortunately this bulletin board doesn't format the above like the text I pasted (pity it doesn't use CODE tags). The PARTTYPE follows the TYPE field and is blank for sda (MX-15, data, MXswap are LABEL fields) but it isn't blank for sdb - it shows 0x7 and 0x83. Is BIBM responsible for the PARTTYPE being omitted?
Russell
rustleg
 
Posts: 108
Joined: Thu Sep 01, 2011 10:01 am

Re: Missing parttype in Linux lsblk

Postby TeraByte Support » Sat Jan 02, 2016 10:52 pm

no, once you boot BIBM is no longer in the system.

check the start/end lba looking for overlaps. you can also use partinfo to
see the file system id in the mbr and ebmr or gpt.



"rustleg" wrote in message news:10803@public.bootitbm...

I installed Linux MX-15 a couple of days ago and I had 2 problems.

First was that it decided to ignore the partition I had chosen for
installation, which was an ext4 partition I had previously used for another
Linux (Mint). I didn't bother to wipe it as I assumed the installer would
ask if I wanted to format it (but it didn't ask) or else just go ahead,
which it did. But it didn't install the system in that partition but in the
"free space following". It overwrote another hidden Linux partition (I
didn't limit primaries) but that wasn't a big issue as I had an image.
Obviously this is a problem with the installer rather than BIBM and I'm
following it up with the MX-15 (Mepis) folks. One strange quirk about this
is that it created a 15GB partition whereas the free space in the MBR was
about 24GB between the target root partition and a NTFS data partition. I
guess this was probably due to the fact that the hidden Linux partition was
being used, but it was the same size as the target partition in front of it
so the installer could already have decided to use a 15GB partition size.
Any comments on this would be welcome but my question here is about the
second problem as follows:

The installer said ""The partition you selected for root appears to be a
MS-Windows partition. Are you sure ..." whereas this was in fact an ext4
partition (as explained above). Apparently this is probably due to the
installer using lsblk to find the partition type but coming up with blanks
on this system:

root@Orac-MX-15:/home/jr# lsblk -lo name,size,fstype,type,parttype,label
NAME SIZE FSTYPE TYPE PARTTYPE LABEL
sda 223.6G disk
sda1 14.7G ext4 part MX-15
sda2 50.8G ntfs part data
sda4 2G swap part MXswap
sdb 1.8T disk
sdb1 97.7G ntfs part 0x7 SYSIMG
sdb2 1.7T ext4 part 0x83 NASback
sr0 1024M rom
root@Orac-MX-15:/home/jr#

Unfortunately this bulletin board doesn't format the above like the text I
pasted (pity it doesn't use CODE tags). The PARTTYPE follows the TYPE field
and is blank for sda (MX-15, data, MXswap are LABEL fields) but it isn't
blank for sdb - it shows 0x7 and 0x83. Is BIBM responsible for the PARTTYPE
being omitted?

TeraByte Support
 
Posts: 2330
Joined: Thu May 05, 2011 3:37 pm


Return to BootIt Bare Metal

cron