[opensuse] partition type is microsoft but filesystem is ext4
Not sure how I did this, but it happened before I upgraded to tumbleweed a couple of months ago, but I only noticed it now. On the partition in question, I had opensuse 42.2 installed, so I went in, changed all my repositories to tumbleweed, and did an online upgrade, and have been operating like that ever since. I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4. -------------------- /home/george # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 488397168 sectors, 232.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 5105ED88-0EA8-4BF5-B7B8-31C56BA1351E Partition table holds up to 128 entries First usable sector is 34, last usable sector is 488397134 Partitions will be aligned on 2048-sector boundaries Total free space is 2349 sectors (1.1 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 52430847 25.0 GiB 8300 rootxtra 2 52430848 104859647 25.0 GiB 0700 roottw 3 104859648 488396799 182.9 GiB 0700 ntfsdata /home/george # mount | grep sda /dev/sda2 on / type ext4 (rw,relatime) /dev/sda3 on /mounters/ntfsdata type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) ---------------------- First, I didn't know this was even possible, but apparently it is, because my system is running with partition 2 as the root drive. My first question is, is this likely to cause problems, and what kind of problems? My 2nd question is, how important is it to migrate my root over to another partition right away? -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: TW | Plasma 5.13 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | KDE Plasma 5.8 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
George from the tribe wrote:
Not sure how I did this, but it happened before I upgraded to tumbleweed a couple of months ago, but I only noticed it now. On the partition in question, I had opensuse 42.2 installed, so I went in, changed all my repositories to tumbleweed, and did an online upgrade, and have been operating like that ever since.
I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4. [snip]
First, I didn't know this was even possible, but apparently it is, because my system is running with partition 2 as the root drive.
It's very much possible - I'm not sure how much the partition type is really used anymore, but it certainly does not dictate which file systems you can use on a partition.
My first question is, is this likely to cause problems, and what kind of problems?
No and none.
My 2nd question is, how important is it to migrate my root over to another partition right away?
Not important at all. YOu could just use fdisk to revert the partition type to 0x83. -- Per Jessen, Zürich (21.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 15/09/2018 à 18:15, George from the tribe a écrit :
My first question is, is this likely to cause problems, and what kind of problems?
probably not
My 2nd question is, how important is it to migrate my root over to another partition right away?
I think under linux no application take care of this. It happened to me when reformatting in ext4 previous windows partitions jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 15 Sep 2018 at 18:50, jdd@dodin.org
Le 15/09/2018 à 18:15, George from the tribe a écrit :
My first question is, is this likely to cause problems, and what kind of problems?
probably not
I've seen these symptoms cause problems with upgrades - YaST (rightly) gets very confused about the Microsoft partition which it will normally avoid because it knows it's not a linux partition..but then it can't find the root partition to upgrade. IIRC the end result is a system that cant be upgraded without significant manual effort, unless the YaST team figured out a way of working around the issue because I'm pretty sure someone reported it before..at least I hope so.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 15/09/2018 à 19:16, Richard Brown a écrit :
On Sat, 15 Sep 2018 at 18:50, jdd@dodin.org
wrote: Le 15/09/2018 à 18:15, George from the tribe a écrit :
My first question is, is this likely to cause problems, and what kind of problems?
probably not
I've seen these symptoms cause problems with upgrades - YaST (rightly) gets very confused about the Microsoft partition which it will normally avoid because it knows it's not a linux partition..but then it can't find the root partition to upgrade.
ok
IIRC the end result is a system that cant be upgraded without significant manual effort, unless the YaST team figured out a way of working around the issue because I'm pretty sure someone reported it before..at least I hope so..
may be the OP can open a bug report. I'm pretty sure I had such thing recently, but have no memory from what computer :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/09/2018 13.16, Richard Brown wrote:
On Sat, 15 Sep 2018 at 18:50, jdd@dodin.org
wrote: Le 15/09/2018 à 18:15, George from the tribe a écrit :
My first question is, is this likely to cause problems, and what kind of problems?
probably not
I've seen these symptoms cause problems with upgrades - YaST (rightly) gets very confused about the Microsoft partition which it will normally avoid because it knows it's not a linux partition..but then it can't find the root partition to upgrade.
It is actually YaST which sets up that incorrect partition type when it does the partitioning, since several versions. AFAIK it is harmless, except perhaps when running another year and trying to figure out autodetection of systems. It has been commented often enough, it must be a known issue to the YaST team. I think YaST does have a look inside all partitions to find out what they are. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
George from the tribe composed on 2018-09-15 11:15 (UTC-0500):
I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4. -------------------- /home/george # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1
Partition table scan: MBR: protective BSD: not present APM: not present GPT: present
Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 488397168 sectors, 232.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 5105ED88-0EA8-4BF5-B7B8-31C56BA1351E Partition table holds up to 128 entries First usable sector is 34, last usable sector is 488397134 Partitions will be aligned on 2048-sector boundaries Total free space is 2349 sectors (1.1 MiB)
Number Start (sector) End (sector) Size Code Name 1 2048 52430847 25.0 GiB 8300 rootxtra 2 52430848 104859647 25.0 GiB 0700 roottw 3 104859648 488396799 182.9 GiB 0700 ntfsdata
/home/george # mount | grep sda /dev/sda2 on / type ext4 (rw,relatime) /dev/sda3 on /mounters/ntfsdata type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
IMO, gdisk has has misleading personality problems, and other tools are preferable to it. The following are all from TW on the same disk and has no partitions formatted NTFS (type 07s are all HPFS): # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc22068fb Device Boot Start End Sectors Size Id Type /dev/sda1 2048 518143 516096 252M 6 FAT16 /dev/sda2 518144 5433343 4915200 2.4G 17 Hidden HPFS/NTFS /dev/sda3 * 5433344 6252543 819200 400M 83 Linux /dev/sda4 6252544 1953523711 1947271168 928.5G 5 Extended /dev/sda5 6252576 6254591 2016 1008K 1 FAT12 /dev/sda6 6254624 6770687 516064 252M 6 FAT16 /dev/sda7 6770720 23564287 16793568 8G 82 Linux swap / Solaris /dev/sda8 23564320 42739711 19175392 9.1G fd Linux raid autodetect /dev/sda9 42739744 79603711 36863968 17.6G fd Linux raid autodetect /dev/sda10 79603744 116467711 36863968 17.6G fd Linux raid autodetect /dev/sda11 116467744 153331711 36863968 17.6G fd Linux raid autodetect /dev/sda12 153331744 190195711 36863968 17.6G fd Linux raid autodetect /dev/sda13 190195744 198387711 8191968 3.9G fd Linux raid autodetect /dev/sda14 198387744 202483711 4095968 2G fd Linux raid autodetect /dev/sda15 202483744 509683711 307199968 146.5G fd Linux raid autodetect /dev/sda16 509683744 990963711 481279968 229.5G fd Linux raid autodetect /dev/sda17 990963744 1953523711 962559968 459G fd Linux raid autodetect # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Disk /dev/sda: 1953525168 sectors, 931.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 19436D04-01EA-4F55-A8A7-3404DBDFFEE3 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 32-sector boundaries Total free space is 3853 sectors (1.9 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 518143 252.0 MiB 0700 Microsoft basic data 2 518144 5433343 2.3 GiB 0700 Microsoft basic data 3 5433344 6252543 400.0 MiB 8300 Linux filesystem 5 6252576 6254591 1008.0 KiB 0700 Microsoft basic data 6 6254624 6770687 252.0 MiB 0700 Microsoft basic data 7 6770720 23564287 8.0 GiB 8200 Linux swap 8 23564320 42739711 9.1 GiB FD00 Linux RAID 9 42739744 79603711 17.6 GiB FD00 Linux RAID 10 79603744 116467711 17.6 GiB FD00 Linux RAID 11 116467744 153331711 17.6 GiB FD00 Linux RAID 12 153331744 190195711 17.6 GiB FD00 Linux RAID 13 190195744 198387711 3.9 GiB FD00 Linux RAID 14 198387744 202483711 2.0 GiB FD00 Linux RAID 15 202483744 509683711 146.5 GiB FD00 Linux RAID 16 509683744 990963711 229.5 GiB FD00 Linux RAID 17 990963744 1953523711 459.0 GiB FD00 Linux RAID # parted -l Model: ATA ST1000DM003-1CH1 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 265MB 264MB primary fat16 type=06 2 265MB 2782MB 2517MB primary hidden, type=17 3 2782MB 3201MB 419MB primary ext2 boot, type=83 4 3201MB 1000GB 997GB extended type=05 5 3201MB 3202MB 1032kB logical type=01 6 3202MB 3467MB 264MB logical fat16 type=06 7 3467MB 12.1GB 8598MB logical linux-swap(v1) type=82 8 12.1GB 21.9GB 9818MB logical ext4 raid, type=fd 9 21.9GB 40.8GB 18.9GB logical ext4 raid, type=fd 10 40.8GB 59.6GB 18.9GB logical ext4 raid, type=fd 11 59.6GB 78.5GB 18.9GB logical ext4 raid, type=fd 12 78.5GB 97.4GB 18.9GB logical ext4 raid, type=fd 13 97.4GB 102GB 4194MB logical ext4 raid, type=fd 14 102GB 104GB 2097MB logical ext4 raid, type=fd 15 104GB 261GB 157GB logical ext4 raid, type=fd 16 261GB 507GB 246GB logical ext4 raid, type=fd 17 507GB 1000GB 493GB logical ext4 raid, type=fd In short, try a different tool than gdisk if you wish to be sure about the actual partition type. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/15/2018 01:10 PM, Felix Miata wrote:
George from the tribe composed on 2018-09-15 11:15 (UTC-0500):
I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4. -------------------- /home/george # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1
Partition table scan: MBR: protective BSD: not present APM: not present GPT: present
Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 488397168 sectors, 232.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 5105ED88-0EA8-4BF5-B7B8-31C56BA1351E Partition table holds up to 128 entries First usable sector is 34, last usable sector is 488397134 Partitions will be aligned on 2048-sector boundaries Total free space is 2349 sectors (1.1 MiB)
Number Start (sector) End (sector) Size Code Name 1 2048 52430847 25.0 GiB 8300 rootxtra 2 52430848 104859647 25.0 GiB 0700 roottw 3 104859648 488396799 182.9 GiB 0700 ntfsdata
/home/george # mount | grep sda /dev/sda2 on / type ext4 (rw,relatime) /dev/sda3 on /mounters/ntfsdata type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
IMO, gdisk has has misleading personality problems, and other tools are preferable to it. The following are all from TW on the same disk and has no partitions formatted NTFS (type 07s are all HPFS):
# fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc22068fb
Device Boot Start End Sectors Size Id Type /dev/sda1 2048 518143 516096 252M 6 FAT16 /dev/sda2 518144 5433343 4915200 2.4G 17 Hidden HPFS/NTFS /dev/sda3 * 5433344 6252543 819200 400M 83 Linux /dev/sda4 6252544 1953523711 1947271168 928.5G 5 Extended /dev/sda5 6252576 6254591 2016 1008K 1 FAT12 /dev/sda6 6254624 6770687 516064 252M 6 FAT16 /dev/sda7 6770720 23564287 16793568 8G 82 Linux swap / Solaris /dev/sda8 23564320 42739711 19175392 9.1G fd Linux raid autodetect /dev/sda9 42739744 79603711 36863968 17.6G fd Linux raid autodetect /dev/sda10 79603744 116467711 36863968 17.6G fd Linux raid autodetect /dev/sda11 116467744 153331711 36863968 17.6G fd Linux raid autodetect /dev/sda12 153331744 190195711 36863968 17.6G fd Linux raid autodetect /dev/sda13 190195744 198387711 8191968 3.9G fd Linux raid autodetect /dev/sda14 198387744 202483711 4095968 2G fd Linux raid autodetect /dev/sda15 202483744 509683711 307199968 146.5G fd Linux raid autodetect /dev/sda16 509683744 990963711 481279968 229.5G fd Linux raid autodetect /dev/sda17 990963744 1953523711 962559968 459G fd Linux raid autodetect
# gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1
Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present
*************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. ***************************************************************
Disk /dev/sda: 1953525168 sectors, 931.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 19436D04-01EA-4F55-A8A7-3404DBDFFEE3 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 32-sector boundaries Total free space is 3853 sectors (1.9 MiB)
Number Start (sector) End (sector) Size Code Name 1 2048 518143 252.0 MiB 0700 Microsoft basic data 2 518144 5433343 2.3 GiB 0700 Microsoft basic data 3 5433344 6252543 400.0 MiB 8300 Linux filesystem 5 6252576 6254591 1008.0 KiB 0700 Microsoft basic data 6 6254624 6770687 252.0 MiB 0700 Microsoft basic data 7 6770720 23564287 8.0 GiB 8200 Linux swap 8 23564320 42739711 9.1 GiB FD00 Linux RAID 9 42739744 79603711 17.6 GiB FD00 Linux RAID 10 79603744 116467711 17.6 GiB FD00 Linux RAID 11 116467744 153331711 17.6 GiB FD00 Linux RAID 12 153331744 190195711 17.6 GiB FD00 Linux RAID 13 190195744 198387711 3.9 GiB FD00 Linux RAID 14 198387744 202483711 2.0 GiB FD00 Linux RAID 15 202483744 509683711 146.5 GiB FD00 Linux RAID 16 509683744 990963711 229.5 GiB FD00 Linux RAID 17 990963744 1953523711 459.0 GiB FD00 Linux RAID
# parted -l Model: ATA ST1000DM003-1CH1 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags 1 1049kB 265MB 264MB primary fat16 type=06 2 265MB 2782MB 2517MB primary hidden, type=17 3 2782MB 3201MB 419MB primary ext2 boot, type=83 4 3201MB 1000GB 997GB extended type=05 5 3201MB 3202MB 1032kB logical type=01 6 3202MB 3467MB 264MB logical fat16 type=06 7 3467MB 12.1GB 8598MB logical linux-swap(v1) type=82 8 12.1GB 21.9GB 9818MB logical ext4 raid, type=fd 9 21.9GB 40.8GB 18.9GB logical ext4 raid, type=fd 10 40.8GB 59.6GB 18.9GB logical ext4 raid, type=fd 11 59.6GB 78.5GB 18.9GB logical ext4 raid, type=fd 12 78.5GB 97.4GB 18.9GB logical ext4 raid, type=fd 13 97.4GB 102GB 4194MB logical ext4 raid, type=fd 14 102GB 104GB 2097MB logical ext4 raid, type=fd 15 104GB 261GB 157GB logical ext4 raid, type=fd 16 261GB 507GB 246GB logical ext4 raid, type=fd 17 507GB 1000GB 493GB logical ext4 raid, type=fd
In short, try a different tool than gdisk if you wish to be sure about the actual partition type.
Thanks everyone for your comments. Good to know that there is no immediate concern about this. I will fix it with something at some point in the future. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: TW | Plasma 5.13 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | KDE Plasma 5.8 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/09/2018 15.52, George from the tribe wrote:
Thanks everyone for your comments. Good to know that there is no immediate concern about this. I will fix it with something at some point in the future.
It is actually very simple: take any partitioner, say, fdisk, and change the type. No formatting. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/15/2018 9:15 AM, George from the tribe wrote:
I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4.
MBR stands for Master Boot Record. Here, in a GPT formatted disk, I believe it is there to signal to other formatting utils that don't recognize a Global Partition Table, that the disk is formatted. I'm not sure if it contains actual boot code or not -- I tend to think it's there as a place marker to protect the GPT data. As far as I know, any partition can be a root partition. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/09/2018 11.48, L A Walsh wrote:
On 9/15/2018 9:15 AM, George from the tribe wrote:
I noticed this morning while setting up my backups, that it turns out the partition type is "Microsoft basic data" but the file system type is ext4.
MBR stands for Master Boot Record. Here, in a GPT formatted disk, I believe it is there to signal to other formatting utils that don't recognize a Global Partition Table, that the disk is formatted. I'm not sure if it contains actual boot code or not -- I tend to think it's there as a place marker to protect the GPT data.
It can contain bootcode, yes. It is the trick to make GPT disks bootable on old BIOS machines.
As far as I know, any partition can be a root partition.
-- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R.
-
Felix Miata
-
George from the tribe
-
jdd@dodin.org
-
L A Walsh
-
Per Jessen
-
Richard Brown