Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Without seeing the output from fdisk it is not possible to understand the problem.
Quote:
Are not all partitions on a physical volume the same partition table format?
It is possible to create a table on a partition itself i.e. fdisk /dev/sdx1 that is separate from the entire drive i.e. fdisk /dev/sdx. You can find more then one thread on the site where the OP made the mistake.
FDISK and GPARTED show different things because you have them POINTED to different things.
From what I can tell (with possibly inadequate information) your /dev/sda disk has a GPT/EFI table. IF it is a normal EFI format that means partition /dev/sda1 will be DOS/FAT format file system and /dev/sda2 will be some format of Linux partition. (most common is Linux(83) type which can contain almost any of the Linux filesystems. On my laptops usually EXT4 or BTRFS. )
You pointed GPARTED at the disk.
You pointed FDISK at the DOS partition.
It is possible to create a table on a partition itself i.e. fdisk /dev/sdx1 that is separate from the entire drive i.e. fdisk /dev/sdx. You can find more then one thread on the site where the OP made the mistake.
The output is clear, it is a GPT disk, but how MBR resides on GPT demands cognitive digestion.
It is as if a partition is just another disk. But if, say, an OS demands a GPT/UEFI setup, will it be the disk or partition complying with the standard?
I believe we basically are all saying the same thing. You specified the wrong device when running fdisk. Again it is possible to create a partition table within a partition itself like below. The drive itself is GPT and the partition table created within the first partition is MBR. While it is possible I don't know if can actually be used. Best to create a new filesystem.
Code:
root@debian:~# fdisk -l /dev/sdb
Disk /dev/sdb: 1.44 GiB, 1543503872 bytes, 3014656 sectors
Disk model: VBOX HARDDISK
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9C186899-02B4-46B5-A148-70F5AC8C99DB
Device Start End Sectors Size Type
/dev/sdb1 2048 3012607 3010560 1.4G Linux filesystem
root@debian:~# fdisk -l /dev/sdb1
Disk /dev/sdb1: 1.44 GiB, 1541406720 bytes, 3010560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8211f379
Device Boot Start End Sectors Size Id Type
/dev/sdb1p1 2048 3010559 3008512 1.4G 83 Linux
The drive itself is GPT and the partition table created within the first partition is MBR. While it is possible I don't know if can actually be used.
Oh, it can be used, and really isn't all that uncommon. Consider a host partition that is used as a virtual disk by a VM. Viewed from the host, it's a partition that then begins with a partition table. While it's uncommon to dig into that partition structure from the host, you can do it if you play the right games with kpartx. While you can do that from a booted system, there's no way to make the BIOS dig into that partition, treat it like a drive, and boot from it, at least none that I know of. It can of course be used as the boot drive for a VM, but that doesn't help if the objective is to install an OS on the bare hardware.
Oh, it can be used, and really isn't all that uncommon. While you can do that from a booted system, there's no way to make the BIOS dig into that partition, treat it like a drive, and boot from it, at least none that I know of.
That's what BSD does. I fooled about a bit with openbsd a couple of years ago and was amazed to find that it subdivided its partition and placed some kind of mbr or label at the beginning of it to handle the sub-partitions. This label also had entries for the other main partitions on the drive so that they could be mounted within the BSD system.
It must have booted in two stages. There was some kind of BSD bootloader on the partition, which could be accessed with GRUB or reFind but not with elilo.
The discrepancy between disk types in fdisk and gparted often occurs because they interpret disk types differently. fdisk typically categorizes disks based on their partition table type (e.g., MBR or GPT), while gparted categorizes disks based on their partitioning scheme (e.g., MBR, GPT, or unallocated space). This variation can lead to differences in the reported disk types between the two tools.
The discrepancy between disk types in fdisk and gparted often occurs because they interpret disk types differently. fdisk typically categorizes disks based on their partition table type (e.g., MBR or GPT), while gparted categorizes disks based on their partitioning scheme (e.g., MBR, GPT, or unallocated space). This variation can lead to differences in the reported disk types between the two tools.
Yeah, but that was not the issue here.
He pointed one at the disk /dev/sda
and the other at the PARTITION /dev/sda1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.