[Dell PowerEdge R810] System fails to install, "debootstrap program exited with an error (return value 1)" and hard disk "changes" its device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Confirmed
|
High
|
Unassigned |
Bug Description
[Dell PowerEdge R810] System fails to install, "debootstrap program exited with an error (return value 1)" and hard disk "changes" its device
System: PowerEdge R810
Ubuntu version: Natty (11.04) amd64 server (image dated 20110426).
I'm doing a network install on this system using Ubuntu Server 11.04. The debian-installer starts and reads the preseed file, starts working, and eventually the screen goes red and a message appears:
Base system installation error
The debootstrap program exited with an error (return value 1).
Check /var/log/syslog or see virtual console 4 for the details.
The interesting part of the log at the end is like this:
May 4 20:22:25 debconf: --> PROGRESS INFO base-installer/
May 4 20:22:25 debconf: <-- 0 OK
May 4 20:22:28 kernel: [ 78.646855] mpt2sas0: log_info(
(... repeat about 100 times ...)
May 4 20:22:29 kernel: [ 79.274759] mpt2sas0: log_info(
May 4 20:22:31 kernel: [ 81.271637] sd 2:0:0:0: [sda] Unhandled error code
May 4 20:22:31 kernel: [ 81.271640] sd 2:0:0:0: [sda] Result: hostbyte=
May 4 20:22:31 kernel: [ 81.271645] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 07 84 0d 90 00 00 08 00
May 4 20:22:31 kernel: [ 81.271655] end_request: I/O error, dev sda, sector 126094736
(... repeat about 100 times ...)
May 4 20:22:31 kernel: [ 81.271665] sd 2:0:0:0: [sda] Unhandled error code
May 4 20:22:31 kernel: [ 81.271667] sd 2:0:0:0: [sda] Result: hostbyte=
May 4 20:22:31 kernel: [ 81.271670] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 07 84 0d 88 00 00 08 00
May 4 20:22:31 kernel: [ 81.275098] end_request: I/O error, dev sda, sector 126097008
May 4 20:22:31 kernel: [ 81.276161] Aborting journal on device sda1-8.
May 4 20:22:31 kernel: [ 81.276184] JBD2: I/O error detected when updating journal superblock for sda1-8.
May 4 20:22:31 kernel: [ 81.276226] EXT4-fs error (device sda1) in ext4_init_
May 4 20:22:31 kernel: [ 81.284184] EXT4-fs (sda1): I/O error while writing superblock
May 4 20:22:31 kernel: [ 81.284188] EXT4-fs (sda1): Remounting filesystem read-only
May 4 20:22:31 kernel: [ 81.284193] EXT4-fs error (device sda1): ext4_journal_
May 4 20:22:31 kernel: [ 81.284200] EXT4-fs (sda1): ext4_da_writepages: jbd2_start: 8192 pages, ino 4194309; err -30
May 4 20:22:31 kernel: [ 81.284221] EXT4-fs error (device sda1): ext4_journal_
May 4 20:22:31 debconf: --> SUBST base-installer/
May 4 20:22:31 debconf: Adding [EXITCODE] -> [1]
May 4 20:22:31 debconf: <-- 0
May 4 20:22:31 debconf: --> INPUT critical base-installer/
May 4 20:22:31 debconf: <-- 0 question will be asked
May 4 20:22:31 debconf: --> GO
May 4 20:22:31 kernel: [ 81.364439] mpt2sas0: removing handle(0x000a), sas_addr(
May 4 20:22:34 kernel: [ 84.589864] scsi 2:0:1:0: Direct-Access WD WD1460BKFG-18P2V D1E4 PQ: 0 ANSI: 6
May 4 20:22:34 kernel: [ 84.589875] scsi 2:0:1:0: SSP: handle(0x000a), sas_addr(
May 4 20:22:34 kernel: [ 84.589881] scsi 2:0:1:0: SSP: enclosure_
May 4 20:22:34 kernel: [ 84.589888] scsi 2:0:1:0: qdepth(254), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
May 4 20:22:34 kernel: [ 84.590782] sd 2:0:1:0: Attached scsi generic sg1 type 0
May 4 20:22:34 kernel: [ 84.592030] sd 2:0:1:0: [sdb] 286749480 512-byte logical blocks: (146 GB/136 GiB)
May 4 20:22:34 kernel: [ 84.594559] sd 2:0:1:0: [sdb] Write Protect is off
May 4 20:22:34 kernel: [ 84.594566] sd 2:0:1:0: [sdb] Mode Sense: 9f 00 10 08
May 4 20:22:34 kernel: [ 84.595757] sd 2:0:1:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
May 4 20:22:34 kernel: [ 84.656609] sdb: sdb1 sdb2 < sdb5 >
May 4 20:22:34 kernel: [ 84.669010] sd 2:0:1:0: [sdb] Attached SCSI disk
It looks like the hard disk disappears from under the installer's feet, and then reappears, in /dev/sdb instead of /dev/sda. So the installer obviously returns an error and stops.
I tried mounting /dev/sdb1 in /target and continuing the installation, but after a short while the same thing happens, and the disk "moves" to /dev/sdc.
This problem did/does not happen with Lucid or Maverick, so it looks like a regression for this system.
I'm attaching partman, syslog and lspci.
Changed in hw-labs: | |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
affects: | hw-labs → blitzortung-tracker |
affects: | blitzortung-tracker → debian-installer |
tags: | added: blocks-hwcert regression |
Just wanted to note that I saw this too earlier, but didn't get a chance to file a bug before I went away.