Error resizing partition ubuntu

First, I’d like to be very clear on an important distinction:

Partitions are simply pointers to where filesystems begin and end. On modern disks, these start and end points are expressed as sector values.
Filesystems are complex data structures that reside within partitions (or other containers). Typically, filesystems are defined relative to the start point of the containing partition.

Your /dev/sda2 used to begin at sector 40,962,048. You changed it so that it now begins at sector 80,078,848. Thus, the critical early parts of the filesystem now begin outside the partition. An analogy might be if you somehow moved the front cover of a reference book, sitting flat on a table, a centimeter or so down without moving any of the pages of the book. When you opened the book, you’d find that the table of contents was missing, along with the first chapter or two. Those pages would now be floating freely, extracted from the book. You’d therefore be unable to find anything in the book except by reading the whole thing — and even then, parts of it would be missing.

Generally speaking, any partitioning operation that involves moving or resizing the start of a partition is best done using GParted, which knows the proper order of operations for moving and resizing partition and filesystem data structures to keep everything working properly. Even GParted is not without its risks when resizing partitions, though — especially not when the start point is involved, since this requires moving significant amounts of data, so a bug, power failure, hardware fault, or other problem can end up trashing the whole partition. If you must do it without GParted, you can, but you have to fully understand the distinction between a partition and a filesystem that I’ve outlined, and understand the implications of this distinction for the order in which you perform various operations (resize filesystem, move filesystem, change partition boundaries).

In your specific case, what I recommend is:

Delete your new /dev/sda2.
Re-create your /dev/sda2 using its original start and end sector values. Be sure these are exactly the same as they were before.
Check that the re-created /dev/sda2 is accessible.
Back up your important data from /dev/sda2.
Re-evaluate whether you really need to move the start of the partition. I don’t know what your ultimate goal is, so I can’t do this for you. Perhaps moving the end point would work as well (and that would be safer); or maybe adding another disk would be a better option; or maybe you don’t really need to repartition at all.
If you must repartition the disk, use GParted to do the job.

Источник

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
General Help
[SOLVED] Gparted error upon resizing partition

Gparted error upon resizing partition

Hello,

I am in need of your help!

I logged in to my system which I made to automount the partition /dev/sda9 (/Data). Earlier I did a resize of this partition when installing Pangolin for testing. In an attempt to increase the size of the testing system, and while logged in my default system (Lucid), I closed all applications that are using /Data, umount(ed) /dev/sda9 & used gparted to resize /dev/sda9 (I know; I should have used a live session instead so I am sure all partitions are unmounted; my bad!!)

So the thing is that gparted produced an error (attached):

Code:

GParted 0.5.1
 Libparted 2.2
    Shrink /dev/sda9 from 125.12 GiB to 120.25 GiB  00:00:15    ( ERROR )             calibrate /dev/sda9  00:00:00    ( SUCCESS )             path: /dev/sda9
start: 161887068
end: 424275739
size: 262388672 (125.12 GiB)          check file system on /dev/sda9 for errors and (if possible) fix them  00:00:07    ( SUCCESS )             e2fsck -f -y -v /dev/sda9             Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

   14413 inodes used (0.18%)
    1725 non-contiguous files (12.0%)
       2 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 12877/241
24318123 blocks used (74.14%)
       0 bad blocks
       3 large files

   11709 regular files
    1410 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
    1285 symbolic links (1285 fast symbolic links)
       0 sockets
--------
   14404 files
       e2fsck 1.41.11 (14-Mar-2010)
             shrink file system  00:00:03    ( SUCCESS )             resize2fs /dev/sda9 126086120K             Resizing the filesystem on /dev/sda9 to 31521530 (4k) blocks.
The filesystem on /dev/sda9 is now 31521530 blocks long.

       resize2fs 1.41.11 (14-Mar-2010)
             shrink partition from 125.12 GiB to 120.25 GiB  00:00:02    ( SUCCESS )             old start: 161887068
old end: 424275739
old size: 262388672 (125.12 GiB)       new start: 161887068
new end: 414059309
new size: 252172242 (120.25 GiB)          check file system on /dev/sda9 for errors and (if possible) fix them  00:00:01    ( ERROR )             e2fsck -f -y -v /dev/sda9             The filesystem size (according to the superblock) is 32798584 blocks
The physical size of the device is 31521530 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes

       e2fsck 1.41.11 (14-Mar-2010)
             grow file system to fill the partition  00:00:02    ( ERROR )             resize2fs /dev/sda9             Resizing the filesystem on /dev/sda9 to 31521530 (4k) blocks.
       resize2fs 1.41.11 (14-Mar-2010)
resize2fs: Can't read an block bitmap while trying to resize /dev/sda9 
Please run 'e2fsck -fy /dev/sda9' to fix the filesystem
after the aborted resize operation.
             ========================================
    Move /dev/sda10 to the left and grow it from 4.75 GiB to 9.63 GiB    ========================================

I seek your help.

For more info, here’s the fdisk output:

Code:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x72078d5f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           5       40131   de  Dell Utility
/dev/sda2   *           6        1918    15360000    7  HPFS/NTFS
/dev/sda3            1918       10077    65539869+   7  HPFS/NTFS
/dev/sda4           10078       60802   407443027    5  Extended
/dev/sda5           27032       31238    33788928    7  HPFS/NTFS
/dev/sda6           31239       31846     4882432   82  Linux swap / Solaris
/dev/sda7           31847       34886    24413184   83  Linux
/dev/sda8           34886       60802   208168960   83  Linux
/dev/sda9           10078       25774   126086121   83  Linux
/dev/sda10          25775       27031    10096821   83  Linux

Partition table entries are not in disk order

P.S.: When rebooting, Ubuntu tried checking the partition but it lead to nowhere; I had to skip mounting it.

[Dell Studio XPS 1640] [Core2Duo P8700 2.53GHz] [500/4GB][ATI Radeon HD 4670] [12.04/Win7]
[Dell Inspiron 8600] [? 1.73GHz] [80/1 GB] [-] [10.04/XP]
[No Brand] [PIII (Coppermine) 1GHz] [80GB/248 MB] [-] [#!/lubuntu 11.10/XP]

Re: Gparted error upon resizing partition

It says at the end to do this, did you? And best to run from liveCD.

e2fsck -fy /dev/sda9

Any logical partition mounts the extended partition and you cannot modify any logicals as extended is mounted. This is why even with liveCD you often have to do swap-off as swap is usually a logical partition.
Re: Gparted error upon resizing partition

It is impossible to resize a partition AFTER installing.

If you want a bigger space, get more hard drives. Obviously your current one is enormous.

Or get a USB drive.
Re: Gparted error upon resizing partition

Originally Posted by ph4nt0m117

It is impossible to resize a partition AFTER installing.

If you want a bigger space, get more hard drives. Obviously your current one is enormous.

Or get a USB drive.

THIS is pure nonsense. I myself have resized countless partitions after reinstalling.

Re: Gparted error upon resizing partition

Originally Posted by oldfred

It says at the end to do this, did you? And best to run from liveCD.

e2fsck -fy /dev/sda9

Any logical partition mounts the extended partition and you cannot modify any logicals as extended is mounted. This is why even with liveCD you often have to do swap-off as swap is usually a logical partition.

No didn’t. Just did it from Knoppix usb:
Code:
$ e2fsck -fy /dev/sda9 
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 32798584 blocks
The physical size of the device is 31521530 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
Also tried without the ‘y’ option:
Code:
 e2fsck -f /dev/sda9
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 32798584 blocks
The physical size of the device is 31521530 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error reading block 31981568 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? no

e2fsck: Can't read an block bitmap while retrying to read bitmaps for Data
e2fsck: aborted
I ran a Knoppix from a usb & tried mounting (in nautilus) the partition. I got an error that said that «dmesg | tail» might help, so here it is:
Code:
$ dmesg | tail
[   38.461845] drm: registered panic notifier
[   38.461858] [drm] Initialized radeon 2.7.0 20080528 for 0000:01:00.0 on minor 0
[   39.636262] Adding 4882428k swap on /dev/sda6.  Priority:-1 extents:1 across:4882428k 
[   51.976178] NET: Registered protocol family 10
[   51.976344] lo: Disabled Privacy Extensions
[   59.727755] tg3 0000:08:00.0: irq 44 for MSI/MSI-X
[   59.755260] lp: driver loaded but no devices found
[   59.760127] ppdev: user-space parallel port driver
[   59.828919] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  112.890736] EXT4-fs (sda9): bad geometry: block count 32798584 exceeds size of device (31521530 blocks)
Moreover, here is the fsck output:
Code:
$ sudo fsck /dev/sda9
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 32798584 blocks
The physical size of the device is 31521530 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Data contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error reading block 31981568 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? no

fsck.ext4: Can't read an block bitmap while retrying to read bitmaps for Data
e2fsck: aborted

Last edited by astrobob.tk; April 24th, 2012 at 10:37 PM.

Reason: adding code

[Dell Studio XPS 1640] [Core2Duo P8700 2.53GHz] [500/4GB][ATI Radeon HD 4670] [12.04/Win7]
[Dell Inspiron 8600] [? 1.73GHz] [80/1 GB] [-] [10.04/XP]
[No Brand] [PIII (Coppermine) 1GHz] [80GB/248 MB] [-] [#!/lubuntu 11.10/XP]

Re: Gparted error upon resizing partition

I think gparted wanted you to run the e2fsck as the partition data is corrupted or just the error that e2fsck is now saying. You have to have partition table data and internal data match.

#From liveCD so everything is unmounted,swap off if necessary
#e2fsck is used to check the ext2/ext3/ext4 family of file systems.
sudo e2fsck -C0 -p -f -v /dev/sda9
#if errors:
sudo e2fsck -f -y -v /dev/sda9

And if that does not work, but this is grasping at straws. I never have had to do any of this:
http://linuxexpresso.wordpress.com/2…ock-in-ubuntu/
Remove first inode to use alternative superblock:
http://ubuntuforums.org/showthread.php?t=1682038
Using alternative superblock to check ext3
http://planet.admon.org/using-altern…to-check-ext3/
List backup superblocks:
sudo dumpe2fs /dev/sda5 | grep -i backup
then use backup superblock, 32768 just an example, try several
sudo fsck -b 32768 /dev/sda5
One user could not get partition unmounted (may have needed swapoff), but used another live distro
Re: Gparted error upon resizing partition
Originally Posted by oldfred

I think gparted wanted you to run the e2fsck as the partition data is corrupted or just the error that e2fsck is now saying. You have to have partition table data and internal data match.

#From liveCD so everything is unmounted,swap off if necessary
#e2fsck is used to check the ext2/ext3/ext4 family of file systems.
sudo e2fsck -C0 -p -f -v /dev/sda9
#if errors:
sudo e2fsck -f -y -v /dev/sda9
Code:

$ sudo e2fsck -C0 -p -f -v /dev/sda9 Data: The filesystem size (according to the superblock) is 32798584 blocks The physical size of the device is 31521530 blocks Either the superblock or the partition table is likely to be corrupt! Data: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) $ sudo e2fsck -f -y -v /dev/sda9 e2fsck 1.41.12 (17-May-2010) The filesystem size (according to the superblock) is 32798584 blocks The physical size of the device is 31521530 blocks Either the superblock or the partition table is likely to be corrupt! Abort? yes $ sudo e2fsck -f -v /dev/sda9 e2fsck 1.41.12 (17-May-2010) The filesystem size (according to the superblock) is 32798584 blocks The physical size of the device is 31521530 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Error reading block 31981568 (Invalid argument) while reading inode and block bitmaps. Ignore error<y>? no e2fsck: Can't read an block bitmap while retrying to read bitmaps for Data e2fsck: aborted
Originally Posted by oldfred

This helped solve the problem :
Code:

$ sudo fsck.ext4 -v /dev/sda9 e2fsck 1.41.12 (17-May-2010) The filesystem size (according to the superblock) is 32798584 blocks The physical size of the device is 31521530 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no Data contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Error reading block 31981568 (Invalid argument) while reading inode and block bitmaps. Ignore error<y>? no fsck.ext4: Can't read an block bitmap while retrying to read bitmaps for Data e2fsck: aborted
Code:

$ sudo mke2fs -n /dev/sda9 mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 7880704 inodes, 31521530 blocks 1576076 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 962 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872
Code:

$ sudo e2fsck -b 23887872 /dev/sda9
Interrupted it at some point since I chose the last (?) backup? And ran:
Code:

$sudo e2fsck -b 32768 /dev/sda9 . . . Data: ***** FILE SYSTEM WAS MODIFIED ***** Data: 14413/7880704 files (12.0% non-contiguous), 24298077/31521530 blocks
Originally Posted by oldfred

This was not tried!

Originally Posted by oldfred

One user could not get partition unmounted (may have needed swapoff), but used another live distro

Thank you; now I know

Thank you for you help; I appreciate it
[Dell Studio XPS 1640] [Core2Duo P8700 2.53GHz] [500/4GB][ATI Radeon HD 4670] [12.04/Win7]
[Dell Inspiron 8600] [? 1.73GHz] [80/1 GB] [-] [10.04/XP]
[No Brand] [PIII (Coppermine) 1GHz] [80GB/248 MB] [-] [#!/lubuntu 11.10/XP]
Re: Gparted error upon resizing partition

Glad the backup super block worked.

Tags for this Thread

Bookmarks

Posting Permissions

Источник

I added a new disk (/dev/vdb) of 2TB with existing data from the previous 1TB disk.

I used fdisk /dev/vdb to extend its only partition /dev/vdb1 to full capacity of 2TB from previous 1TB. (In other words, I deleted vdb1, and then re-created it to fill the disk. See How to Resize a Partition using fdisk — Red Hat Customer Portal).

And then I did:

[root - /]$ fsck -n /dev/vdb1
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/vdb1: clean, 46859496/65536000 files, 249032462/262143744 blocks

[root - /]$ e2fsck -f /dev/vdb1
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/vdb1: 46859496/65536000 files (0.4% non-contiguous), 249032462/262143744 blocks

[root - ~]$ resize2fs /dev/vdb1
resize2fs 1.42.9 (28-Dec-2013)
The filesystem is already 262143744 blocks long.  Nothing to do!

And fdisk -l looks like this:

Disk /dev/vdb: 2147.5 GB, 2147483648000 bytes, 4194304000 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 label type: dos
Disk identifier: 0x4eb4fbf8

   Device Boot      Start         End      Blocks   Id  System
/dev/vdb1            2048  4194303999  2097150976   83  Linux

However when I mount it:

mount /dev/vdb1 /mnt

This is what I got from df -h:

/dev/vdb1       985G  935G     0 100% /mnt

Which is still the size of the previous partition.

What am I doing wrong here?

UPDATE

I ran partprobe and it told me to reboot:

Error: Error informing the kernel about modifications to partition /dev/vdb1 -- Device or resource busy.  This means Linux won't know about any changes you made to /dev/vdb1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.
Error: Failed to add partition 1 (Device or resource busy)

So I rebooted and then ran this again:

mount /dev/vdb1 /mnt

But the added file system is still:

/dev/vdb1       985G  935G     0 100% /mnt

Any ideas? Should I do all the fsck, e2fsck, and resize2fs once again?

This is really weird. After the reboot, I ran partprobe again and it was still this error:

Error: Error informing the kernel about modifications to partition /dev/vdb1 -- Device or resource busy.  This means Linux won't know about any changes you made to /dev/vdb1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.
Error: Failed to add partition 1 (Device or resource busy)

Why is the device or resource busy? Even after I rebooted?

Источник

Я хотел создать больше места для Ubuntu на моем жестком диске в пользу моего раздела Windows. Я загрузил livecd и изменил размер раздела NTFS на 100 ГБ. Затем я хотел изменить размер раздела Ubuntu (ext4), чтобы заполнить созданное нераспределенное пространство.

Снимок экрана моего текущего диска. (С livecd нет значка «ключ» после sda6)

Моя первая мысль была просто правой кнопкой мыши на sda6 → move / resize → done. К сожалению, я не могу изменять размер или перемещать раздел. Однако я могу изменить размер раздела NTFS.

Я предполагаю, что это связано с тем, что расширенный раздел sda4 заблокирован. Я не видел возможности разблокировки, хотя …

Итак, как мне изменить размер раздела ext4, возможно, разблокировав расширенный раздел, но как?

задан
1 July 2016 в 04:22

8 ответов

Вы не можете изменять размер смонтированной файловой системы, поэтому вы видите значок блокировки.

У вас все хорошо, вы загрузились в Live CD и изменили размер раздела NTFS.

Теперь вам нужно увеличить расширенный раздел, разделяя «внутри», что расширенный раздел не может «выйти» снаружи.

Убедитесь, что /dev/sda6 отключен. Если значок блокировки виден, щелкните его правой кнопкой мыши и выберите «Отключить». Убедитесь, что раздел подкачки /dev/sda5 отключен. Щелкните правой кнопкой мыши по нему и выберите «Swapoff». Выберите /dev/sda4 и выберите «Изменить размер». Используйте свободное пространство слева. Выберите /dev/sda6 и измените его размер с правой стороны. Внесите изменения, и все готово.

ответ дан Lekensteyn
18 July 2018 в 13:01

Вы не можете изменять размер смонтированной файловой системы, поэтому вы видите значок блокировки.

У вас все хорошо, вы загрузились в Live CD и изменили размер раздела NTFS.

ответ дан Lekensteyn
24 July 2018 в 20:05

Для начала загрузки с вашего live CD.

Нажмите «Пуск» и введите Gparted:

После того, как вы откроете программу, вы увидите список с вашими разделами. Теперь, чтобы внести какие-либо изменения, мы должны размонтировать разделы, которые мы хотим изменить. Щелкните правой кнопкой мыши на разделе и выберите «Отключить»:

[!d4]

Предположим, что я хочу уменьшить размер sda1 и добавить его в sda3. Щелкните правой кнопкой мыши на sda1 и выберите Unmount

Появятся новые окна, если мы сможем внести наши изменения. Теперь, чтобы уменьшить размер, перетащите стрелку «Вправо» влево. Вы также можете ввести пользовательское значение рядом с параметром New size (MB) :. Когда вы выберете новый размер, нажмите кнопку Resize / Move

[!d15]

Теперь появится новое поле с ярлыком unallocated. Мы добавим это свободное пространство в раздел sda1 .

Щелкните правой кнопкой мыши на sda3 и выберите Новый размер (МБ):

[!d24]

Перетащите левую стрелку влево, как показано ниже:

Нажмите Кнопка

Наконец, нажмите кнопку «tick», чтобы применить все ваши изменения.

[!d32]

ответ дан efthialex
18 July 2018 в 13:01

Да, вы можете с GParted.

Загрузите Live CD с Ubuntu. Запустить GParted. Выберите раздел Ubuntu и нажмите «Изменить размер» / «Переместить» с панели инструментов «GParted» или выберите «Меню раздела» → «Изменить размер / перемещение» — при условии, что полученное нераспределенное пространство находится прямо рядом с разделом Ubuntu. Если нераспределенное пространство не находится рядом с разделом Ubuntu, вам нужно либо переместить или сжать разделы, чтобы можно было поместить нераспределенное пространство рядом с разделом Ubuntu, чтобы иметь возможность изменять его размер. Для получения более подробной информации ознакомьтесь с этими сайтами: http://www.dedoimedo.com/computers/gparted.html http://en.kioskea.net/faq/2036-how-to-resize-a- раздел-использование-gparted-on-linux http://gparted.sourceforge.net/larry/resize/resizing.htm http://www.howtogeek.com/114503/how-to-resize-your-ubuntu-partitions/

ответ дан Peachy
18 July 2018 в 13:01

Вы должны загрузиться в LiveCD, чтобы использовать gparted для изменения размера активного раздела ext4 — его неразумно изменять разделы во время их активного использования (особенно активный системный раздел ext4)

вы должны иметь возможность перемещать и изменять размер раздела в этой среде LiveCD, и изменения будут выполняться при загрузке обратно в раздел ext4, а не в LiveCD

ответ дан Thomas Ward
18 July 2018 в 13:01

Для начала загрузки с вашего live CD.

Нажмите «Пуск» и введите Gparted:

[!d4]

[!d15]

Теперь появится новое поле с ярлыком unallocated. Мы добавим это свободное пространство в раздел sda1 .

Щелкните правой кнопкой мыши на sda3 и выберите Новый размер (МБ):

[!d24]

Перетащите левую стрелку влево, как показано ниже:

Нажмите Кнопка

Наконец, нажмите кнопку «tick», чтобы применить все ваши изменения.

[!d32]

ответ дан efthialex
24 July 2018 в 20:05

Да, вы можете с GParted.

ответ дан Peachy
24 July 2018 в 20:05

ответ дан Thomas Ward
24 July 2018 в 20:05

Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

UPDATE

8 ответов

Другие вопросы по тегам:

Похожие вопросы:

Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Re: Gparted error upon resizing partition

Tags for this Thread

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" alt /> Posting Permissions

UPDATE

8 ответов

Другие вопросы по тегам:

Похожие вопросы:

Posting Permissions