I receive the following message at boot time, "SCSI error: <0 0 0 0> return code = 0x70000". Yet all SCSI devices seem to work. Anyone know of where to look to find out what is causing this error?

This error occurs on a recent install of Red Hat Enterprise ES version 4. The hardware is an IBM x236 with ServeRAID 7k and an additional Adaptec U320 controller card.

No idea what that one is myself. I went to http://www.google.com/linux and search the string you have in your post and see many on the subject. Check that out.

There should be a device just before the error you mention. Check to see which device it is.

Brian1

Thank you for responding.

That is the odd thing. Most of the errors I've seen of this type are followed by some type of IO error. I don't see that here. The closest device is the tape drive. It works fine. I've done test backups and restores using this system.


Last 50 lines of dmesg
-----------------------------------------------------------
uhci_hcd 0000:00:1d.0: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 169, io base 00002200
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 177
uhci_hcd 0000:00:1d.1: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 177, io base 00002600
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0342040(lo)
IPv6 over IPv4 tunneling driver
divert: not allocating divert_blk for non-ethernet device sit0
ACPI: Power Button (FF) [PWRF]
EXT3 FS on sda2, internal journal
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
cdrom: open failed.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sda1, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sda5, type ext3), uses xattr
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sda6, type ext3), uses xattr
Adding 2032212k swap on /dev/sda3. Priority:-1 extents:1
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
parport0: PC-style at 0x378 [PCSPP]
st0: Block limits 1 - 16777215 bytes.
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (8192 buckets, 65536 max) - 340 bytes per conntrack
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
SCSI error : <0 0 0 0> return code = 0x70000
parport0: PC-style at 0x378 [PCSPP]
lp0: using parport0 (polling).
lp0: console ready
eth0: no IPv6 routers present

What device uses scsi0, channel 0, id 0, lun 0?
Look earlier in the log, than you have posted.

It may not be the case here, but an often overlooked cause for problems on Red Hat Servers is that the configuration file that is read for a program or device to function properly has the wrong SELinux context and can't be read. I hope I explained that correctly. I'm not an SELinux expert.

> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

Dooh!


Thank you,

Sorry, I didn't know if it couldn't be the controller or the ServeRaid7k card.

Thanks to both of you for responding to my question.

It appears that smartd is causing this error. Smartd tries to monitor logical drive /dev/sda, but fails. It logs the following error.

Device: /dev/sda, BAD IEC (SMART) mode page, err=5 skip device


Anyway, I don't really see the need to run smartd considering I have IBM ServeRAID Manager installed and working.

Thank you,

Was the sda the sata drive? If so there may be issues with those new drives with smartd monitor. It works fine for most IDE drives. I would disable the smartd daemon.

Brian1

/dev/sda is the logical drive setup on the ServeRAID 7k SCSI controller. You are probably correct in that smartd may not be able to monitor that type of drive or perhaps /etc/smartd.conf has the wrong configuration for that type of drive.

I will do some searches and review man smartd.conf. However, in the meantime I have disabled smartd.

Thank you,

Some scsi drives also support smart but limited. It never really took off from what I know of.

Brian1

May be your issue is, device entry as SCSI but underlying disks are ATA disks on a 3ware or such. This can be fixed by specifying the device type.

For example:
/dev/sda -a -d ata
/dev/sdc -d 3ware,0

When you run the smartctl from shell prompt,

smartctl -H /dev/sdc -d 3ware,0

Information about the driver and disks in your system can be found at /proc/ide/ and /proc/scsi/ etc.

Siya

Hi ,

I also have this error with IBM 346 with ServerRaid 7K , I disabled smartd but im still get this error .

Double check that there's no other scripts or plugins that uses the smartctl command.

Anyone have any problems with Dell PowerEdge 1900 and a Perc 5/i (integrated SAS RAID controller) and smartd? I cant get it to work I get the following errors.

smartd - Bad IEC (smart) mode page err=-5

Even with DEVICESCAN.

My CDROM is detected as /dev/hda and I have some /media/cdrom and /media/cdrom1 as virtual devices and crap.

Im using CentOS 4.4 x86_64

Dell PowerEdge 1900
Intel XEON 64bit Dual Core 2x2mb
Dual 320 SAS Drives
2GB DDR2 ECC

I have SAS RAID drivers from dell I havent installed yet cuz im having the shittiest time. Tried using the DKMS and then the RPM and it didnt work, said it couldnt find my source for my kernel.

Any ideas would be helpful

I just purchased a Dell PowerEdge 2900, which is very similar to a PE1900. I'm experiencing the same issue with CentOS 4.4. smartd refuses to start both on system startup and when invoked manually. Here follows a rough summary of the server specifications,

(2) 1.6Ghz Quad-core Xeon 1066Mhz FSB
(4) 146GB SAS 3.5" 15K Hard drive
(4) 2GB 667Mhz Dual Ranked Fully Buffered DIMMS
(1) PERC 5/i configured for RAID 10

The technical specifications, for the hard drives, can be found here,
http://193.128.183.41/home/v3__produ...0&inf=fsp&wg=0

The error in /var/log/messages is as follows,
[root@bigdog ~]# service smartd start
Starting smartd: [FAILED]
[root@bigdog ~]# tail /var/log/messages
Apr 3 16:37:35 bigdog smartd: smartd startup failed
Apr 3 16:38:08 bigdog smartd[30205]: smartd version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Apr 3 16:38:08 bigdog smartd[30205]: Home page is http://smartmontools.sourceforge.net/
Apr 3 16:38:08 bigdog smartd[30205]: Opened configuration file /etc/smartd.conf
Apr 3 16:38:08 bigdog smartd[30205]: Configuration file /etc/smartd.conf parsed.
Apr 3 16:38:08 bigdog smartd[30205]: Device: /dev/sda, opened
Apr 3 16:38:08 bigdog smartd[30205]: Device: /dev/sda, Bad IEC (SMART) mode page, err=-5, skip device
Apr 3 16:38:08 bigdog smartd[30205]: Unable to register SCSI device /dev/sda at line 30 of file /etc/smartd.conf
Apr 3 16:38:08 bigdog smartd[30205]: Unable to register device /dev/sda (no Directive -d removable). Exiting.
Apr 3 16:38:08 bigdog smartd: smartd startup failed
[root@bigdog ~]#

I'm not very experienced with smartd. From what I can gather, this utility is used to detect potential failures before they occur. If smartd is not needed for post-failure recovery of an array then I'd feel safe just removing it from chkconfig...

Even so, any thoughts on the subject would be greatly appreciated.

Cheers!