HP B132L hangs

Hi!

In the last few days the B132l I use as DSL router completely hung 3 times. Every time requiring a power cycle to revive it. It is running Debian testing with kernel 2.4.18-hppa.

To test the machine I tried to compile a new kernel. After compiling a few files everything hung and spit out the following messages:

scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 000902 failing command because of reset, slot 00010520, cmnd 10081c00
failing command because of reset, slot 00010654, cmnd 10081a00
failing command because of reset, slot 00010788, cmnd 10081800
failing command because of reset, slot 000108bc, cmnd 10081600
failing command because of reset, slot 000109f0, cmnd 10081400
failing command because of reset, slot 00010b24, cmnd 10081200
failing command because of reset, slot 00010c58, cmnd 10081000
failing command because of reset, slot 00010d8c, cmnd 10082e00
failing command because of reset, slot 00010ec0, cmnd 10082c00
failing command because of reset, slot 00010ff4, cmnd 10082a00
failing command because of reset, slot 00011128, cmnd 10082800
failing command because of reset, slot 0001125c, cmnd 10082600
failing command because of reset, slot 00011390, cmnd 10082400
failing command because of reset, slot 000114c4, cmnd 10082200
failing command because of reset, slot 000115f8, cmnd 10082000
failing command because of reset, slot 0001172c, cmnd 100a4e00
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 000902 failing command because of reset, slot 00010520, cmnd 10081c00
failing command because of reset, slot 00010654, cmnd 10081a00
failing command because of reset, slot 00010788, cmnd 10081800

... and so on and so forth ...

The power seitch does nothing, only power cycling helps. I tried compiling the kernel again with the same results...

What do these messages mean? Is the hd defective or is it some problem with the scsi bus?

The machine worked flawlessly for half a year... I have no idea what went wrong!

Thanks in advance,
Sebastian

Yes it looks like a disk becoming defective. The best way to be sure is to use a hp cdrom containing Diagnostic tools (iirc the last hpux support + would contains it). This cd is bootable and contains tools allowing you test your disk.

If you have another system on which you can connect your suspected disk you can also try a dd cmd like:
dd if=/dev/rdsk/c0txd0 of=/dev/null bs=2048k (where you replace /dev/rdsk/c0txd0 by the actual disk path)

It seems to confirm your suspition (i have to manage remotely some 300 hp server: a few b132, b180, b2000, A500, K250, L, N and a lot of D; and the most peaces we have to replace are disk becoming defective)

hth,
joel

Yes it looks like a disk becoming defective. The best way to be sure is to use a hp cdrom containing Diagnostic tools (iirc the last hpux support + would contains it). This cd is bootable and contains tools allowing you test your disk.

If you have another system on which you can connect your suspected disk you can also try a dd cmd like:
dd if=/dev/rdsk/c0txd0 of=/dev/null bs=2048k (where you replace /dev/rdsk/c0txd0 by the actual disk path)

It seems to confirm your suspition (i have to manage remotely some 300 hp server: a few b132, b180, b2000, A500, K250, L, N and a lot of D; and the most peaces we have to replace are disk becoming defective)

hth,
joel

Joel Soete:

I don't have such a cd...
I have only two HP cd sets:
"HP-UX Applications/Patches 10.20" 5 CDs "Additional Core Enhancements HP-UX 10.20 Workstations" 1 CD

Do you know if one of them contains these tools?

See my other post for results of backup... it provoced the same (or at least a similar) error :-/
I do not currently have another system I could put the disk in (I got a C200 but it is not in a working state right now). The disk does not contain too important data - but it was a lot of work to set up the router.

thx,
Sebastian

Joel Soete:

I don't have such a cd...
I have only two HP cd sets:
"HP-UX Applications/Patches 10.20" 5 CDs "Additional Core Enhancements HP-UX 10.20 Workstations" 1 CD

Do you know if one of them contains these tools?

See my other post for results of backup... it provoced the same (or at least a similar) error :-/
I do not currently have another system I could put the disk in (I got a C200 but it is not in a working state right now). The disk does not contain too important data - but it was a lot of work to set up the router.

thx,
Sebastian

I also get such set of cd's when I recieved the first b132 (it was also one of the first in belgium) and I think that tools would be on the patch cd but i don't remember exactly. I will check when I will be back to the office (in 10 days :( sorry)

Yes I read it also and as mentioned Grant "I/O error:..." message confirm my first opinion (and my experience with my b180 near the same b132L execepted cpu frequency) unfortunaltely your disk became faulty (the most frequent part replaced over 300 unix server I have to maintain)

So the best would be to try to backup the most of your /etc (where stand generaly config files), additonal config files that you remember, and may be also your /var/lib/dpkg (the debian pakages db: it could help to remember which packages where installed). Then, if you can, replace your disk, and re-install your system.

I also had to reinstall two systems like this this year: one because of a cpu failure (a b2k) and one also due a disk failure. (I would so have a look for tools as mkcdrecord or mondo [don't know which is the most simple to implement] but i do not yet find enough time to build any recovery cd. On the other hand i had the opportunity to install raid1 on my main systems (2 b180; a fw and a test one for cvs kernels and unstable debian install)).

Good luck,
Joel

I also get such set of cd's when I recieved the first b132 (it was also one of the first in belgium) and I think that tools would be on the patch cd but i don't remember exactly. I will check when I will be back to the office (in 10 days :( sorry)

Yes I read it also and as mentioned Grant "I/O error:..." message confirm my first opinion (and my experience with my b180 near the same b132L execepted cpu frequency) unfortunaltely your disk became faulty (the most frequent part replaced over 300 unix server I have to maintain)

So the best would be to try to backup the most of your /etc (where stand generaly config files), additonal config files that you remember, and may be also your /var/lib/dpkg (the debian pakages db: it could help to remember which packages where installed). Then, if you can, replace your disk, and re-install your system.

I also had to reinstall two systems like this this year: one because of a cpu failure (a b2k) and one also due a disk failure. (I would so have a look for tools as mkcdrecord or mondo [don't know which is the most simple to implement] but i do not yet find enough time to build any recovery cd. On the other hand i had the opportunity to install raid1 on my main systems (2 b180; a fw and a test one for cvs kernels and unstable debian install)).

Good luck,
Joel

That's a residue of an incorrect lasi700 driver. Notice it thinks the length is six for a ten byte command. This has long been fixed in the linux-2.4 PA tree (er, I think---I've been concentrating on 2.6 mainly).

However, something higher up in the trace you don't attach caused the actual problem that this is a response to (It's caused by the SCSI mid layer putting the wrong command length back *after* error recovery, so your true root cause is the error that first started this).

James

That's a residue of an incorrect lasi700 driver. Notice it thinks the length is six for a ten byte command. This has long been fixed in the linux-2.4 PA tree (er, I think---I've been concentrating on 2.6 mainly).

However, something higher up in the trace you don't attach caused the actual problem that this is a response to (It's caused by the SCSI mid layer putting the wrong command length back *after* error recovery, so your true root cause is the error that first started this).

James

Hrm...

I installed the latest available kernel image (2.4.20-32) and it worked - only compiling seems to raise the error... strange!

I ran make-kpkg again and this time captured the first messages:

/usr/bin/make -C scsi fastdep
make[6]: Entering directory `/usr/src/linux-2.4.22/drivers/scsi' gcc -D__KERNEL__ -I/usr/src/linux-2.4.22/include -Wall -Wstrict-prototypes -Wnoc | /sbin/genksyms -k 2.4.22 > /usr/src/linux-2.4.22/include/linux/modules/scsi_p mv /usr/src/linux-2.4.22/include/linux/modules/scsi_syms.ver.tmp /usr/src/linuxr gcc -D__KERNEL__ -I/usr/src/linux-2.4.22/include -Wall -Wstrict-prototypes -Wnoc | /sbin/genksyms -k 2.4.22 > /usr/src/linux-2.4.22/include/linux/modules/53c70p 53c700.c:163:22: 53c700_d.h: No such file or directory
mv /usr/src/linux-2.4.22/include/linux/modules/53c700.ver.tmp /usr/src/linux-2.r /usr/src/linux-2.4.22/scripts/mkdep -D__KERNEL__ -I/usr/src/linux-2.4.22/includm vme16x.c mvme16xInfo fld=0x35e1fb.h ncr53c8xx.c n, cr53c8xx.h nsp32Current .c nr _debug.c nsp32_iAdditional sense indicates Unrecovered read error o.h oktagon_esp. I/O error: dev 08:04, sector 3182320
c oktagon_esp.h scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ )

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
oktagon_io.S ossscsi0: (2:0) Synchronous at offset 8, period 100ns t.c osst.h osst_detect.h osst_options.h pas16.c pas16.h pci2000.c pci2000.h pci)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
qlogicpti.h qlogscsi0: (2:0) Synchronous at offset 8, period 100ns icpti_asm.c scsi.c scsi.h scsi_debug.c scsi_debug.h scsi_dma.c scsi_error.c scs)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
710_d.h sim710_uscsi0: (2:0) Synchronous at offset 8, period 100ns .h sr.c sr.h sr_ioctl.c sr_vendor.c st.c st.h st_options.h sun3_NCR5380.c sun3_)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 000109f0, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081a00 failing command because of reset, slot 00010654, cmnd 10081800 failing command because of reset, slot 00010788, cmnd 10082800 failing command because of reset, slot 000108bc, cmnd 10081000 failing command because of reset, slot 000109f0, cmnd 10081c00 failing command because of reset, slot 00010b24, cmnd 10082e00 failing command because of reset, slot 00010c58, cmnd 10081200 failing command because of reset, slot 00010d8c, cmnd 10082a00 failing command because of reset, slot 00010ec0, cmnd 10082600 failing command because of reset, slot 00010ff4, cmnd 10081600 failing command because of reset, slot 00011128, cmnd 10082200 failing command because of reset, slot 0001125c, cmnd 10082c00 failing command because of reset, slot 00011390, cmnd 10081400 failing command because of reset, slot 000114c4, cmnd 10082400 failing command because of reset, slot 000115f8, cmnd 10082000 failing command because of reset, slot 0001172c, cmnd 100a4e00
7000.c wd7000.h scsi0: (2:0) Synchronous at offset 8, period 100ns zalon7xx.c zalon7xx.h > .depend
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00 failing command because of reset, slot 00010654, cmnd 10081a00 failing command because of reset, slot 00010788, cmnd 10081800 failing command because of reset, slot 000108bc, cmnd 10081600 failing command because of reset, slot 000109f0, cmnd 10081400 failing command because of reset, slot 00010b24, cmnd 10081200 failing command because of reset, slot 00010c58, cmnd 10081000 failing command because of reset, slot 00010d8c, cmnd 10082e00 failing command because of reset, slot 00010ec0, cmnd 10082c00 failing command because of reset, slot 00010ff4, cmnd 10082a00 failing command because of reset, slot 00011128, cmnd 10082800 failing command because of reset, slot 0001125c, cmnd 10082600 failing command because of reset, slot 00011390, cmnd 10082400 failing command because of reset, slot 000114c4, cmnd 10082200 failing command because of reset, slot 000115f8, cmnd 10082000 failing command because of reset, slot 0001172c, cmnd 100a4e00
...

I will try the newer kernel now...
However "Unrecovered read error" sounds very much like a bad disk for me so I suppose it will not help...

cu,
Sebastian

Hrm...

I installed the latest available kernel image (2.4.20-32) and it worked - only compiling seems to raise the error... strange!

I ran make-kpkg again and this time captured the first messages:

/usr/bin/make -C scsi fastdep
make[6]: Entering directory `/usr/src/linux-2.4.22/drivers/scsi' gcc -D__KERNEL__ -I/usr/src/linux-2.4.22/include -Wall -Wstrict-prototypes -Wnoc | /sbin/genksyms -k 2.4.22 > /usr/src/linux-2.4.22/include/linux/modules/scsi_p mv /usr/src/linux-2.4.22/include/linux/modules/scsi_syms.ver.tmp /usr/src/linuxr gcc -D__KERNEL__ -I/usr/src/linux-2.4.22/include -Wall -Wstrict-prototypes -Wnoc | /sbin/genksyms -k 2.4.22 > /usr/src/linux-2.4.22/include/linux/modules/53c70p 53c700.c:163:22: 53c700_d.h: No such file or directory
mv /usr/src/linux-2.4.22/include/linux/modules/53c700.ver.tmp /usr/src/linux-2.r /usr/src/linux-2.4.22/scripts/mkdep -D__KERNEL__ -I/usr/src/linux-2.4.22/includm vme16x.c mvme16xInfo fld=0x35e1fb.h ncr53c8xx.c n, cr53c8xx.h nsp32Current .c nr _debug.c nsp32_iAdditional sense indicates Unrecovered read error o.h oktagon_esp. I/O error: dev 08:04, sector 3182320
c oktagon_esp.h scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ )

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
oktagon_io.S ossscsi0: (2:0) Synchronous at offset 8, period 100ns t.c osst.h osst_detect.h osst_options.h pas16.c pas16.h pci2000.c pci2000.h pci)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
qlogicpti.h qlogscsi0: (2:0) Synchronous at offset 8, period 100ns icpti_asm.c scsi.c scsi.h scsi_debug.c scsi_debug.h scsi_dma.c scsi_error.c scs)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00
710_d.h sim710_uscsi0: (2:0) Synchronous at offset 8, period 100ns .h sr.c sr.h sr_ioctl.c sr_vendor.c st.c st.h st_options.h sun3_NCR5380.c sun3_)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 000109f0, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081a00 failing command because of reset, slot 00010654, cmnd 10081800 failing command because of reset, slot 00010788, cmnd 10082800 failing command because of reset, slot 000108bc, cmnd 10081000 failing command because of reset, slot 000109f0, cmnd 10081c00 failing command because of reset, slot 00010b24, cmnd 10082e00 failing command because of reset, slot 00010c58, cmnd 10081200 failing command because of reset, slot 00010d8c, cmnd 10082a00 failing command because of reset, slot 00010ec0, cmnd 10082600 failing command because of reset, slot 00010ff4, cmnd 10081600 failing command because of reset, slot 00011128, cmnd 10082200 failing command because of reset, slot 0001125c, cmnd 10082c00 failing command because of reset, slot 00011390, cmnd 10081400 failing command because of reset, slot 000114c4, cmnd 10082400 failing command because of reset, slot 000115f8, cmnd 10082000 failing command because of reset, slot 0001172c, cmnd 100a4e00
7000.c wd7000.h scsi0: (2:0) Synchronous at offset 8, period 100ns zalon7xx.c zalon7xx.h > .depend
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)

         len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00

scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090]
failing command because of reset, slot 00010520, cmnd 10081c00 failing command because of reset, slot 00010654, cmnd 10081a00 failing command because of reset, slot 00010788, cmnd 10081800 failing command because of reset, slot 000108bc, cmnd 10081600 failing command because of reset, slot 000109f0, cmnd 10081400 failing command because of reset, slot 00010b24, cmnd 10081200 failing command because of reset, slot 00010c58, cmnd 10081000 failing command because of reset, slot 00010d8c, cmnd 10082e00 failing command because of reset, slot 00010ec0, cmnd 10082c00 failing command because of reset, slot 00010ff4, cmnd 10082a00 failing command because of reset, slot 00011128, cmnd 10082800 failing command because of reset, slot 0001125c, cmnd 10082600 failing command because of reset, slot 00011390, cmnd 10082400 failing command because of reset, slot 000114c4, cmnd 10082200 failing command because of reset, slot 000115f8, cmnd 10082000 failing command because of reset, slot 0001172c, cmnd 100a4e00
...

I will try the newer kernel now...
However "Unrecovered read error" sounds very much like a bad disk for me so I suppose it will not help...

cu,
Sebastian

Could you redirect the output from make-kpkg to a file or /dev/null so the messages from the compilation aren't interleaved with the kernel messages.

"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

Could you redirect the output from make-kpkg to a file or /dev/null so the messages from the compilation aren't interleaved with the kernel messages.

"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

I tried to backup the system and got the a similar error with very few messages mixed into it. Maybe this is better readable:

b132l:~# tar c / | ssh -l sb 192.168.0.2 'gzip -f > root.tar.gz'
tar: Removing leading `/' from member names
[email protected]'s password:
scsi0: ERROR on channel 0, id 2, lun 0, CDB: Request Sense 00 00 00 40 00
Info fld=0x39a27b, Current sd08:04: sense key Medium Error
Additional sense indicates Unrecovered read error
 I/O error: dev 08:04, sector 3428208
tar: /usr/share/consolefonts/lat1-08.psf.gz: Read error at byte 0, reading 1024 bytes: Input/output error
scsi0: ERROR on channel 0, id 2, lun 0, CDB: Request Sense 00 00 00 40 00
Info fld=0x39a5e4, Current sd08:04: sense key Medium Error
Additional sense indicates Unrecovered read error
 I/O error: dev 08:04, sector 3429080
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010ff4, dsp 00090210[0210]
 failing command because of reset, slot 00010ff4, cmnd 10081c00
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00

cu,
Sebastian

I tried to backup the system and got the a similar error with very few messages mixed into it. Maybe this is better readable:

b132l:~# tar c / | ssh -l sb 192.168.0.2 'gzip -f > root.tar.gz'
tar: Removing leading `/' from member names
[email protected]'s password:
scsi0: ERROR on channel 0, id 2, lun 0, CDB: Request Sense 00 00 00 40 00
Info fld=0x39a27b, Current sd08:04: sense key Medium Error
Additional sense indicates Unrecovered read error
 I/O error: dev 08:04, sector 3428208
tar: /usr/share/consolefonts/lat1-08.psf.gz: Read error at byte 0, reading 1024 bytes: Input/output error
scsi0: ERROR on channel 0, id 2, lun 0, CDB: Request Sense 00 00 00 40 00
Info fld=0x39a5e4, Current sd08:04: sense key Medium Error
Additional sense indicates Unrecovered read error
 I/O error: dev 08:04, sector 3429080
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010ff4, dsp 00090210[0210]
 failing command because of reset, slot 00010ff4, cmnd 10081c00
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00
scsi0: Bus Reset detected, executing command 10081c00, slot 00010520, dsp 00090210[0210]
 failing command because of reset, slot 00010520, cmnd 10081c00
 failing command because of reset, slot 00010ff4, cmnd 10081a00
 failing command because of reset, slot 000115f8, cmnd 10081800
scsi0: (2:0) Synchronous at offset 8, period 100ns
scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT)
         len = 6, cmd =Read (10) 00 00 39 a5 e8 00 00 a0 00

cu,
Sebastian

yes, much better

This is the disk telling the driver it had a real failure.

...

this output is the bug james mentioned was fixed in a later kernel.

grant

yes, much better

This is the disk telling the driver it had a real failure.

...

this output is the bug james mentioned was fixed in a later kernel.

grant