[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#455856: marked as done (IO Error with usb-storage (Coolmax360 enclosure))

Your message dated Sun, 23 Dec 2007 07:52:27 +0000
with message-id <E1J6LdL-00044o-I8@ries.debian.org>
and subject line Bug#455856: fixed in fai-kernels 1.17+etch.17
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.18.dfsg.1-13

Forwarded from the nslu2-linux@yahoogroups.com list:

* Richard Morey <moreyr@missouri.edu> [2007-12-10 11:37]:
> I am trying to install debian on the NSLU2, and thanks to the help from 
> this mailing list I've managed to connect to the debian installer and 
> start the install process. However, I'm hitting some snags in partition 
> creation.
> 
> I'm using a Maxtor 60GB HD in a Coolmax360 enclosure. The drive mounts 
> up fine in Ubuntu Gutsy, with no errors (I've tried repartitioning and 
> fsck).
> 
> In the debian installer, after "calculating partitions" I get the error:
> Input/output error during read on
> /dev/scsi/host0/bus0/target0/lun0/disc
> 
> I'm wondering if it is the enclosure, after googling:
> http://www.linuxforums.org/forum/peripherals-hardware/97245-cant-mount-coolmax-hd-360-enclosure.html
> 
> Is there a workaround for this? Will the next version of debian solve 
> it? Do I need to just get new enclosures?
> 
> I've attached three files - the nslu2's syslog, the partman log, and the 
> syslog excerpt from when I plug it in in ubuntu.
> 
> The NSLU2's /var/log/syslog is full of lines like:
> Apr 12 03:42:58 kernel: sd 0:0:0:0: SCSI error: return code = 0x10070000
> Apr 12 03:42:58 kernel: end_request: I/O error, dev sda, sector 4
> 
> Below is an excerpt of /var/log/partman, showing the error:
> *********************
> parted_server: Closing infifo and outfifo
> parted_server: main_loop: iteration 104
> parted_server: Opening infifo
> /bin/partman: IN: PARTITIONS =dev=scsi=host0=bus0=target0=lun0=disc
> parted_server: Read command: PARTITIONS
> parted_server: command_partitions()
> parted_server: Opening outfifo
> parted_server: OUT: OK
> 
> 
> parted_server: OUT: 1   32256-6999713279        6999681024      primary
> ext3    /dev/scsi/host0/bus0/target0/lun0/part1
> 
> 
> parted_server: OUT: 5   6999745536-7098416639   98671104        logical
> linux-swap      /dev/scsi/host0/bus0/target0/lun0/part5
> 
> 
> parted_server: OUT: 6   7098448896-59995192319  52896743424     logical
> ext3    /dev/scsi/host0/bus0/target0/lun0/part6
> 
> 
> parted_server: Partitions printed
> parted_server: OUT:
> 
> **********cut*************
> 
> parted_server: Closing infifo and outfifo
> parted_server: main_loop: iteration 111
> parted_server: Opening infifo
> /lib/partman/commit.d/30parted: IN: COMMIT
> =dev=scsi=host0=bus0=target0=lun0=disc
> parted_server: Read command: COMMIT
> parted_server: command_commit()
> parted_server: Opening outfifo
> parted_server: OUT: Error
> 
> 
> parted_server: OUT: Input/output error during read on
> /dev/scsi/host0/bus0/target0/lun0/disc
> 
> 
> parted_server: OUT:
> 
> 
> parted_server: OUT: Retry
> 
> 
> parted_server: OUT: Ignore
> 
> 
> parted_server: OUT: Cancel
> 
> 
> parted_server: OUT:
> 
> 
> /lib/partman/commit.d/30parted: error_handler: exception with type Error
> /lib/partman/commit.d/30parted: error_handler: reading message
> /lib/partman/commit.d/30parted: paragraph: Input/output error during
> read on /dev/scsi/host0/bus0/target0/lun0/disc
> /lib/partman/commit.d/30parted: error_handler: reading options
> /lib/partman/commit.d/30parted: option: Retry
> /lib/partman/commit.d/30parted: option: Ignore
> /lib/partman/commit.d/30parted: option: Cancel
> /bin/partman: *******************************************************
> /lib/partman/init.d/30parted:
> *******************************************************
> /lib/partman/init.d/35dump:
> *******************************************************
> /lib/partman/init.d/35dump: IN: DUMP =dev=mtdblock0
> parted_server: exception_handler: Bad option: "DUMP =dev=mtdblock0"
> parted_server: Line 301. CRITICAL ERROR!!!  EXITING.
> /bin/partman: *******************************************************
> /lib/partman/init.d/30parted:
> *******************************************************
> parted_server: ======= Starting the server
> parted_server: main_loop: iteration 1
> parted_server: Opening infifo
> /lib/partman/init.d/30parted: IN: OPEN
> =dev=scsi=host0=bus0=target0=lun0=disc
> /dev/scsi/host0/bus0/target0/lun0/disc
> parted_server: Read command: OPEN
> parted_server: command_open()
> parted_server: Request to open =dev=scsi=host0=bus0=target0=lun0=disc
> parted_server: Opening outfifo
> parted_server: OUT: OK

Richard suggested the following patch should help:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=f1cd4ad202ce34d29c847fd82df948ff67c17826

-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---
--- Begin Message --- 
Source: fai-kernels
Source-Version: 1.17+etch.17

We believe that the bug you reported is fixed in the latest version of
fai-kernels, which is due to be installed in the Debian FTP archive:

fai-kernels_1.17+etch.17.dsc
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.17.dsc
fai-kernels_1.17+etch.17.tar.gz
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.17.tar.gz
fai-kernels_1.17+etch.17_i386.deb
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.17_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 455856@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier <dannf@debian.org> (supplier of updated fai-kernels package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 22 Dec 2007 17:32:43 -0700
Source: fai-kernels
Binary: fai-kernels
Architecture: source i386
Version: 1.17+etch.17
Distribution: stable
Urgency: high
Maintainer: Holger Levsen <holger@debian.org>
Changed-By: dann frazier <dannf@debian.org>
Description: 
 fai-kernels - special kernels for FAI (Fully Automatic Installation)
Closes: 412740 414742 433187 453120 455856
Changes: 
 fai-kernels (1.17+etch.17) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18 (2.6.18.dfsg.1-17):
     * [futex] Fix address computation in compat code, fixing hangs
       on sparc64. (closes: #433187)
     * [x86_64] Mask the NX bit in mk_pte_phys to avoid triggering a RSVD type
       page fault on non-NX capable systems which causes a crash.
       (closes: #414742)
     * [fusion] Avoid holding the device busy for too long in the low level
       driver, which was causing filesystems in VMWare guests to get remounted
       read-only under load. (closes: #453120)
     * Add UNUSUAL_DEV entries for supertop usb drives which require the
       IGNORE_RESIDUE flag. (closes: #455856)
     * [sparc64] Enable CONFIG_USB_SERIAL (closes: #412740)
Files: 
 5e6824c8a9be0d65a0f262c0b9efbdec 725 admin extra fai-kernels_1.17+etch.17.dsc
 2e71feb8a67fa7c785b0200f31071e3d 55670 admin extra fai-kernels_1.17+etch.17.tar.gz
 5a847f9f83ab1ed2478fef7d4301955a 5502266 admin extra fai-kernels_1.17+etch.17_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHbbqOhuANDBmkLRkRAjp7AJ9V98hoUvV8XcgTM55IFxBUjJWKIgCglh/+
HTQ9Sy/7Z5H7kU7tosSJ0u8=
=uUWr
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: