Long time SuSE / openSUSE user. I was looking forward to installing Leap 15 this morning, but quickly hit a problem.
I have 4 hard drives in my system (all SATA, all pre-partitioned, all MBR partition table not GPT). However, the SuSE Partitioner only detected the partition tables for 1 of these 4 hard disks (sdc), and this disk was not the disk containing the partition I intend to install OpenSuSE Leap 15 on (sdd). The other 3 disks just listed a single device for the whole disk in the Partitioner.
**How do I get the Partitioner to read the partition table for a specific disk I specify (or for all disks, which IMO should have been the default)?
**I know this disk I want to install Leap 15 on is partitioned properly and working just fine as it contains the OpenSuSE 13.1 install that I’m posting from now!
Yes. And selected “Start with Existing Partitions”. Here’s more data as well: I unplugged every single hard drive in my system “except” the one I want to install SuSE 15.0 on (sdd), which is the same one that I am currently booting and running SuSE 13.1 on from a different partition. Expert Partitioner → Start with Existing Partitions still wouldn’t detect “any” partitions on that disk, despite the fact that it’s a working disk that’s already pre-partitioned. So, I flipped over to a shell (Ctrl-Alt-F2) and ran “fdisk /dev/sda”. The partition output looked fine! All 8 partitions reported properly. … however at the end of the partition report it said:
Partition 1 does not start on a physical sector boundary. < repeated for partitions 2..8 >
After that, I tried “parted /dev/sda print”, but it didn’t work properly, reporting only a single partition of 1000GB (entire disk) of type fat16, giving all the appearances of seeing it as an unpartitioned disk (which it’s not). That’s strange considering that in SuSE 13.1, both fdisk and parted report the partition table properly. Here’s the SuSE 13.1 output for parted and fdisk:
# parted /dev/sda print
Model: ATA WDC WD10EZRX-00L (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 52.4GB 52.4GB primary fat32 type=0b
2 52.4GB 105GB 52.4GB primary ntfs type=07
3 105GB 1000GB 895GB extended boot, lba, type=0f
5 105GB 136GB 31.5GB logical ext4 type=83
6 136GB 138GB 2089MB logical linux-swap(v1) type=82
7 138GB 170GB 31.5GB logical ext4 type=83
8 170GB 1000GB 830GB logical ext4 type=83
# fdisk /dev/sda
Disk /dev/sda: 1000.2 GB, 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 Disk label type: dos Disk identifier: 0x0000000a Device Boot Start End Blocks Id System /dev/sda1 63 102398309 51199123+ b W95 FAT32 Partition 1 does not start on physical sector boundary. /dev/sda2 102398310 204796619 51199155 7 HPFS/NTFS/exFAT Partition 2 does not start on physical sector boundary. /dev/sda3 * 204796620 1953520064 874361722+ f W95 Ext'd (LBA) Partition 3 does not start on physical sector boundary. /dev/sda5 204796683 266229179 30716248+ 83 Linux Partition 5 does not start on physical sector boundary. /dev/sda6 266229243 270309689 2040223+ 82 Linux swap / Solaris Partition 6 does not start on physical sector boundary. /dev/sda7 270309753 331742249 30716248+ 83 Linux Partition 7 does not start on physical sector boundary. /dev/sda8 331742313 1953520064 810888876 83 Linux Partition 8 does not start on physical sector boundary.
Do you mean did I generate the sha256 checksum and verify the integrity of the ISO I downloaded? Yes. EDIT: What is wrong with the editor on these forums? It just took out all the newlines in my entire post, so the code blocks are almost unreadable.
I’m not having that problem. I’m using firefox. However, I have had similar problems with other browsers.
I’m not sure what browser you are using.
At the top left of the browser window, there’s something that looks like A/A. If you click that, it will change the edit box to just show plain unformatted. You might have less problems with that. In particular, what you paste into the edit box will be text with no formats. Even with firefox, I sometimes find that useful.
Now that I’ve got that fixed (Forum software quirk), let me repost that SuSE 13.1 parted and fdisk output for that disk I’m trying to install Leap 15 to:
# parted /dev/sda print
Model: ATA WDC WD10EZRX-00L (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 52.4GB 52.4GB primary fat32 type=0b
2 52.4GB 105GB 52.4GB primary ntfs type=07
3 105GB 1000GB 895GB extended boot, lba, type=0f
5 105GB 136GB 31.5GB logical ext4 type=83
6 136GB 138GB 2089MB logical linux-swap(v1) type=82
7 138GB 170GB 31.5GB logical ext4 type=83
8 170GB 1000GB 830GB logical ext4 type=83
# fdisk /dev/sda
...
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 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
Disk label type: dos
Disk identifier: 0x0000000a
Device Boot Start End Blocks Id System
/dev/sda1 63 102398309 51199123+ b W95 FAT32
Partition 1 does not start on physical sector boundary.
/dev/sda2 102398310 204796619 51199155 7 HPFS/NTFS/exFAT
Partition 2 does not start on physical sector boundary.
/dev/sda3 * 204796620 1953520064 874361722+ f W95 Ext'd (LBA)
Partition 3 does not start on physical sector boundary.
/dev/sda5 204796683 266229179 30716248+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 266229243 270309689 2040223+ 82 Linux swap / Solaris
Partition 6 does not start on physical sector boundary.
/dev/sda7 270309753 331742249 30716248+ 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 331742313 1953520064 810888876 83 Linux
Partition 8 does not start on physical sector boundary.
Firefox 59.0.2. I post to another VBulletin Forum-based site every day and have never had this problem.
However, playing with these forums, I found I had to disable the WYSIWYG editor in my General settings. Then the forum software here stops deleting all of my newline characters. But that’s just weird. I post to another VBulletin-based forum every day and I’ve never had this problem there. EDIT: The problem may have been related to not giving opensuse.org and suse.org perms to run Javascript in my browser.
I see what you’re talking about now. Thanks for the tip. I’ll keep that in mind for the future.
And here is the Leap 15 parted and fdisk output for that same disk, which I just snagged from the DVD install using a shell and a USB flash drive:
# parted /dev/sda print
Model: ATA WDC WD10EZRX-00L (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 1000GB 1000GB fat16
# fdisk /dev/sda
...
Command (m for help): p
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: 0x0000000a
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 102398309 102398247 48.8G b W95 FAT32
/dev/sda2 102398310 204796619 102398310 48.8G 7 HPFS/NTFS/exFAT
/dev/sda3 * 204796620 1953520064 1748723445 833.9G f W95 Ext'd (LBA)
/dev/sda5 204796683 266229179 61432497 29.3G 83 Linux
/dev/sda6 266229243 270309689 4080447 2G 82 Linux swap / Solaris
/dev/sda7 270309753 331742249 61432497 29.3G 83 Linux
/dev/sda8 331742313 1953520064 1621777752 773.3G 83 Linux
Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition 6 does not start on physical sector boundary.
Partition 7 does not start on physical sector boundary.
Partition 8 does not start on physical sector boundary.
It seems like parted in Leap 15 has taken a step back from it’s capability in SuSE 13.1. I wonder if that has something to do with the Leap 15 Partitioner’s problem detecting the partitions on this disk.
Partition label “loop” is certainly unexpected. Could you post “hexdump -C -n 512 /dev/sda”? And it possible the same for other disks that are not recognized by Leap 15?
Partition 1 does not start on physical sector boundary.
Wild speculation, and probably wrong, but…
Couldn’t it be that, given the pervasiveness of SSD nowadays, LEAP 15 installer requires sector bound partitions, and thus does not recognize the existing ones? IINM there was a change in the installer partition editor.
# hexdump -C -n 512 /dev/sdb
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 00 00 00 00 00 00 00 00 2f ba 91 bd 00 00 81 01 |......../.......|
000001c0 01 00 07 fe ff ff 3f 00 00 00 bd ea ff 18 00 fe |......?.........|
000001d0 ff ff 07 fe ff ff fc ea ff 18 fc ea ff 18 00 fe |................|
000001e0 ff ff 0f fe ff ff f8 d5 ff 31 5d db bf 07 00 00 |.........1].....|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
sdb surprised me, as I have Windows backup partitions created and populated on that disk. I guess I must not have used the same partitioning tool to partition it.
Yes, that’s likely. In WYSIWYG mode, the editor probably needs javascript. I allow scripting for opensuse.org, suse.com and microfocus.com. That “A/A” button turns off WYSIWYG (I think).
That is the problem. Apparently SBM boot code looks identical to FAT superblock, so parted mistedects it and ignores real partition table. From parted NEWS:
libparted: fat and ntfs boot sectors were misdetected as dos partition tables instead of being treated as a loop label.
I was able to reproduce it easily on Leap 15 by writing your MBR on disk. Personally I would say this is something that both projects should be made aware of. May be SBM can be told to not instal FAT boot sector on MBR.
Now this is not really “new” - last parted version was released in 2014. It would be interesting to know whether you managed to install previous openSUSE version on disk with SBM. If yes, it implies regression in openSUSE and you should open bug report also on openSUSE bugzilla
Actually you probably should file openSUSE bug in any case, simply to make developers aware of this problem.
Was that directed to comment 14? If so, you must not have read the link, or at least, not seen the “start with existing partitions” difference between its attachment and the image nrickert posted here.