DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd"

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd"
# 1  
Old 08-14-2011
DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd"

Dear Guru,

IHAC who is using Redhat Linux 5 on DELL M910.

When system bootup, it show "Buffer I/O error on device sdd" error message. Below is the "dmesg" output.

The scenario is:
If more external FC SAN disk LUN add, the device would change other name. So it will impact the raw device mapping which they set in "/etc/udev/rules.d/60-raw.rules".

Anybody met this issue before? Any tips for fixing this issue?

Thanks a lot for your help!

Best regards,
David Feng

===================================
#dmesg | grep sdd
SCSI device sdd: 2 512-byte hdwr sectors (0 MB)
sdd: Write Protect is off
sdd: Mode Sense: 97 00 00 08
SCSI device sdd: drive cache: write through
SCSI device sdd: 2 512-byte hdwr sectors (0 MB)
sdd: Write Protect is off
sdd: Mode Sense: 97 00 00 08
SCSI device sdd: drive cache: write through
sdd:[0x000053420001015e][INFO][UP][__mppLnx_scsi_done, 2682][4294689543] UP_done: A0C0P0L0,r=8000002,MPP_CHECK_CONDITION,sk=5,ASC/ASCQ=20/0,SN:13.
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
Dev sdd: unable to read RDB block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
sd 8:0:0:0: Attached scsi disk sdd
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
SCSI device sdd: 2 512-byte hdwr sectors (0 MB)
sdd: Write Protect is off
sdd: Mode Sense: 97 00 00 08
SCSI device sdd: drive cache: write through
sdd:[0x000053420001015e][INFO][UP][__mppLnx_scsi_done, 2682][4294757946] UP_done: A0C0P3L0,r=8000002,MPP_CHECK_CONDITION,sk=5,ASC/ASCQ=20/0,SN:1915.
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
Dev sdd: unable to read RDB block 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
[root@rac1 log]# 001015e][INFO][UP][__mppLnx_scsi_done, 2682][4294757946] UP_done: A0C0P3L0,r=8000002,MPP_CHECK_CONDITION,sk=5,ASC/ASCQ=20/0,SN:1915.
-bash: 001015e][INFO][UP][__mppLnx_scsi_done,: command not found
===================================
DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd"-error_virtual_cdromjpg
# 2  
Old 08-14-2011
Please post output from:

Code:
fdisk -l

and

Code:
df -h

and
Code:
cat /etc/fstab

# 3  
Old 08-14-2011
Thanks for quick response!

But I cannot get the output at the moment, would post the output tomorrow morning.

Do you have any work around for me to do some testing since tomorrow morning in my time is your midnight. Smilie

Regards,
David Feng
# 4  
Old 08-14-2011
I would hate to take a guess, without looking at the output of those commands. Also, what kind of SAN Storage array do you have and are you using any volume manager? Lvm is the native volume manager or you could use veritas.
Also these forums has always someone who can help in your timezone. Don'tworry about that Smilie. If I am not online,someone else will be able to help.
# 5  
Old 08-14-2011
Sure understood! Thanks!

The customer is using the Linux native LVM.
The SAN storage is HuaWei Symantec 5600T.

Will post more detail information tomorrow.

Regards,
David Feng
# 6  
Old 08-14-2011
Another useful output will be from sg3-utils, install these through yum if you are subscribed to RHN.
Once installed, paste output from :

Code:
sg_map -i

# 7  
Old 08-15-2011
Also, are you using multipathing drivers?
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. SCO

NFS umount shows the "Device busy (Error 16)"

Hi there After making a backup copy of it sometimes happens that when I want to unmount an NFS indicates the error:umount: /path_mount busy: Device busy (Error 16) if I run lsoff, I can not find the process that is blocking the application. I'm using OpenServer 5.0.2c as one NFS server ... (14 Replies)
Discussion started by: flako
14 Replies

2. Solaris

Repeated error - "se_hdlc: clone device must be attached before use" in /var/adm/messages

Below is the error being repeated on my Solaris 9 Sun-Fire-V890 machine. SAN team confirmed as everything is fine from their end. I did google and found that some people say its a known Oracle bug when you have Oracle 10G installed on your system but I kind of disagree with them. Please see below... (2 Replies)
Discussion started by: vikkash
2 Replies

3. Solaris

"Can't open boot device" error !!

I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440. after... (3 Replies)
Discussion started by: Anti_Evil
3 Replies

4. UNIX for Dummies Questions & Answers

UNIX rm -rf error "rm: cannot remove `filename' : Device or resource busy"

Hi Everyone, I am trying to remove a directory: $ rm -rf directory_name/ rm: cannot remove `directory_name/filename': Device or resource busy What does this mean, and why can't I remove these files? I already tried moving into the directory, and removing the files individually, but I... (7 Replies)
Discussion started by: Anna_Z
7 Replies

5. Red Hat

"if" and "then" statement is not working in RedHat

Dear experts, I'm trying to write a script to calculate the usage of Log Archive in a directory, so if it gets to a point where the directory size is 60%, then send out an FYI.. email. So if then it reaches to 80%, move the logs from that directory. I have written the script as follow but... (10 Replies)
Discussion started by: Afi_Linux
10 Replies

6. Emergency UNIX and Linux Support

Mapping between "Pseudo name" and "Logical device ID" in powerpath with SVM changed....

Dear All, I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output : root # powermt display dev=all Pseudo name=emcpower3a CLARiiON ID=CK200073400372 Logical device ID=60060160685D1E004DD97FB647BFDC11 state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies

7. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies
Login or Register to Ask a Question