[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Anaconda failure during PXE kickstart package install sequence: Read-only Filesystem



Hello –

 

    My PXE install fails about half-way through the installation of the packages with the following: (This is last text on the screen at the point it wants me to Ctrl-Alt-Delete)

 

(First section is remnants from my attempts at printing values at the debug prompt)

 

<error text>

    Error cmd.Cmd.onecmd(self, line)              

  File “/usr/lib64/python2.6/cmd.py”, line 219, in onecmd

    Return func(arg)

  File “/usr/lib64/python2.6/pdb.py”, line 661, in do_run

    Raise Restart

Pdb.Restart

 

Original Exception was:

Traceback (most recent call last):

  File “/usr/lib/anaconda/yuminstall.py”, line 173, in callback

    Self.instLog.flush()

IOError: [Errno 30] Read-only file system

Error: pythin callback <bound method AnacondaCallback.callback of <yuminstall.AnacondaCallback instance at 0x7ff07cc7ea28>> failed, aborting!

Unlink: /mnt/sysimage/var/lib/rpm/__db.002: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.004: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.003: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.001: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.002: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.004: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.003: Read-only file system

Unlink: /mnt/sysimage/var/lib/rpm/__db.001: Read-only file system

Install exited abnormally [1/1]

The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete.

<end error text>

 

Our system: Supermicro X8DTU motherboard x86_64, with 300GB SCSI and 30GB SSD.

RHEL 6.2.

 

This has installed before on this system on SSD only, and it failed yesterday just on a different package.

This is an isolated network (PXE server and this host only) This PXE install did a full drive formatting.

 

I’ve searched google and found no other info on this specific problem.

Any ideas? Any suggestions for action at python debug prompt? (I’m not familiar w/ python, but this seems like a systemic issue rather than py coding error)

 

Thanks

    Sean

 

 

 

 

 

 

Sean Parker

Gromellski & Associates

Office: 703-367-1020

Cell: 703-615-3729

 

 

 

 

 

I've sent you an email as a courtesy so you can open/respond when you have time, I would appreciate the courtesy of a response at all.

 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]