I'm trying to install Debian on a Lenovo Thinkpad T430. This is not the
first time I install Debian on this machine, no problems earlier. The
problem is that the installer crash at the end of the "[s]elect and
install packages" step. All the packages have been downloaded and most
of them are installed; the installer crash about 85 percent into the
installation. I've tried to redo the step and the whole installation,
nothing helps. I've verified the ISO with GPG and SHA512sums and done an
integrity check of the USB disk.
This is the last part of the error log (/var/log/syslog):
Pastebin:
http://pastebin.com/jCTW2jCU
> kernel: [...] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> kernel: [...] sd 0:0:0:0: [sda] CDB:
> kernel: [...] Write(10): 2a 00 00 17 c0 00 00 00 08 00
> kernel: [...] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal
> in-target: E: Sub-process /usr/bin/dpkg returned an error code (2)
> in-target: E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp
> in-target: tasksel: apt-get failed (100)
> in-target: Unexpected error; command not executed: 'dpkg --configure -a'
> pkgsel: dpkg-divert: error: error checking '/usr/bin/scrollkeeper-update.distrib': Read-only file system
> pkgsel: dpkg-divert: error: error checking '/usr/bin/scrollkeeper-rebuilddb.distrib': Read-only file system
> pkgsel: dpkg-divert: error: error checking '/usr/bin/fc-cache.distrib': Read-only file system
> pkgsel: cleanup failed
> main-menu[215]: (process:11513): rm: can't remove '/target/usr/sbin/policy-rc.d': Read-only file system
> main-menu[215]: (process:11513): apt-install or in-target is already running, so you cannot run either of
> main-menu[215]: (process:11513): them again until the other instance finishes. You may be able to use
> main-menu[215]: (process:11513): 'chroot /target ...' instead.
> main-menu[215]: (process:11513): rm: can't remove '/target/usr/bin/scrollkeeper-update': Read-only file system
> main-menu[215]: (process:11513): rm: can't remove '/target/usr/bin/scrollkeeper-rebuilddb': Read-only file system
> main-menu[215]: (process:11513): rm: can't remove '/target/usr/bin/fc-cache': Read-only file system
> main-menu[215]: WARNING **: Configuring 'pkgsel' failed with error code 1
> main-menu[215]: WARNING **: Menu item 'pkgsel' failed.
> main-menu[215]: INFO: Modifying debconf priority limit from 'high' to 'medium'
> debconf: Setting debconf/priority to medium
> lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
> main-menu[215]: INFO: Menu item 'pkgsel' selected
> debconf-copydb: Cannot open file /target/var/cache/debconf/config.dat-new: Read-only file system
> kernel: [...] sd 0:0:0:0: [sda] Unhandled error code
> kernel: [...] sd 0:0:0:0: [sda]
> kernel: [...] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> kernel: [...] sd 0:0:0:0: [sda] CDB:
> kernel: [...] Read(10): 28 00 18 98 c1 80 00 00 08 00
> kernel: [...] blk_update_request: 99 callbacks suppressed
> kernel: [...] end_request: I/O error, dev sda, sector 412664192
> kernel: [...] EXT4-fs error (device dm-1):
ext4_find_entry:1312: inode #12845236: comm debconf-copydb: reading
directory lblock 0
> kernel: [...] EXT4-fs (dm-1): previous I/O error to superblock detected
> kernel: [...] sd 0:0:0:0: [sda] Unhandled error code
> kernel: [...] sd 0:0:0:0: [sda]
> kernel: [...] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> kernel: [...] sd 0:0:0:0: [sda] CDB:
> kernel: [...] Write(10): 2a 00 00 17 c0 00 00 00 08 00
> kernel: [...] end_request: I/O error, dev sda, sector 1556480
> kernel: [...] quiet_error: 216 callbacks suppressed
> kernel: [...] Buffer I/O error on device dm-1, logical block 0
> kernel: [...] lost page write due to I/O error on dm-1
> main-menu[215]: (process:20895): ln: /target/usr/bin/scrollkeeper-update: File exists
> main-menu[215]: WARNING **: Configuring 'pkgsel' failed with error code 1
> main-menu[215]: WARNING **: Menu item 'pkgsel' failed.
> main-menu[215]: INFO: Modifying debconf priority limit from 'medium' to 'low'
> debconf: Setting debconf/priority to low
> lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
The answers I got on IRC suggests that it was something wrong with my
SSD. So I tested it with all the tools I know.
First I run an extended self-test with S.M.A.R.T. tools. Everything
comes up OK. No fails. I when run badblocks:
# badblocks -vsw /dev/sda
> Checking for bad blocks in read-write mode
> From block 0 to 234431063
> [---]
> Pass completed, 0 bad blocks found. (0/0/0 errors)
It's suggested to me to test by write random data to a file in a similar
environment to "emulate" the debian-installer. This is what I did:
1. Create new GPT partition table
2. Create new partition labeled for LVM with recommended start and end
(+1MiB to last block)
3. Encrypt the partition with LUKS.
4. Create physical volume, volume group and a logical volume spanning
the whole partition.
4. Create EXT4 file system on logical volume.
6. Create file 'foo' and write to it with:
# dd bs=4M if=/dev/urandom of=foo status=progress
> 236059623424 bytes (236 GB, 220 GiB) copied, 13192.2 s, 17.9 MB/s
> dd: error writing 'foo': No space left on device
> 56284+0 records in
> 56283+0 records out
> 236072116224 bytes (236 GB, 220 GiB) copied, 13192.8 s, 17.9 MB/s
Have you any suggestions on what I can do?
Thanks in advance!
Regards,
Albin Otterhäll