Tomas Bodzar wrote:
Hi all,
Do you know someone what does mean this error?
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf5cd0/192 (10 entries)
cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, DVDRAM GSA-4163B, A103> SCSI0 5/cdrom
removable
cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf5cd0/192 (10 entries)
cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, DVDRAM GSA-4163B, A103> SCSI0 5/cdrom
removable
cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28
Mechanic was running fine for 4 years.Reads very well all types of supported
media.
I tried wodim in Mandriva 2008.1 sometimes error,that I must use TAO,sometimes
error
That buffer overflow and some others.K3b have no info during process about
Buffer,
but in setup or in info is everything OK for HW,SW and privileges.Forgot
dmesg,
but it shows buffer right.Than i reboot to OpenBSD and tried cdio and cdrtools
- nothing.
Will it be sw problem or is mechanic dead?Can I use some of OpenBSD programs
for check condition?
Cdrtools shows mechanic,some info from it and from disc too.hdparm on Mandriva
shows no problem.
Thanks a lot
TB
Most causes for problems that appear and disappear randomly better are
tested
from the hardware side.
The hardware problem does not need to be related to the device which
generates
error messages.
Fwiw: my last crash (system freeze) was related to a video card gone bad
(or conflict between
onboad video and video card). What happened is that something was
written to the
hard drives, destroying the super blocks.
So, in my case: cause = VGA card, effect,=file system corruption. How
are they related?
Many: databus, DMA, ...
I would take everything out of the box.
Start with a known to be good DRAM stick,
connect the CDROM (secong IDE connector, or the only IDE connector you
have,
Boot from CD. Some live CDs (knoppix, puppy, slackx) will load in memory and
leave the CDROM free to write on.
Jumpers should be: on CS (cable select) not master nor slave, try 40
wire flatcable model with only 2
connectors, try 80-wire flatcable, don't use the connector in the middle.
If this works, the only, connect a booting hard drive. On the first IDE
connector, or
on SATA if it is one.
Then the other peripherals one at the time.
.
