You are not logged in.
Pages: 1
hi every body
I set the partition size to 20 GB to install Arch but now i want too increase partation
its fdisk -l
[root@skyboy ~]# fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LM012 HN-M5
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: gpt
Disk identifier: 8A94A9E9-81D2-4D55-85A3-43FDA9583ED1
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda3 315598848 645326847 329728000 157.2G Microsoft basic data
/dev/sda4 645326848 646375423 1048576 512M EFI System
/dev/sda5 646375424 650569727 4194304 2G Linux swap
/dev/sda6 650569728 692512767 41943040 20G Linux filesystemi create new partition with fdisk with linux system type but i dont see partition in my Dolphin file manager
[root@skyboy ~]# fdisk /dev/sda
Welcome to fdisk (util-linux 2.36).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): n
Partition number (2,7-128, default 2):
First sector (4096-976773134, default 4096):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (4096-315598847, default 315598847): +100G
Created a new partition 2 of type 'Linux filesystem' and of size 100 GiB.
Command (m for help): w
The partition table has been altered.
Syncing disks.and after that
[root@skyboy ~]# fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LM012 HN-M5
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: gpt
Disk identifier: 8A94A9E9-81D2-4D55-85A3-43FDA9583ED1
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 209719295 209715200 100G Linux filesystem
/dev/sda3 315598848 645326847 329728000 157.2G Microsoft basic data
/dev/sda4 645326848 646375423 1048576 512M EFI System
/dev/sda5 646375424 650569727 4194304 2G Linux swap
/dev/sda6 650569728 692512767 41943040 20G Linux filesystemsda2 is created success but i dont see and i cant use that
Where is my work wrong?
Last edited by SkyBoy (2020-09-30 18:56:01)
Offline
I see where you created a partition, but, I don't see where you put a filesystem on it.
Offline
a separate partition is fine, but you have to make a filesystem, mount it somewhere, then think about how to use it. the size of the original 20G partition would not change.
it seems like you could grow the partition you already have
parted /dev/sda unit mib print freeif there is free space after sda6, with parted you can use 'resizepart' to grow it, then follow with resize2fs (if it's ext4 filesystem on sda6)
Last edited by frostschutz (2020-09-30 12:23:47)
Offline
I see where you created a partition, but, I don't see where you put a filesystem on it.
thanks for your attention
i set partition on ext4 :
root@skyboy ~]# mkfs.ext4 /dev/sda2
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 26214400 4k blocks and 6553600 inodes
Filesystem UUID: dbd17d43-1796-410d-95c0-20a0e7aea72c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks):
done
Writing superblocks and filesystem accounting information: done and partition successfully shown
but i cant do anything like:
i cant create folder,paste or save anything in that partition
how can i solve that?
and this is lsblk -l:
[root@skyboy ~]# lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
sda1 8:1 0 1M 0 part
sda2 8:2 0 100G 0 part /run/media/amirsky/dbd17d43-1796-410d-95c0-20
sda3 8:3 0 157.2G 0 part
sda4 8:4 0 512M 0 part
sda5 8:5 0 2G 0 part [SWAP]
sda6 8:6 0 20G 0 part /home
sr0 11:0 1 1024M 0 rom Last edited by SkyBoy (2020-09-30 12:40:34)
Offline
It's an ext4 partition so the permissions reside on the filesystem. If you intend this to be a logical extension of your /home chown the directory to your user/group after mounting.
See this example of the same case we have here
Last edited by V1del (2020-09-30 12:46:24)
Offline
It's an ext4 partition so the permissions reside on the filesystem. If you intend this to be a logical extension of your /home chown the directory to your user/group after mounting.
I did not understand what to do
i do this:
[root@skyboy ~]# chown user/group /dev/sda2
chown: invalid user: ‘user/group’
[root@skyboy ~]# chown user /dev/sda2
chown: invalid user: ‘user’
[root@skyboy ~]# chown usr /dev/sda2
chown: invalid user: ‘usr’
[root@skyboy ~]# chown group /dev/sda2
chown: invalid user: ‘group’Offline
Not the device, the directory of the mounted partition (i.e. /run/media/amirsky/dbd17d43-1796-410d-95c0-20 ) . And user/group should be your own local user and the primary group of that same user . Read the entire linked article if you aren't aware of these basics.
Last edited by V1del (2020-09-30 13:55:02)
Offline
V1del wrote:It's an ext4 partition so the permissions reside on the filesystem. If you intend this to be a logical extension of your /home chown the directory to your user/group after mounting.
I did not understand what to do
i do this:[root@skyboy ~]# chown user/group /dev/sda2 chown: invalid user: ‘user/group’ [root@skyboy ~]# chown user /dev/sda2 chown: invalid user: ‘user’ [root@skyboy ~]# chown usr /dev/sda2 chown: invalid user: ‘usr’ [root@skyboy ~]# chown group /dev/sda2 chown: invalid user: ‘group’
You have entered the example text. Instead of filling in the required parameters with YOUR actual values.
Instead of
# chown user/group /dev/sda2 You should do
# chown -R skyboy:skyboy /run/media/amirsky/dbd17d43-1796-410d-95c0-20 That will grant ownership of the newly created filesystem on your partition. I personally would create a dedicated mountpoint for it rather than the auto-generated one.
For example:
# mkdir /mnt/partition2
# mount /dev/sda2 /mnt/partition2
# chown -R skyboy:skyboy /mnt/partition2
Then update /etc/fstab to mount upon boot time.
*Above assumes your username is "skyboy"
Last edited by coxe87b (2020-09-30 15:24:31)
Desktop: Dual boot {Arch & Windows 11} | Hyprland | AMD Ryzen 5700X | 32GB DDR4 | AMD Radeon RX 6700XT | Dual display DP-1 & DP-2=2560x1440
Laptop: Triple boot {Arch & Mint & Windows 11} | Dell Latitude 5420 | Intel Core i5-1145G7 | 16GB DDR4 | Iris Xe GPU | eDP-1=1920x1080
~ Do or do not, there is no try ~
Offline
SkyBoy wrote:V1del wrote:It's an ext4 partition so the permissions reside on the filesystem. If you intend this to be a logical extension of your /home chown the directory to your user/group after mounting.
I did not understand what to do
i do this:[root@skyboy ~]# chown user/group /dev/sda2 chown: invalid user: ‘user/group’ [root@skyboy ~]# chown user /dev/sda2 chown: invalid user: ‘user’ [root@skyboy ~]# chown usr /dev/sda2 chown: invalid user: ‘usr’ [root@skyboy ~]# chown group /dev/sda2 chown: invalid user: ‘group’You have entered the example text. Instead of filling in the required parameters with YOUR actual values.
Instead of
# chown user/group /dev/sda2You should do
# chown -R skyboy:skyboy /run/media/amirsky/dbd17d43-1796-410d-95c0-20That will grant ownership of the newly created filesystem on your partition. I personally would create a dedicated mountpoint for it rather than the auto-generated one.
For example:# mkdir /mnt/partition2
# mount /dev/sda2 /mnt/partition2
# chown -R skyboy:skyboy /mnt/partition2Then update /etc/fstab to mount upon boot time.
*Above assumes your username is "skyboy"
thanks a lot
The problem was completely SOLVED
Offline
Pages: 1