J’ai fini par réussir à augmenter la partition sous un VM Debian 11 ( sous Proxmox ) mais je suis jamais 100% sur de moi. J’oubli souvent la commande partprobe qui permet la confirmation du changement.
J’ai donc l’erreur :
# journalctl -u udisks2.service
-- Logs begin at Thu 2020-12-03 11:00:22 CET, end at Thu 2020-12-03 20:33:01 CET. --
déc. 03 11:00:26 my systemd[1]: Starting Disk Manager...
déc. 03 11:00:26 my udisksd[540]: udisks daemon version 2.8.1 starting
déc. 03 11:00:26 my udisksd[540]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
déc. 03 11:00:26 my udisksd[540]: Failed to load the 'mdraid' libblockdev plugin
déc. 03 11:00:27 my systemd[1]: Started Disk Manager.
déc. 03 11:00:27 my udisksd[540]: Acquired the name org.freedesktop.UDisks2 on the system message busNormalement d’après les forums il faut faire:
Etape 1 : Localisation du disque avec la command fdisk :
# fdisk -l
Disk /dev/sda: 238,5 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SMI
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: B9D6E0E3-54C2-41BC-BBF8-3464FCE6A229
Device Start End Sectors Size Type
/dev/sda1 2048 999423 997376 487M EFI System
/dev/sda2 999424 98656255 97656832 46,6G Linux filesystem
/dev/sda3 98656256 469749759 371093504 177G Linux filesystem
/dev/sda4 469749760 500117503 30367744 14,5G Linux swap
Disk /dev/sdb: 111,8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SA400S3
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: 0x7ac27f0a
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 234441647 234439600 111,8G 83 Linux
Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Portable SSD T5
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x7beb508f
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 1953522112 1953520065 931,5G 7 HPFS/NTFS/exFAT
# fdisk -l /dev/sdc1
Disk /dev/sdc1: 931,5 GiB, 1000202273280 bytes, 1953520065 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1p1 4294967295 8589934589 4294967295 2T ff BBT
/dev/sdc1p2 4294967295 8589934589 4294967295 2T ff BBT
/dev/sdc1p3 4294967295 8589934589 4294967295 2T ff BBT
/dev/sdc1p4 4294967295 6854241533 2559274239 1,2T ff BBTLa premiere commande localise mon nouveau disque, avec la seconde j’ai plus de détail.
Michel, je te sais tout patraque depuis que tu as vu une série d’articles indiquant que Débian avait plus de faille que Windows:
La liste des failles de Débian est ici : https://www.cvedetails.com/vendor/23/Debian.html .
Je viens de prendre un disque dur externe car j’ai pas trop confiance dans les cartes SD ( désolé Michel).
Etape 1 : Le formatage, pour cela il faut fdisk !
rock64@rock64:~$ cat /etc/debian_version
9.9
rock64@rock64:~$ sudo whereis fdisk
fdisk: /sbin/fdisk /usr/share/man/man8/fdisk.8.gz
rock64@rock64:~$ dpkg -S /sbin/fdisk
util-linux: /sbin/fdisk
rock64@rock64:~$ sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 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/mtdblock0: 4 MiB, 4128768 bytes, 8064 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
Disk /dev/mmcblk1: 59.5 GiB, 63864569856 bytes, 124735488 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: gpt
Disk identifier: 9CFDF7D8-766C-43DE-9354-57097D428E8F
Device Start End Sectors Size Type
/dev/mmcblk1p1 64 8063 8000 3.9M Linux filesystem
/dev/mmcblk1p2 8064 8191 128 64K Linux filesystem
/dev/mmcblk1p3 8192 16383 8192 4M Linux filesystem
/dev/mmcblk1p4 16384 24575 8192 4M Linux filesystem
/dev/mmcblk1p5 24576 32767 8192 4M Linux filesystem
/dev/mmcblk1p6 32768 262143 229376 112M Microsoft basic data
/dev/mmcblk1p7 262144 124735454 124473311 59.4G Linux filesystem
Disk /dev/sda: 1.8 TiB, 2000398933504 bytes, 3907029167 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: 0x88185100
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 3907024128 3907024065 1.8T 7 HPFS/NTFS/exFAT
rock64@rock64:~$ sudo mkfs.ext3 /dev/sda1
mke2fs 1.43.4 (31-Jan-2017)
/dev/sda1 contains a ntfs file system labelled 'Seagate Portable Drive'
Proceed anyway? (y,N) y
Creating filesystem with 488378008 4k blocks and 122101760 inodes
Filesystem UUID: 42a1cde2-2269-4582-b4a0-2bb6272b0990
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done A noter qu’en cas de crash durant le formatage, je conseille alors :