在分割磁盘分区时,遭受错误“WA途乐NING: Re-reading the partition table
failed with error 22: Invalid argument” 如下所示:

WARNING: Re-reading the partition table failed with error 22: Invalid argument,re-readingargument

在划分磁盘分区时,遭受错误“WAENCORENING: Re-reading the partition table
failed with error 22: Invalid argument” 如下所示:

[[email protected] u02]# fdisk -l

 

Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1          13      104391   83  Linux

/dev/sda2              14       60801   488279610   8e  Linux LVM

[[email protected] u02]# fdisk /dev/sda2

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

 

 

The number of cylinders for this disk is set to 60788.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

 

Command (m for help): m

Command action

   a   toggle a bootable flag

   b   edit bsd disklabel

   c   toggle the dos compatibility flag

   d   delete a partition

   l   list known partition types

   m   print this menu

   n   add a new partition

   o   create a new empty DOS partition table

   p   print the partition table

   q   quit without saving changes

   s   create a new empty Sun disklabel

   t   change a partition's system id

   u   change display/entry units

   v   verify the partition table

   w   write table to disk and exit

   x   extra functionality (experts only)

 

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 2

First cylinder (1-60788, default 1): 

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-60788, default 60788): 

Using default value 60788

 

Command (m for help): w

The partition table has been altered!

 

Calling ioctl() to re-read partition table.

 

WARNING: Re-reading the partition table failed with error 22: Invalid argument.

The kernel still uses the old table.

The new table will be used at the next reboot.

轻松学会硬盘安装双系统,U盘自动布署报错化解办法之二。 

 

并发那几个错误,是因为尚未在使得的装备(valid
device)上拓展分区操作(太久没有玩这台测试服务器了,忘记当初怎么着划分存款和储蓄,测试三个备份的进度急于必要磁盘空间,没有检查意况,就动手了),实际上那一个分区类型为
Linux LVM。已经划给VolGroup00了。后续处理如下。

 

[[email protected] ~]# pvscan

  PV /dev/sda2   VG VolGroup00   lvm2 [465.66 GB / 413.94 GB free]

  Total: 1 [465.66 GB] / in use: 1 [465.66 GB] / in no VG: 0 [0   ]

[[email protected] ~]# lvscan

  ACTIVE            '/dev/VolGroup00/LogVol00' [45.97 GB] inherit

  ACTIVE            '/dev/VolGroup00/LogVol01' [5.75 GB] inherit

[[email protected] ~]# more /etc/fstab 

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1

LABEL=/boot             /boot                   ext3    defaults        1 2

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0

[[email protected] ~]# vgdisplay

  --- Volume group ---

  VG Name               VolGroup00

  System ID             

  Format                lvm2

  Metadata Areas        1

  Metadata Sequence No  3

  VG Access             read/write

  VG Status             resizable

  MAX LV                0

  Cur LV                2

  Open LV               2

  Max PV                0

  Cur PV                1

  Act PV                1

  VG Size               465.66 GB

  PE Size               32.00 MB

  Total PE              14901

  Alloc PE / Size       1655 / 51.72 GB

  Free  PE / Size       13246 / 413.94 GB

  VG UUID               EYKFmq-O1Ko-0z94-Os3P-AKfC-0bG9-9oTQDh

   

[[email protected] ~]# lvextend -L 80G /dev/VolGroup00/LogVol00

  Extending logical volume LogVol00 to 80.00 GB

  Logical volume LogVol00 successfully resized

[[email protected] ~]# resize2fs /dev/VolGroup00/LogVol00

resize2fs 1.39 (29-May-2006)

Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required

Performing an on-line resize of /dev/VolGroup00/LogVol00 to 20971520 (4k) blocks.

The filesystem on /dev/VolGroup00/LogVol00 is now 20971520 blocks long.

 

[[email protected] ~]# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/mapper/VolGroup00-LogVol00

                       78G   32G   42G  44% /

/dev/sda1              99M   13M   82M  14% /boot

tmpfs                 1.9G 1023M  916M  53% /dev/shm

/tmp/rhel-server-5.7-x86_64-dvd.iso

                      3.6G  3.6G     0 100% /mnt/cdrom

[[email protected] ~]# 

 

: Re-reading the partition table failed
with error 22: Invalid argument,re-readingargument
在分割磁盘分区时,遭受错误“WA陆风X8NING: Re-reading the partition
tabl…

于今无数人都在用双系统,本文也钻探了一下硬盘安装双系统难点,首借使比较流行的四个系统安装给我们解析一下,三个系统一分配别是Windows和Linux双系统,希望读者能从硬盘安装双系统进程与总计中学到经验。

 
继续此前使用MDT制作的U盘进行自动化布置的话题,以前早已介绍了计划进程中因为职责种类难题造成报错的八个消除措施,之后又遇见了一种MDT安排时报错的题材,今天来介绍一下化解办法

[root@DB-Server u02]# fdisk -l

 

Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1          13      104391   83  Linux

/dev/sda2              14       60801   488279610   8e  Linux LVM

[root@DB-Server u02]# fdisk /dev/sda2

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

 

 

The number of cylinders for this disk is set to 60788.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

 

Command (m for help): m

Command action

   a   toggle a bootable flag

   b   edit bsd disklabel

   c   toggle the dos compatibility flag

   d   delete a partition

   l   list known partition types

   m   print this menu

   n   add a new partition

   o   create a new empty DOS partition table

   p   print the partition table

   q   quit without saving changes

   s   create a new empty Sun disklabel

   t   change a partition's system id

   u   change display/entry units

   v   verify the partition table

   w   write table to disk and exit

   x   extra functionality (experts only)

 

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 2

First cylinder (1-60788, default 1): 

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-60788, default 60788): 

Using default value 60788

 

Command (m for help): w

The partition table has been altered!

 

Calling ioctl() to re-read partition table.

 

WARNING: Re-reading the partition table failed with error 22: Invalid argument.

The kernel still uses the old table.

The new table will be used at the next reboot.

壹 、先把硬盘分区,安装Windows系统。之后把Linux系统装在倒数第四个分区上30G),最终3个分区10G)用来做LFS。

澳门金沙国际, 
首先来叙述一下标题标具体景况,在选拔MDT进行布局时,发现有分别机器会提醒faied
to apply
image的谬误,那是三个很意外的意况,因为唯有极个其余机器出现了那一个标题,那是为啥吧?测试发现采取互连网计划时也会唤醒那个题材,而且报错的新闻也是同样的,那表达并不是多少个偶发现象,肯定还存在着无人问津的局地原因。

 

设置达成后重新启航,运转停在grub不能够进入

 
之后采用了最原始的U盘安装的方法展开了测试,发现此次的布署是没非凡的,那么自然不是机械的原故了,之后作者仔细回看了瞬间难题的最首要,突然想起从前在这台机器上捕获镜像时,选取的磁盘分区是D盘,一下子醒来,看来难题的重中之重应该是在100M分区了,在PE环境下,这些100M分区被分了C盘的盘符,而笔者辈定义的布局策略是哪些分区是C盘就装在哪个分区上,这样操作系统就会被安装到100M分区上了,不过因为磁盘空间过小的标题,安装肯定是没戏的,之后作者进去PE环境查看了100M分区的可用空间,发现可用空间改为了0M,也印证了本身的视角,之后笔者将100M分区删除后,重新进行了测试,本次的配备没有出现别的难题。看来那也是现在的方案中必要创新的一些,对于有100M分区的机械,操作系统的布局有也许会战败,但自作者印象中记得有个别机器尽管有100M分区,在破获镜像的时候选择的也是C盘,也就意味着着100M分区没有被划分盘符,对于那种机械,MDT的自动布署是足以成功的,可是简单的说,在有100M分区的机器上拓展活动布置还是有挫折的恐怕的,那也是还索要通盘的地点。

澳门金沙国际 1

案由剖析:可能因为grub无法识别160G硬盘1024柱面以往的内容。

 别的还有一些要提的正是,MDT安排形成后,进入操作系统还会举行一套相关的剧本,大约内容是还原在此以前捕获的用户数据,安装使用,应用组策略等,在那些历程中会在C盘建立二个SMS初步的权且文件夹,在那么些进度中必定要注意千万不要拔掉U盘只怕网线,一定要让这一套脚本实施实现,不然MDT会始终认为安插还尚无到头到位,C盘下的权且文件夹也不会被删去,大概造成的难题不怕,之后再进来系统会一贯弹出插入U盘的窗口,并且不能关闭,而且还会油然则生再选用MDT自动计划时,选用完任务系列之后会直接闪退重启系统,这么些都以因为上三遍配置时脚本没有到头完毕导致的,所以必然要让总体安排进度彻底到位,C盘下的权且文件夹被自动删除再拔掉U盘或许网线

 

② 、又想把Linux系统安装在其次个分区上,未来第2个分区为30G,作者想把他分成20G+10G,20G装Linux系统,10G做LFS)

并发那几个荒唐,是因为从没在使得的装备(valid
device)上拓展分区操作(太久没有玩那台测试服务器了,忘记当初怎么着划分存款和储蓄,测试三个备份的进度急于须要磁盘空间,没有检查意况,就起先了),实际上那些分区类型为
Linux LVM。已经划给VolGroup00了。后续处理如下。

于是乎,在磁盘管理里,把第②块扩丰裕区删掉,重新创制了20G+10G的恢宏分区;此时XP系统将20G分区的盘符设为D,10G盘符设为终极贰个盘符。思疑不平常了)

 

叁 、重启,硬盘安装Linux,装完重新指导,又停在grub,此时在输入root
(hd0,_)时,用Tab键补齐时,无法甄别出Linux的ext3及swap格式分区,此时试过又Linux的kernel硬盘携带起来,修复grub,但不算,认为是grub太低无法平常识别160G硬盘的标题,在网上再度下载新本子的grub在DOS下运营,均出现和原先一样症状。

[root@DB-Server ~]# pvscan

  PV /dev/sda2   VG VolGroup00   lvm2 [465.66 GB / 413.94 GB free]

  Total: 1 [465.66 GB] / in use: 1 [465.66 GB] / in no VG: 0 [0   ]

[root@DB-Server ~]# lvscan

  ACTIVE            '/dev/VolGroup00/LogVol00' [45.97 GB] inherit

  ACTIVE            '/dev/VolGroup00/LogVol01' [5.75 GB] inherit

[root@DB-Server ~]# more /etc/fstab 

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1

LABEL=/boot             /boot                   ext3    defaults        1 2

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0

[root@DB-Server ~]# vgdisplay

  --- Volume group ---

  VG Name               VolGroup00

  System ID             

  Format                lvm2

  Metadata Areas        1

  Metadata Sequence No  3

  VG Access             read/write

  VG Status             resizable

  MAX LV                0

  Cur LV                2

  Open LV               2

  Max PV                0

  Cur PV                1

  Act PV                1

  VG Size               465.66 GB

  PE Size               32.00 MB

  Total PE              14901

  Alloc PE / Size       1655 / 51.72 GB

  Free  PE / Size       13246 / 413.94 GB

  VG UUID               EYKFmq-O1Ko-0z94-Os3P-AKfC-0bG9-9oTQDh

   

[root@DB-Server ~]# lvextend -L 80G /dev/VolGroup00/LogVol00

  Extending logical volume LogVol00 to 80.00 GB

  Logical volume LogVol00 successfully resized

[root@DB-Server ~]# resize2fs /dev/VolGroup00/LogVol00

resize2fs 1.39 (29-May-2006)

Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required

Performing an on-line resize of /dev/VolGroup00/LogVol00 to 20971520 (4k) blocks.

The filesystem on /dev/VolGroup00/LogVol00 is now 20971520 blocks long.

 

[root@DB-Server ~]# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/mapper/VolGroup00-LogVol00

                       78G   32G   42G  44% /

/dev/sda1              99M   13M   82M  14% /boot

tmpfs                 1.9G 1023M  916M  53% /dev/shm

/tmp/rhel-server-5.7-x86_64-dvd.iso

                      3.6G  3.6G     0 100% /mnt/cdrom

[root@DB-Server ~]# 

肆 、发生新的想法,把Linux系统安装在主分区,再在扩张分区留10G做LFS,

 

⑤ 、在进入Diskgen举行改动分区时,发现提醒1分区和7分区参数错误。

澳门金沙国际 2

发现错误:

在把第一个分区30G,划分成20G+10G时,Windows划分的分区本人能够辨认。但在DOS和Diskgen和grub中都会发觉分区错误,不识别有误分区。

⑥ 、发现真正的失实原因后,进入Windows磁盘管理器,把资料都翻翻C盘,然后将扩充足区中的逻辑分区全部删掉,再重复分逻辑分区,那样能够保障逻辑分区中的各分区会牢牢相连,不会时有产生分区参数错误。

柒 、经重新分配逻辑分区后,再在其次块分区第壹块逻辑分区)上安装Linux,他自带的grub中写入要修改的选项,重新指导体系,grub运转不荒谬。

双系统运营平常

小结:对分区的操作尽量小心,保障在底部软件不会爆发歧义。

在安装Linux时,报告Dbug的标题:在Windows中为Linux准备好分区后,进入Linux手动分区后。相应的硬盘编号会依据规则变更,将招致错误在开班筹划后提醒错误)。此时只需“确认”,重新进入安装,在这一次进入后,手动分区时,分区内容已存在,只需重新分别选拔格式化
/boot , swap, / ;分区,继续设置,则不会再出错!

梦想经过本文你能学会硬盘安装双系统,那样你就能在你的处理器上利于利用Windows和Linux了。

  1. 教您Open Suse Linux服务器配置格局
  2. 圆满解析Suse Linux通过sun测试
  3. 学前线指挥部导:SUSE Linux
  4. 爱护入微Open Suse与谷歌编制程序之夏项目
  5. 阐述Open SUSE中Jdk,mysql安装

相关文章