[ale] CentOS 7 install driving me mad

[Boris Borisov]

Mad admin :)

The horror ... the horror ...
On Jun 3, 2016 11:39 AM, "Chris Fowler" <cfowler at outpostsentinel.com> wrote:

> I'm trying to do a custom install of CentOS 7 on i586.
>
> I've started with
> http://vega.sra-tohoku.co.jp/~kabe/linux/c7-i586/pentium.html  and have a
> boot install USB stick
>
> This is the last thing before the device seems to "hang".  I'm struggling
> at this point because I don't really know what it is doing, waiting on, etc.
>
> [ 55.929937] sd 0:0:0:0: [sda] 7142688 512-byte logical blocks: (3.65
> GB/3.40 GiB)
> [ 55.943552] sd 2:0:0:0: [sdb] 15140855 512-byte logical blocks: (7.75
> GB/7.21 GiB)
> [ 55.953168] sd 0:0:0:0: [sda] Write Protect is off
> [ 55.957986] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 55.966454] sd 2:0:0:0: [sdb] Write Protect is off
> [ 55.971338] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
> [ 55.983089] sd 2:0:0:0: [sdb] No Caching mode page found
> [ 55.988454] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [ 55.996853] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled,
> doesn't support DPO or FUA
> [ 56.017750] sda:
> [ 56.023559] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 56.056997] sdb: sdb1
> [ 56.063058] sd 2:0:0:0: [sdb] Attached SCSI removable disk
> [ 56.381233] systemd-journald[81]: no db file to read
> /run/udev/data/+pci:0000:00:01.0: No such file or directory
> [ 56.403093] systemd-journald[81]: no db file to read
> /run/udev/data/+pci:0000:00:01.0: No such file or directory
> [ 56.417404] systemd-journald[81]: no db file to read
> /run/udev/data/+pci:0000:00:01.0: No such file or directory
> [ 56.429521] systemd-journald[81]: no db file to read
> /run/udev/data/+hid:0003:046D:C52B.0003: No such file or directory
> [ 56.441345] systemd-journald[81]: no db file to read
> /run/udev/data/+hid:0003:046D:C52B.0003: No such file or directory
> [ 56.453516] systemd-journald[81]: no db file to read
> /run/udev/data/+pci:0000:00:0c.0: No such file or directory
> [ 56.464649] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:host0: No such file or directory
> [ 56.475340] systemd-journald[81]: no db file to read
> /run/udev/data/+hid:0003:046D:C52B.0005: No such file or directory
> [ 56.487204] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:host1: No such file or directory
> [ 56.498468] systemd-journald[81]: no db file to read
> /run/udev/data/+hid:0003:046D:C52B.0006: No such file or directory
> [ 56.510947] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.521795] systemd-journald[81]: no db file to read
> /run/udev/data/+usb:2-1:1.0: No such file or directory
> [ 56.532498] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:host2: No such file or directory
> [ 56.544694] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.556158] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.567008] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.577789] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.588564] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.599357] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.610230] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.620997] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.631803] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.642607] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.653543] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:0:0:0:0: No such file or directory
> [ 56.664500] systemd-journald[81]: no db file to read
> /run/udev/data/+scsi:2:0:0:0: No such file or directory
> [ 56.700149] systemd[1]:
> sys-devices-pci0000:00-0000:00:0c.0-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
> changed dead -> plugged
> [ 56.790279] systemd[1]:
> dev-disk-by\x2dpath-pci\x2d0000:00:0b.1\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0.device
> changed dead -> plugged
> [ 56.820177] systemd[1]: dev-sdb.device changed dead -> plugged
> [ 57.320128] systemd[1]:
> dev-disk-by\x2dpath-pci\x2d0000:00:0b.1\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart1.device
> changed dead -> plugged
>
> Here is the full log:
>
> https://dl.dropboxusercontent.com/u/2486826/boot.log
>
>
> How can I debug past this point?  Can I use rd.shell to break and try to
> manually run anaconda?
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20160603/e709cf5e/attachment.html>