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

Bug#521723: marked as done (smartmontools: smartd fails on amd64 kernel with 3ware controller)

Your message dated Mon, 3 Jun 2013 19:03:10 +0200
with message-id <20130603170310.GC5319@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #521723,
regarding smartmontools: smartd fails on amd64 kernel with 3ware controller
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
521723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521723
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: smartmontools
Version: 5.38-2
Severity: normal


To get support for 64bit KVM guests I switch from the i686 kernel
(linux-image-2.6.26-1-686) to amd64 (linux-image-2.6.26-1-amd64).

The machine has a 3ware controller which smartmontools is capable
of checking its attached disks. After I rebooted and the amd64
kernel came up, smartd refuses to work. dmesg shows that the
kernel logs out some messages then:

[132307.686213] ioctl32(smartd:23945): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ffc29c5c) on /dev/twa0
[136015.740193] ioctl32(smartd:27292): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ff94b10c) on /dev/twa0
[139733.432548] ioctl32(smartd:29680): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ffff4fbc) on /dev/twa0
[143430.429019] ioctl32(smartd:1066): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ffbceb8c) on /dev/twa0
[172513.471587] ioctl32(smartd:20721): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ff7f9fbc) on /dev/twa0
[176182.578514] ioctl32(smartd:23674): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ffa241ec) on /dev/twa0

If I give smartctl a try, it fails too

unki@cdserver:~$ sudo smartctl -a -d 3ware,0 -a /dev/twa0
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

WARNING - NO DEVICE FOUND ON 3WARE CONTROLLER (disk 0)
Note: /dev/sdX many need to be replaced with /dev/tweN or /dev/twaN
Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

And causes the same log messages:

unki@cdserver:~$ dmesg |grep smartctl
[212209.819155] ioctl32(smartctl:13265): Unknown cmd fd(3) cmd(00000108){t:01;sz:0} arg(ffaec31c) on /dev/twa0


-- Package-specific info:
Ouput of /usr/share/bug/smartmontools:
# CONFIG_IDE_TASK_IOCTL is not set

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages smartmontools depends on:
ii  debianutils                  2.30        Miscellaneous utilities specific t
ii  libc6                        2.7-18      GNU C Library: Shared libraries
ii  libgcc1                      1:4.3.2-1.1 GCC support library
ii  libstdc++6                   4.3.2-1.1   The GNU Standard C++ Library v3
ii  lsb-base                     3.2-20      Linux Standard Base 3.2 init scrip

Versions of packages smartmontools recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20071201cvs-3 A simple mail user agent
ii  mailx              1:20071201-3          Transitional package for mailx ren

smartmontools suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: