Partition table entries are not in disk order как исправить

Иногда может случиться так, что порядок разделов в таблице разделов меняется. Таким образом, что раздел (партиция) с номером x+2 оказывается физически между разделом x и x+1. Например, так, как это показано ниже:

$ sudo fdisk -l /dev/sda 

 …

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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 identifier: 0x000e3147
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    58593279    29295616   83  Linux
/dev/sda2        58595326   625141759   283273217    5  Extended
/dev/sda5        58595328   373270527   157337600   83  Linux
/dev/sda6       615235584   625141759     4953088   82  Linux swap / Solaris
/dev/sda7       373272576   615225239   120976332   83  Linux
Partition table entries are not in disk order

Как видно, раздел /dev/sda7 на самом деле расположен между /dev/sda5 и /dev/sda6.

В принципе, это не критично. Однако, если вы всё же хотите восстановить правильный порядок разделов, надо выполнить следующие простые действия:

1) Запускаем fdisk для требуемого раздела

$ sudo fdisk /dev/sda

2) Включаем расширенные команды:

Command (m for help): x

3) Правим порядок:

4) Записываем изменения на диск:

Собственно, всё, порядок разделов исправлен:

Для чистоты эксперимента, я смело могу удалять всё, кроме sda1.

Для начала отключим существующий swap (для начала проверим состояние):

> cat /proc/swaps

Filename                                Type            Size    Used    Priority

/dev/sda5                               partition       731128  0       -1

Удаляем из файла /etc/fstab строку:
UUID=4771bdd4-e219-4b8f-920a-9d5460b47ff6 none            swap    sw              0       0

Удаляем разделы:

> sudo fdisk  /dev/sda 

WARNING: DOS-compatible mode is deprecated. It’s strongly recommended to

         switch off the mode (command ‘c’) and change display units to

         sectors (command ‘u’).

Command (m for help): c

DOS Compatibility flag is not set

Command (m for help): u

Changing display/entry units to sectors

Command (m for help): d

Partition number (1-5): 2

Command (m for help): d

Partition number (1-4): 3

Command (m for help): p

Disk /dev/sda: 17.2 GB, 17179869184 bytes

255 heads, 63 sectors/track, 2088 cylinders, total 33554432 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 identifier: 0x00049f1f

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *        2048     4220927     2109440   83  Linux

Syncing disks.

Обратите внимание, что я установил тип раздела 8e (Linux LVM).

Теперь необходимо установить ПО для работы с LVM:

> sudo aptitude install lvm2

Следующие НОВЫЕ пакеты будут установлены:        

  lvm2 

0 пакетов обновлено, 1 установлено новых, 0 пакетов отмечено для удаления, и 0 пакетов не обновлено.

Необходимо получить 448 kB архивов. После распаковки 1 077 kB будет занято.

Получено 448 kБ в 1с (309 kБ/с)

Выбор ранее не выбранного пакета lvm2.

(Чтение базы данных … на данный момент установлено 39064 файла и каталога.)

Распаковывается пакет lvm2 (из файла …/lvm2_2.02.66-5_amd64.deb)…

Обрабатываются триггеры для man-db …

Настраивается пакет lvm2 (2.02.66-5) …

Setting up LVM Volume Groups  Reading all physical volumes.  This may take a while…

  No volume groups found

  No volume groups found

  No volume groups found

.

update-initramfs: deferring update (trigger activated)

Обрабатываются триггеры для initramfs-tools …

Но при этом у нас осталось почти 5 Гб неразмеченного пространства. LVM позволяет гибко изменять разделы томов, т.ч. оставлю его в резерве.

Форматируем разделы:

> sudo mkfs.ext4 /dev/server/home

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

131072 inodes, 524288 blocks

26214 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=536870912

16 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376, 294912

Writing inode tables: done                            

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

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

65536 inodes, 262144 blocks

13107 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=268435456

8 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376

Writing inode tables: done                            

Creating journal (8192 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

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

131072 inodes, 524288 blocks

26214 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=536870912

16 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376, 294912

Writing inode tables: done                            

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

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

65536 inodes, 262144 blocks

13107 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=268435456

8 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376

Writing inode tables: done                            

Creating journal (8192 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 34 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

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

131072 inodes, 524288 blocks

26214 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=536870912

16 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376, 294912

Writing inode tables: done                            

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

no label, UUID=13ad3312-8b76-4018-8e3e-6cbbc94a807f

Мне пришлось использовать аргумент -f, т.к. вылезает ошибка «warning: don’t erase bootbits sectors on whole disk.».

В результате мы получили тома со следующими идентификаторами:

> sudo blkid 

/dev/sda1: UUID=»653ac5dc-ea55-4c75-be36-e54e26d078e1″ TYPE=»ext3″ 

/dev/sda2: UUID=»mkkLen-vzQr-KFRA-rJCe-h4dw-Irj8-GIfNsi» TYPE=»LVM2_member» 

/dev/mapper/server-swap: UUID=»13ad3312-8b76-4018-8e3e-6cbbc94a807f» TYPE=»swap» 

/dev/mapper/server-tmp: UUID=»19ab2a02-6ff2-4870-b834-f0c992f577d2″ TYPE=»ext4″ 

/dev/mapper/server-root: UUID=»854a4bc0-eb17-4639-b298-35f3367cbc83″ TYPE=»ext4″ 

/dev/mapper/server-home: UUID=»f971ccfb-4391-4ad0-bf49-885406800783″ TYPE=»ext4″ 

/dev/mapper/server-usr: UUID=»13e6e8a9-4aa8-467c-8995-fe3d52f1f8c6″ TYPE=»ext4″ 

/dev/mapper/server-srv: UUID=»b178a220-5548-44e6-ac81-4d7ec5dd1373″ TYPE=»ext4″

swapon: /dev/mapper/server-swap: pagesize=4096, swapsize=1073741824, devsize=1073741824

Смотрим, что получилось:

> cat /proc/swaps

Filename                                Type            Size    Used    Priority

/dev/dm-0                               partition       1048568 0       -1

• 
• Forum
• The Ubuntu Forum Community
• Ubuntu Official Flavours Support
• New to Ubuntu
• [SOLVED] Partition table entries are not in disk order=?Problem

1. Partition table entries are not in disk order=?Problem
   

   Hello everyone,

   Just did a sudo fdisk -l of my newly installed OS. I had manually configured the partitions with the Live CD install to allow for my /home to be on it’s own partition. The included screenshot of same indicates that my Partition table entries are not in disk order. Is this something I should correct? Can I expect problems with the partitioning as it is? If so, what should I do?

   I must go to bed, and will not be available for answering of questions immediately. Sorry.

   Thank you.

   Last edited by mikodo; August 29th, 2009 at 10:57 AM.

   ---

2. Re: Partition table entries are not in disk order=?Problem
   

   It is not a problem. You can «reset» them to the correct order but you would need to check your grub menu and fstab in case there were any references to «sdXX» instead of to UUIDs. The reason is at least two of the partition «sdXX» designations would change after you ‘reset’ them.

   For those wishing to do so, here is the procedure. Note that your system will operate fine without making this change and you run the risk of screwing up your boot process or partition mounting if the partition designations no longer match in fstab or menu.lst:

   Code:

   sudo fdisk /dev/sda

   at the prompt:
   m (for help)
   at the prompt:
   x (extra functionality — experts only)
   f (fix)
   w (write to disk and exit)
   You may get a warning that devices are in use and the new table will be used at the next boot.
   Check fstab and menu.lst before rebooting.
   Repeat for other drives.

   Last edited by drs305; August 29th, 2009 at 11:01 AM.

   ---

3. Re: Partition table entries are not in disk order=?Problem
   

   Here’s a screeshot of Gparted showing the partitions set up.

   ---

4. Re: Partition table entries are not in disk order=?Problem
   

   Originally Posted by drs305
   

   It is not a problem. You can «reset» them to the correct order but you would need to check your grub menu and fstab in case there were any references to «sdXX» instead of to UUIDs. The reason is at least two of the partition «sdXX» designations would change after you ‘reset’ them.

   For those wishing to do so, here is the procedure. Note that your system will operate fine without making this change and you run the risk of screwing up your boot process or partition mounting if the partition designations no longer match in fstab or menu.lst:

   Code:

   sudo fdisk /dev/sda

   at the prompt:
   m (for help)
   at the prompt:
   x (extra functionality — experts only)
   f (fix)
   w (write to disk and exit)
   You may get a warning that devices are in use and the new table will be used at the next boot.
   Check fstab and menu.lst before rebooting.
   Repeat for other drives.

   Wow, thanks for the quick and detailed explanation. This is stuff that is not something I will attempt as a Newbie, especially that you were kind enough to assure me twice in response that it is not a problem and the system would operate fine as it is. For those with similar configurations and knowledge and skill to follow the posters advice, have at it, if you wish. He is obviously an expert.

   Thank you,

   mikodo

   ---

5. Re: Partition table entries are not in disk order=?Problem
   

   Hello.

   Just some additional notes:

   You may only have 4 primary partitions, so if you set up your partition table with only 3 primary partitions and one of them as an extended, this will always be out of order.

   Your dmesg should also show how your current set up looks like.

   Basically it doesnt really matter if they’re out of order, just add labels to all your partitions and you can easily access them.

   Just, why the good god do you have a 8GB swap partition?

   o.O

   I assume your PC is quite young, so swappoff and do something useful with the space.

   It won’t render your system unstable if you swap off, so you could do this live, resize the swap partition to like 1GB max, and then go for whatever comes to your mind with the freed space.

   ---

6. Re: Partition table entries are not in disk order=?Problem
   

   Originally Posted by drs305
   

   It is not a problem. You can «reset» them to the correct order but you would need to check your grub menu and fstab in case there were any references to «sdXX» instead of to UUIDs. The reason is at least two of the partition «sdXX» designations would change after you ‘reset’ them.

   For those wishing to do so, here is the procedure. Note that your system will operate fine without making this change and you run the risk of screwing up your boot process or partition mounting if the partition designations no longer match in fstab or menu.lst:

   Code:

   sudo fdisk /dev/sda

   at the prompt:
   m (for help)
   at the prompt:
   x (extra functionality — experts only)
   f (fix)
   w (write to disk and exit)
   You may get a warning that devices are in use and the new table will be used at the next boot.
   Check fstab and menu.lst before rebooting.
   Repeat for other drives.

   Hello; It still is bothering me that my Partition table entries are not in order. Do the screenshots of my fstab and grub menu indicate that it is safe to run the above quoted code to fix them?

   Thank you.

   ---

7. Re: Partition table entries are not in disk order=?Problem
   

   Hello everyone,

   I went ahead and run the above code, and now my Partition table entries are in order. Please see screenshot of same.

   Thank you all.

   ---

8. Re: Partition table entries are not in disk order=?Problem
   

   Originally Posted by mikodo
   

   Hello everyone,

   I went ahead and run the above code, and now my Partition table entries are in order. Please see screenshot of same.

   Thank you all.

   Glad it worked out. In checking those two files, what I would have looked for is any «sdXX» entry, such as sda5, instead of the (now) expected UUIDs. If everything is referenced by UUID, then the command won’t create any boot or mount issues.

   ---

9. Re: Partition table entries are not in disk order=?Problem
   

   Originally Posted by drs305
   

   For those wishing to do so, here is the procedure.

   FWIW, when only logical partitions are out of order, my FixParts program does this automatically — just launch the program and type «w» to save the changes. (It’s always wise to verify you’re working on the right disk by typing «p» to check the partitions, though. This also lets you verify that the partitioning tool has correctly read all the partitions.)

   Originally Posted by drs305
   

   It is not a problem.

   I’d like to reiterate this point, and add that there’s always a risk of damage when messing with partition tables. I know that mikodo has done the modification without problems, but an error (user error, a bug in a program, a power failure at exactly the wrong moment, etc.) can cause the partition definitions to be lost, and that will take a lot of effort to correct. It’s just not worth the risk for something like this. Note that there’s no «IMHO» in that statement.

   Originally Posted by loomsen

   You may only have 4 primary partitions, so if you set up your partition table with only 3 primary partitions and one of them as an extended, this will always be out of order.

   Not quite; with that setup, there will necessarily be a gap in the numbering, but the partitions that are there can be in order.

   Originally Posted by loomsen

   Your dmesg should also show how your current set up looks like.

   The dmesg command displays the kernel ring buffer, which contains messages generated by the kernel. Mostly these relate to hardware detection and errors. Among many other things, these messages will show you how many partitions you’ve got and how they’re numbered, but they won’t say anything about partition sizes. For instance:

   Code:

   [    5.499096] sd 1:0:1:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
   [    5.499129] sd 1:0:1:0: [sdb] Write Protect is off
   [    5.499131] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
   [    5.499149] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
   [    5.499235]  sdb: sdb1 sdb2 sdb3

   That last line indicates the disk has three partitions, /dev/sdb1 through /dev/sdb3. (On a disk with extended and logical partitions, that arrangement is indicated, IIRC.) There’s nothing there about partition sizes or types. For such information, you’ve got to use a partitioning tool like fdisk, parted, GParted, or gdisk.

   Originally Posted by aj_84@live.co.uk

   can you help me how to put this in order, i have three primary partition and one extended partition. I just want to get the linux versions together.

   Your Linux partitions are contiguous in on-disk space; the last two (your logical partitions) are just out of order in their numbering sequence. This is unimportant, and as I wrote earlier, changing your partitions just to «fix» this is inadvisable. Basically, your disk isn’t broken, and there’s wisdom to the saying, «if it ain’t broke, don’t fix it.»

   FWIW and for future reference, it’s generally best to put a swap partition in-between Linux partitions (in terms of actual partition sectors, not necessarily the partition numbers). This minimizes head seek movements when accessing swap space, thus improving performance. Since swap space is rarely used today, though, I wouldn’t advise trying to change your existing configuration; you’ll spend more time trying to improve performance than you could possibly save by optimizing your swap file placement, and you’ll run the risk of creating bigger problems. It’s just something to keep in mind for the next time you partition a disk.

   If I’ve suggested a solution to a problem and you’re not the original poster, do not try my solution! Problems can seem similar but be different, and a good solution to one problem can make another worse. Post a new thread with your problem details.

   ---

Tags for this Thread

#1 2020-03-05 22:03:41

Partition table entries are not in disk order.

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p9
UUID=b177476c-53c0-4a8f-bac2-3955040ce0b3	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p7
UUID=B26C-A1E5      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p10
UUID=a25a996b-c90a-4597-9fb6-cdaa2ebf6de3	/home     	ext4      	rw,relatime	0 2

# /dev/nvme0n1p8
UUID=3915a4f1-d3de-4ada-964a-09fef8733b5f	none      	swap      	defaults  	0 0

menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b177476c-53c0-4a8f-bac2-3955040ce0b3' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod fat
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root  B26C-A1E5
	else
	  search --no-floppy --fs-uuid --set=root B26C-A1E5
	fi
	echo	'Loading Linux linux ...'
	linux	/vmlinuz-linux root=UUID=b177476c-53c0-4a8f-bac2-3955040ce0b3 rw  intel_iommu=on video=1920x1080 resume=UUID=3915a4f1-d3de-4ada-964a-09fef8733b5f verbose
	echo	'Loading initial ramdisk ...'
	initrd	/intel-ucode.img /initramfs-linux.img
}

#2 2020-03-05 22:49:13

#3 2020-03-06 09:23:21

#4 2020-03-06 09:26:19

• Печать

Тема: Проблемы с жестким диском  (Прочитано 1950 раз)

symon2014

symon2014

symon2014

• Печать