[PowerEdge T610] Error installing base system on natty server
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/
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/
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/
Feb 1 18:18:44 debconf: <-- 10 base-installer/
Feb 1 18:18:44 debconf: --> SUBST base-installer/
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/
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/
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/
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/
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/
Feb 1 18:18:44 debconf: <-- 10 base-installer/
Feb 1 18:18:44 debconf: --> PROGRESS INFO base-installer/
Feb 1 18:18:44 debconf: <-- 0 OK
Feb 1 18:18:44 debconf: --> GET debian-
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-
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-
Feb 1 18:18:44 debconf: --> METAGET debian-
Feb 1 18:18:44 debconf: <-- 0 Install the base system
Feb 1 18:18:44 debconf: --> SUBST debian-
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-
Feb 1 18:18:44 debconf: <-- 0 question will be asked
Feb 1 18:18:44 debconf: --> GO
tags: | added: kj-triage |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Feb 1 17:58:49 kernel: [ 174.354955] mptbase: ioc0: LogInfo( 0x31140000) : Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done DID_NO_ CONNECT driverbyte= DRIVER_ OK 00b2) dpkg/updates/ ': Input/output error start_sb: 258: Detected aborted journal
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=
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 (0x500000e113c5
Feb 1 17:58:49 debootstrap: dpkg: unrecoverable fatal error, aborting:
Feb 1 17:58:49 debootstrap: unable to sync directory '/var/lib/
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_
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.