Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too.
On Mon, 2005-06-06 at 05:35 -0500, Johnny Hughes wrote:
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too. _______________________________________________
BTW ... It might also be either this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149220
or this
Johnny Hughes wrote:
On Mon, 2005-06-06 at 05:35 -0500, Johnny Hughes wrote:
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too. _______________________________________________
BTW ... It might also be either this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149220
or this
No LVM. I therefore do not believe what I encountered is related to those at all. The traceback is rather clear that this is a RAID related issue.
On Tue, 2005-06-07 at 15:12 +0800, Feizhou wrote:
Johnny Hughes wrote:
On Mon, 2005-06-06 at 05:35 -0500, Johnny Hughes wrote:
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too. _______________________________________________
BTW ... It might also be either this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149220
or this
No LVM. I therefore do not believe what I encountered is related to those at all. The traceback is rather clear that this is a RAID related issue.
If you tried the default partition install, it creates LVM volumes. Which is why I suspected that it might be one of those two bugs. I had a similar issue with RHEL ppc that was also RAID only related, so it is probably different.
We will have update one and a new version of anaconda very soon (after upstream provider releases update 1) ... so maybe you can try with that one after CentOS-4.1 is released.
If you can access the alt-f2 console, you can run fdisk manually. I don't know how to do that via VNC or a serial console though.
Johnny Hughes wrote:
On Tue, 2005-06-07 at 15:12 +0800, Feizhou wrote:
Johnny Hughes wrote:
On Mon, 2005-06-06 at 05:35 -0500, Johnny Hughes wrote:
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too. _______________________________________________
BTW ... It might also be either this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149220
or this
No LVM. I therefore do not believe what I encountered is related to those at all. The traceback is rather clear that this is a RAID related issue.
If you tried the default partition install, it creates LVM volumes.
No. I don't. The traceback occured BEFORE I could get Disk Druid. This happens when I click the button for Disk Druid in the partition setup process.
Which is why I suspected that it might be one of those two bugs. I had a similar issue with RHEL ppc that was also RAID only related, so it is probably different.
Or the same.
We will have update one and a new version of anaconda very soon (after upstream provider releases update 1) ... so maybe you can try with that one after CentOS-4.1 is released.
I guess you guys don't fix things inherited from Redhat then? You wait for them to fix them?
If you can access the alt-f2 console, you can run fdisk manually. I don't know how to do that via VNC or a serial console though.
VNC would have been possible...it was with previous versions of anaconda until Redhat decided to remove that option. RH 7.1 GUI installation had it for example.
Johnny Hughes wrote:
On Mon, 2005-06-06 at 16:05 +0800, Feizhou wrote:
Has anybody encountered this problem?
I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4.
I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through VNC.
Once I reach a part that touchs disk, the process will stop and end up with:
Traceback (most recent call last): File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitioning.py", line 54, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partitions.py", line 140, in setFromDisk diskset.startAllRaid() File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/partedUtils.py", line 542, in startAllRaid DiskSet.mdList.extend(raid.startAllRaid(driveList)) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 106, in startAllRaid mdList = scanForRaid(driveList) File "/var/tmp/anaconda-10.1.1.13//usr/lib/anaconda/raid.py", line 56, in scanForRaid (major, minor, raidSet, level, nrDisks, totalDisks, mdMinor) =\ File "/usr/lib/anaconda/isys.py", line 97, in raidsb return raidsbFromDevice("/tmp/md") File "/usr/lib/anaconda/isys.py", line 103, in raidsbFromDevice rc = _isys.getraidsb(fd) SystemError: (5, 'Input/output error')
I had a similar problem with a ppc install on RHEL. I think (but I am not 100% positive) that it is a LVM1 / LVM2 compatibility issue.
No LVM here. As you can see from the traceback, it is all RAID related.
What I had to do was use fdisk and wipe the partitions and then I recreated them in anaconda using the raid and lvm tools in anaconda.
You don't get good old fdisk via serial console or VNC...it is all crappy disk druid or autopartition. I wish fdisk was still an option...
I have never actually had that problem on CentOS-4, but it is the same code, so I'm sure it happens in C4 too.
well, the thing is, Fedora Core 2 reinstallation was a snap after the botched CentOS 4 installation. kickstart all the way through.
Am Dienstag, den 07.06.2005, 15:10 +0800 schrieb Feizhou:
You don't get good old fdisk via serial console or VNC...it is all crappy disk druid or autopartition. I wish fdisk was still an option...
If you are trying to clean out the partitions anyway, you might try a %pre section in you ks-file. By simply doing something like "dd if=/dev/zero of=/dev/your_whole_disk bs=512 count=5" you can overwrite the first blocks of the disk including its partition-table before anaconda actually starts.
(yes, i know it sucks, but it should work)
Andreas Rogge wrote:
Am Dienstag, den 07.06.2005, 15:10 +0800 schrieb Feizhou:
You don't get good old fdisk via serial console or VNC...it is all crappy disk druid or autopartition. I wish fdisk was still an option...
If you are trying to clean out the partitions anyway, you might try a %pre section in you ks-file. By simply doing something like "dd if=/dev/zero of=/dev/your_whole_disk bs=512 count=5" you can overwrite the first blocks of the disk including its partition-table before anaconda actually starts.
(yes, i know it sucks, but it should work)
geez, I thought clearpart --linux in the kickstart file would do that anyway?
Don't forget the --initlabel option to clearpart if you're clearing out all the partitions. I've encountered lots of problems without it.
-Jay
Feizhou wrote:
Andreas Rogge wrote:
Am Dienstag, den 07.06.2005, 15:10 +0800 schrieb Feizhou:
You don't get good old fdisk via serial console or VNC...it is all crappy disk druid or autopartition. I wish fdisk was still an option...
If you are trying to clean out the partitions anyway, you might try a %pre section in you ks-file. By simply doing something like "dd if=/dev/zero of=/dev/your_whole_disk bs=512 count=5" you can overwrite the first blocks of the disk including its partition-table before anaconda actually starts.
(yes, i know it sucks, but it should work)
geez, I thought clearpart --linux in the kickstart file would do that anyway? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Andreas Rogge -
Feizhou -
Hilliard, Jay -
Johnny Hughes