breakdown of the disc

[Member ThakurMsh]

my respects to all!
during installation, I selected automatic split
can you please tell me why this might be?
$ sudo fdisk -l
[sudo] пароль для th:
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 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 /dev/ram1: 16 MiB, 16777216 bytes, 32768 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 /dev/ram2: 16 MiB, 16777216 bytes, 32768 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 /dev/ram3: 16 MiB, 16777216 bytes, 32768 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 /dev/ram4: 16 MiB, 16777216 bytes, 32768 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 /dev/ram5: 16 MiB, 16777216 bytes, 32768 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 /dev/ram6: 16 MiB, 16777216 bytes, 32768 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 /dev/ram7: 16 MiB, 16777216 bytes, 32768 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 /dev/ram8: 16 MiB, 16777216 bytes, 32768 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 /dev/ram9: 16 MiB, 16777216 bytes, 32768 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 /dev/ram10: 16 MiB, 16777216 bytes, 32768 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 /dev/ram11: 16 MiB, 16777216 bytes, 32768 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 /dev/ram12: 16 MiB, 16777216 bytes, 32768 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 /dev/ram13: 16 MiB, 16777216 bytes, 32768 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 /dev/ram14: 16 MiB, 16777216 bytes, 32768 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 /dev/ram15: 16 MiB, 16777216 bytes, 32768 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 /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Samsung SSD 850
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: 4DFAD128-5AEE-48D9-8F24-791482E420F0

Device Start End Sectors Size Type
/dev/sda1 2048 526335 524288 256M Linux filesystem
/dev/sda2 526336 230182911 229656576 109,5G Linux filesystem
/dev/sda3 230182912 234377215 4194304 2G Linux filesystem

[Member Xecure]

Helpful

Up

0

::

I don’t understand what you are asking.
The “breakdown” of the disk is only:

Disk /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Samsung SSD 850
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: 4DFAD128-5AEE-48D9-8F24-791482E420F0

Device Start End Sectors Size Type
/dev/sda1 2048 526335 524288 256M Linux filesystem
/dev/sda2 526336 230182911 229656576 109,5G Linux filesystem
/dev/sda3 230182912 234377215 4194304 2G Linux filesystem

The rest is Ram “sectors”. Not relevant to your Hard disk.

What I see is:
DISK: Samsung SSD 850 (111,8 GiB) – Partition table: GPT
– Partition 1 (/dev/sda1): Size: 256M – Type:Linux (can it be the /boot partition? not sure)
– Partition 2 (/dev/sda2): Size: 109,5G – Type:Linux (definitely the root or system partition, where ALL antiX system is housed)
– Partition 3 (/dev/sda3): Size: 2G – Type:Linux (This is the SWAP partition, that will be used for hibernation or when you need more RAM, and other things).

fdisk isn’t very good for what you want to figure out. Why not use
lsblk
or
blkid
to see real valuable info about your partitions?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Anonymous]

Helpful

Up

0

::

during installation, I selected automatic split

something misunderstood in translation? gazelle-installer_ru.ts

separate…split…partition…re-partition
(“split” here is a noun, or a verb?)

[Member ThakurMsh]

Helpful

Up

0

::

@skidoo, …disk partitioning…
@xecure,

th@anx:~
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111,8G  0 disk 
├─sda1   8:1    0   256M  0 part /boot/efi
├─sda2   8:2    0 109,5G  0 part /
└─sda3   8:3    0     2G  0 part [SWAP]
sr0     11:0    1   5,7M  0 rom  /media/sr0

th@anx:~
$ blkid
/dev/sda1: UUID="1BA2-9BD6" TYPE="vfat" PARTLABEL="ESP" PARTUUID="8d82a762-b9cb-4a6e-9b58-13b880c663f9"
/dev/sda2: LABEL="rootantiX19" UUID="5f5cee75-af3f-4235-bf1f-43912d6f0ef3" TYPE="ext4" PARTLABEL="primary" PARTUUID="a3453ec6-21a9-4eb0-a2bf-624cdcceb4de"
/dev/sda3: LABEL="swapantiX" UUID="ef1cb892-6cf9-4c0f-8a7a-f22bfefbc70b" TYPE="swap" PARTLABEL="primary" PARTUUID="443a0dbc-1343-47c2-977c-7b08425632ca"
/dev/sr0: UUID="2018-11-29-11-25-39-00" LABEL="4G USB M-PM-<M-PM->M-PM-4M-PM-5M-PM-<" TYPE="iso9660" PTTYPE="mac"

then the question arises:
I have a disk of 120G, but if you add it up, it will be 112G
what is it? Disk /dev/ram*`

• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.

[Moderator BobC]

Helpful

Up

0

::

It looks like it used all the space as well as it could. When the drive is formatted a percentage of the space is reserved for things like bad blocks and can’t be used.

That is completely normal for all operating systems. All is well. That should be a good and fast SSD.

[Anonymous]

Helpful

Up

0

::

> what is it? Disk /dev/ram*

a websearch “linux /dev/ram” will be enlightening

also
https://superuser.com/questions/971000/why-df-vs-lsblk-command-have-different-results
.
https://serverfault.com/questions/771832/why-there-is-a-difference-in-size-reported-by-lsblk-gdisk-and-parted

[Member Xecure]

Helpful

Up

0

::

ThakurMsh wrote:

I have a disk of 120G, but if you add it up, it will be 112G

Sorry to be the one to wake you up to the cruel reality. You have been tricked!
But don’t worry, we are all being tricked, so you are not alone.
Hardware sellers tell you it is 120 GB, but they are in fact using multiples of 1000 to calculate the amount. Normally, 1024 Bytes makes a Kilobyte, but manufacturers use the conversion 1000 Bytes equals a Kilobyte.

The manufacturers say 120 GB. That would be 120 * 1000 *1000 * 1000 = 1.2*10^11 Bytes.
To get the real amount of Gigabytes, you would divide with 1024 three times.
The machine says 111,8 GB. That would be 1.2*10^11 / 1024 / 1024 / 1024 = 111,76 GB

Now you know the truth. Now you are “woke”.

• This reply was modified 2 years, 5 months ago by Xecure. Reason: Fixed typos
• This reply was modified 2 years, 5 months ago by Xecure. Reason: fixed divide

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Anonymous]

Helpful

Up

0

::

https://en.wikipedia.org/wiki/Gibibyte
other-ref-gib.html

[Member Xecure]

Helpful

Up

0

::

I still don’t understand why we use measurements that the computer doesn’t use.
I was taught that MB (As in Megabytes) were multiples of 1024 (2^10), and have always used the word thinking this was so. Now I will have to talk in mebibytes (and no-one will understand me 🙁 )

Thanks for the informative links.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member ThakurMsh]

Helpful

Up

0

::

@bobc
@skidoo
@xecure

Thank you very much!

(o_ _)o
(o_ _)o
(o_ _)o

• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.

[Author]

Posts