[PowerEdge T610] Error installing base system on natty server

Bug #711938 reported by Marc Legris
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Tim Gardner
Natty
Fix Released
High
Tim Gardner

Bug Description

Binary package hint: debian-installer

During our weekly testing in the certification servers one of the servers failed to install the base systems.

Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/progress/fallback
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 base-installer: mkdir: can't create directory '/target/etc/': Read-only file system
Feb 1 18:18:44 base-installer: warning: /usr/lib/base-installer.d/05udev returned error code 1
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/progress/console-setup
Feb 1 18:18:44 debconf: <-- 10 base-installer/progress/console-setup does not exist
Feb 1 18:18:44 debconf: --> SUBST base-installer/progress/fallback SCRIPT console-setup
Feb 1 18:18:44 debconf: Adding [SCRIPT] -> [console-setup]
Feb 1 18:18:44 debconf: <-- 0
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/progress/fallback
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 base-installer: mkdir: can't create directory '/target/etc/': Read-only file system
Feb 1 18:18:44 base-installer: warning: /usr/lib/base-installer.d/20console-setup returned error code 1
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/progress/netcfg
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 base-installer: mkdir: can't create directory '/target//etc/': Read-only file system
Feb 1 18:18:44 base-installer: warning: /usr/lib/base-installer.d/40netcfg returned error code 1
Feb 1 18:18:44 debconf: --> PROGRESS SET 3
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/section/install_base_system
Feb 1 18:18:44 debconf: <-- 10 base-installer/section/install_base_system does not exist
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/progress/preparing
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 debconf: --> GET debian-installer/allow_unauthenticated
Feb 1 18:18:44 debconf: <-- 0 true
Feb 1 18:18:44 main-menu[473]: (process:26552): mkdir: can't create directory '/target/etc': Read-only file system
Feb 1 18:18:44 main-menu[473]: WARNING **: Configuring 'bootstrap-base' failed with error code 1
Feb 1 18:18:44 debconf: --> GET debconf/priority
Feb 1 18:18:44 debconf: <-- 0 high
Feb 1 18:18:44 main-menu[473]: WARNING **: Menu item 'bootstrap-base' failed.
Feb 1 18:18:44 debconf: --> SETTITLE debian-installer/bootstrap-base/title
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 debconf: --> CAPB
Feb 1 18:18:44 debconf: <-- 0 multiselect backup progresscancel align plugin-terminal plugin-detect-keyboard
Feb 1 18:18:44 debconf: --> METAGET debian-installer/bootstrap-base/title Description
Feb 1 18:18:44 debconf: <-- 0 Install the base system
Feb 1 18:18:44 debconf: --> SUBST debian-installer/main-menu/item-failure ITEM Install the base system
Feb 1 18:18:44 debconf: Adding [ITEM] -> [Install the base system]
Feb 1 18:18:44 debconf: <-- 0
Feb 1 18:18:44 debconf: --> INPUT critical debian-installer/main-menu/item-failure
Feb 1 18:18:44 debconf: <-- 0 question will be asked
Feb 1 18:18:44 debconf: --> GO

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
affects: grub-installer (Ubuntu) → debian-installer (Ubuntu)
description: updated
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

Feb 1 17:58:49 kernel: [ 174.354955] mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Feb 1 17:58:49 kernel: [ 174.354969] sd 2:0:0:0: [sda] Unhandled error code
Feb 1 17:58:49 kernel: [ 174.354972] sd 2:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 1 17:58:49 kernel: [ 174.354977] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 45 2d b8 00 00 20 00
Feb 1 17:58:49 kernel: [ 174.354988] end_request: I/O error, dev sda, sector 4533688
Feb 1 17:58:49 kernel: [ 174.355016] Aborting journal on device sda1-8.
Feb 1 17:58:49 kernel: [ 174.359209] end_device-2:0: mptsas: ioc0: removing ssp device: fw_channel 0, fw_id 0, phy 0,sas_addr 0x500000e113c500b2
Feb 1 17:58:49 kernel: [ 174.359214] phy-2:0: mptsas: ioc0: delete phy 0, phy-obj (0xf47eca00)
Feb 1 17:58:49 kernel: [ 174.359226] port-2:0: mptsas: ioc0: delete port 0, sas_addr (0x500000e113c500b2)
Feb 1 17:58:49 debootstrap: dpkg: unrecoverable fatal error, aborting:
Feb 1 17:58:49 debootstrap: unable to sync directory '/var/lib/dpkg/updates/': Input/output error
Feb 1 17:58:49 kernel: [ 174.359382] JBD2: I/O error detected when updating journal superblock for sda1-8.
Feb 1 17:58:49 kernel: [ 174.359476] journal commit I/O error
Feb 1 17:58:49 kernel: [ 174.360592] EXT4-fs error (device sda1): ext4_journal_start_sb:258: Detected aborted journal
Feb 1 17:58:49 kernel: [ 174.360597] EXT4-fs (sda1): Remounting filesystem read-only

It all goes wrong from there on in. Looks like a kernel problem to me.

affects: debian-installer (Ubuntu) → linux (Ubuntu)
Revision history for this message
Colin Watson (cjwatson) wrote :

(Or possibly a hardware problem, of course.)

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Triaged
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Marc - mptsas is definitely unhappy. While possible that its an mptsas driver error, do you know if a Maverick install works, and have you ever installed anything on this machine ?

mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 45 2d b8 00 00 20 00
end_request: I/O error, dev sda, sector 4533688
Aborting journal on device sda1-8.
end_device-2:0: mptsas: ioc0: removing ssp device: fw_channel 0, fw_id 0, phy 0,sas_addr 0x500000e113c500b2
phy-2:0: mptsas: ioc0: delete phy 0, phy-obj (0xf47eca00)
port-2:0: mptsas: ioc0: delete port 0, sas_addr (0x500000e113c500b2)
F

Changed in linux (Ubuntu Natty):
assignee: nobody → Tim Gardner (timg-tpi)
status: Triaged → In Progress
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

@Tim

This machine has had lucid, maverick and natty successfully installed.

summary: - Error installing base system on natty server
+ [PowerEdge T610] Error installing base system on natty server
Revision history for this message
Tim Gardner (timg-tpi) wrote :

I presume you mean that it has had successful installs _since_ it failed to install Natty? Is it still failing to install Natty?

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Correct, it was able to successfully install on Apr 11th.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Exactly _what_ version were you able to successfully install?

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

The system was able to install the 20110329.2 natty image

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Seems fixed according to comment #10

Changed in linux (Ubuntu Natty):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.