The issue tracker has been moved https://gitlab.archlinux.org/archlinux/archiso/-/issues
FS#13402 - Boot fails on Lenovo S10
Attached to Project:
Release Engineering
Opened by Rafael Hart (zen_cat) - Saturday, 21 February 2009, 11:47 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 24 February 2009, 23:13 GMT
Opened by Rafael Hart (zen_cat) - Saturday, 21 February 2009, 11:47 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 24 February 2009, 23:13 GMT
|
DetailsHope this is actually a bug and not me being useless - On an S10 Lenovo laptop the boot fails, crashing to ramfs after attempting to find a boot disk and trying to load /media/sr0. MD5SUM for the CD was checked, and the CD can boot another laptop. This is using a USB cdrom drive. The 2008 release works fine, and that is what I'm using at the moment. What checks can I do to provide useful information?
|
This task depends upon
Closed by Aaron Griffin (phrakture)
Tuesday, 24 February 2009, 23:13 GMT
Reason for closing: Fixed
Additional comments about closing: Increase usbdelay
Tuesday, 24 February 2009, 23:13 GMT
Reason for closing: Fixed
Additional comments about closing: Increase usbdelay
scsi 2:0:0:0: CD-ROM Optiarc DVD RW AD-7200A 1.06 PQ: 0 ANSI: 0
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
:: Scanning for boot device...
:: Scanning cd drives...
scsi 3:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CSS
sd 3:0:0:0: [sdb] Attached SCSI removable disk
Failed to mount /dev/sr0
:: Scanning usb drives...
EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2
attempt to access beyond end of device
sda2: rw=0, want=4, limit=2
EXT2-fs: unable to read superblock
Failed to mount /dev/sda2
Failed to mount /dev/sda5
ERROR: cannot find boot device, cannot continue...
Falling back to interactive prompt
ramfs$
It seems like you have an invalid ext2 FS somewhere.
@Aaron do we do automounting of any filesystems somewhere?
Hmmm...
Is it usb attached? Perhaps try adding a usbdelay=10 entry or something.... maybe it needs more time to spin up