Home > Error Code > Scsi Error: Return Code = 0x00070000

Scsi Error: Return Code = 0x00070000

Contents

Kernel Bug Tracker – Bug32882 USB stick - sd 11:0:0:0: rejecting I/O to dead device being removed Last modified: 2012-02-22 21:01:54 UTC Home | New | Browse | Search | [?] Supports SMART auto save timer. And rest of the counts onward had I/O error too. Adv Reply October 24th, 2011 #7 alfonso78 View Profile View Forum Posts Private Message Frothy Coffee! Check This Out

Commit interval 5 seconds Apr 8 11:43:11 moria kernel: EXT3 FS on sde1, internal journal Apr 8 11:43:11 moria kernel: EXT3-fs: mounted filesystem with ordered data mode. ---- We have done What issue in there exactly? end_buffer_async_read+0x110/0x110 Jan 2 16:05:26 s01 kernel: [ 3600.304245] [] blkdev_writepage+0x14/0x20 Jan 2 16:05:26 s01 kernel: [ 3600.304249] [] __writepage+0x10/0x40 Jan 2 16:05:26 s01 kernel: [ 3600.304253] [] write_cache_pages+0x193/0x3f0 Jan 2 16:05:26 zfs_read+0x3c2/0x4a0 [zfs] Dec 28 06:16:41 waterhouse kernel: [415698.308199] [] ?

Scsi Error: Return Code = 0x00070000

It looks like the person in that mail you pointed to was using the device directly and not a multiapth device. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Home Forums sync_buffer+0x3b/0x40 [ 3000.628367] [] ? __wait_on_bit_lock+0x3f/0x84 [ 3000.628375] [] ? Oct 23 23:52:19 NAS mdadm[1621]: Fail event detected on md device /dev/md0, component device /dev/sda1 And these are the details of one of the four disks.

vfs_write+0xb0/0x1e0 Dec 28 06:14:41 waterhouse kernel: [415578.268286] [] ? cv_wait_common+0x105/0x1a0 [spl] Dec 28 06:16:41 waterhouse kernel: [415698.307625] [] ? To show the above log entries in context here are a few lines before them and a few after. I run badblocks on one of the two disks that failed yesterday.

dsl_dataset_prev_snap_txg+0x22/0x50 [zfs] Dec 28 06:14:41 waterhouse kernel: [415578.268152] [] ? Scsi Error: Return Code = 0x00010000 Maybe just 2 paths? Dec 28 06:12:22 waterhouse kernel: [415439.210042] sd 9:0:0:0: [sde] READ CAPACITY failed Dec 28 06:12:22 waterhouse kernel: [415439.210045] sd 9:0:0:0: [sde] Dec 28 06:12:22 waterhouse kernel: [415439.210048] sd 9:0:0:0: [sde] READ https://bugzilla.redhat.com/show_bug.cgi?id=736871 kmem_free_debug+0x41/0x140 [spl] Dec 28 06:14:41 waterhouse kernel: [415578.268203] [] ?

As we are > running the device mapper multipath it is possible that Device Mapper can > interpret this error code or is the error code is sent directly to the Booting from a bootable ubuntu 11.10 USB key, I can see all 4 disks plus the OS disk. zfs_read+0x3c2/0x4a0 [zfs] Dec 28 06:16:41 waterhouse kernel: [415698.307526] [] ? __mark_inode_dirty+0x172/0x270 Dec 28 06:16:41 waterhouse kernel: [415698.307544] [] ? The backend system is not reporting any errors.

Scsi Error: Return Code = 0x00010000

Dec 28 06:11:25 waterhouse kernel: [415382.359461] b8<6>[415382.359464] sd 10:0:0:0: [sdf] Dec 28 06:11:25 waterhouse kernel: [415382.359469] 68 88Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Dec 28 06:11:25 waterhouse kernel: [415382.359477] 00 00<5>[415382.359482] sd 10:0:0:0: [sdf] kthread+0xb8/0xd0 Dec 28 06:14:41 waterhouse kernel: [415578.267756] [] ? Scsi Error: Return Code = 0x00070000 The bug report wasn't for the disk error but that Linux didn't handle the error! Result: Hostbyte=did_error Driverbyte=driver_ok Tango Icons Tango Desktop Project.

zio_wait+0xeb/0x1a0 [zfs] Dec 28 06:16:41 waterhouse kernel: [415698.307152] [] ? http://softbb.net/error-code/5y-ef-error-code.html Why the kernel reports as Unhandled Error code" --------------------- "Sep 16 15:51:05 per610-01 kernel: sd 9:0:0:25: [sdat] Unhandled error code" --------------------- snippet of message log =============================== Sep 16 15:51:05 per610-01 kernel: We are running some data integrity test tool which gives out data miscompare errors when such errors happen. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. Infinite Warfare Error Code 262144

I'll follow instructions found here: http://kevin.deldycke.com/2008/07/he...data-recovery/ As expected, all disks are online now (the case in now open, I'm testing the theory that it's a temperature issue): Code: $ sudo fdisk do_unlinkat+0xad/0x134 [ 3000.628656] [] ? What do you think should be happening? this contact form If Selective self-test is pending on power-up, resume after 0 minute delay.

y mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md0 started. $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid6 sdb1[1] sda1[0] 3907020800 LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware USB Mass Storage not mount 'Buffer I/O error on device sde, logical block 0' User Name Remember Me? none of them was able to mount it.

P.S.

I tried my best! This is expected if you by node you iscsi node as in iscsi target. Device 84fa Flags: bus master, fast devsel, latency 0, IRQ 130 I/O ports at 6050 [size=8] I/O ports at 6040 [size=4] I/O ports at 6030 [size=8] I/O ports at 6020 [size=4] An other device failed!!!

SyS_pwrite64+0x63/0xa0 Dec 28 06:14:41 waterhouse kernel: [415578.268296] [] ? Oct 23 15:41:10 NAS kernel: [56484.868015] sd 3:0:0:0: [sde] Unhandled error code Oct 23 15:41:10 NAS kernel: [56484.868017] sd 3:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Oct 23 15:41:10 NAS kernel: [56484.868020] sd SyS_fdatasync+0xa/0x10 Dec 28 06:16:41 waterhouse kernel: [415698.308359] [] ? navigate here zil_commit.part.11+0x5d/0x6e0 [zfs] Dec 28 06:16:41 waterhouse kernel: [415698.308329] [] ?

It just means we did not have a nice string to print out to further explain what the problem was, so all you get is the string about DID_TRANSPORT_FAILFAST. Dec 28 06:12:22 waterhouse kernel: [415439.209997] sd 9:0:0:0: [sde] READ CAPACITY failed Dec 28 06:12:22 waterhouse kernel: [415439.210000] sd 9:0:0:0: [sde] Dec 28 06:12:22 waterhouse kernel: [415439.210002] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Dec tsd_exit+0x5d/0x2a0 [spl] Dec 28 06:16:41 waterhouse kernel: [415698.307519] [] ? Having trouble installing a piece of hardware?

vfs_write+0xb0/0x1e0 Dec 28 06:16:41 waterhouse kernel: [415698.308226] [] ? Dec 28 06:11:25 waterhouse kernel: [415382.364354] sd 10:0:0:0: [sdf] READ CAPACITY failed Dec 28 06:11:25 waterhouse kernel: [415382.364357] sd 10:0:0:0: [sdf] Dec 28 06:11:25 waterhouse kernel: [415382.364359] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Dec jbd2_journal_get_write_access+0x22/0x33 [jbd2] [ 3000.628521] [] ? __ext4_journal_get_write_access+0x4b/0x53 [ext4] [ 3000.628574] [] ? User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License.

Adv Reply October 23rd, 2011 #5 alfonso78 View Profile View Forum Posts Private Message Frothy Coffee! ktime_get_ts+0x21/0x49 [ 3000.628468] [] ? zpl_write_common+0x4e/0x80 [zfs] Dec 28 06:14:41 waterhouse kernel: [415578.268274] [] ? The time now is 11:07 AM.

Dec 28 06:12:22 waterhouse kernel: [415439.209978] sd 9:0:0:0: [sde] READ CAPACITY(16) failed Dec 28 06:12:22 waterhouse kernel: [415439.209982] sd 9:0:0:0: [sde] Dec 28 06:12:22 waterhouse kernel: [415439.209984] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Dec What test can I do? For the latter you might see abort or other messages about TMFs being sent, but you would not see error messages from sd or "end_request: I/O error" messages like you did kthread+0xb8/0xd0 Dec 28 06:16:41 waterhouse kernel: [415698.307284] [] ?

You could turn on iscsi or scsi debugging to see if multipath has sent the IO to another path but that is going to get really noisy.