Disk problems, or at least fs problems

Disk problems, or at least fs problems

Post by Paul Richardso » Thu, 30 Jul 1998 04:00:00



OK I have RH 5.1 installed on my system.
config is as follows:
ASUS P/I P55T2P4 mother board, with 64 MB of EDO dram
BT958 scsi controller
IBM Dcas 34330 F/W scsi drive
Conner 1.0 Gig Scsi drive
Toshiba cd rom
Matrox Millenium graphics card.

I scored a memory test from the net which you load on to floppy, reboot
your system
and run this test in a low-level mode. No errors

I have been having problems like this for about a year. Up until I
replaced the
BT958 I was not suspecting my motherboard. Maybe that is the next thing
to be replaced. Does anyone have any idea what these errors are pointing
to
in terms of hw failure


I just replaced the BT958, the cables are new also. I have been getting
a lot of
these errors:

EXT2-fs error (device 08:02): ext2_readdir: directory #75170 contains a
hole at
offset 2048
EXT2-fs error (device 08:02): ext2_readdir: directory #75170 contains a
hole at
offset 3072
EXT2-fs error (device 08:02): ext2_readdir: directory #75170 contains a
hole at
offset 4096
EXT2-fs error (device 08:02): ext2_readdir: directory #75170 contains a
hole at
offset 5120
EXT2-fs error (device 08:02): ext2_readdir: directory #75170 contains a
hole at
offset 6144
SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 28000002
extra data not valid Current error sd08:02: sense key Illegal Request
Additional sense indicates Invalid field in cdb
scsidisk I/O error: dev 08:02, sector 327720, absolute sector 536616
scsi : aborting command due to timeout : pid 13085, scsi0, channel 0, id
0, lun
0 Write (6) 03 70 10 02 00
scsi0: Aborting CCB #13098 to Target 0
scsi : aborting command due to timeout : pid 13086, scsi0, channel 0, id
0, lun
0 Write (6) 03 f0 2a 04 00
scsi0: Aborting CCB #13099 to Target 0
scsi : aborting command due to timeout : pid 13087, scsi0, channel 0, id
0, lun
0 Write (6) 04 70 16 02 00
scsi0: Aborting CCB #13100 to Target 0
scsi : aborting command due to timeout : pid 13088, scsi0, channel 0, id
0, lun
0 <4>scsi0: CCB #13098 to Target 0 Aborted
Write (6) 04 70 4c 02 00
scsi0: Aborting CCB #13101 to Target 0
scsi : aborting command due to timeout : pid 13089, scsi0, channel 0, id
0, lun
0 Write (6) 04 70 52 04 00
scsi0: CCB #13099 to Target 0 Aborted
scsi0: Aborting CCB #13102 to Target 0
scsi : aborting command due to timeout : pid 13090, scsi0, channel 0, id
0, lun
0 <4>scsi0: CCB #13100 to Target 0 Aborted
Write (6) 05 30 1a 02 00
scsi0: Aborting CCB #13103 to Target 0
scsi : aborting command due to timeout : pid 13091, scsi0, channel 0, id
0, lun
0 Write (6) 05 70 26 02 00
scsi0: CCB #13101 to Target 0 Aborted
scsi0: Aborting CCB #13104 to Target 0
scsi : aborting command due to timeout : pid 13092, scsi0, channel 0, id
0, lun
0 Write (6) 05 f0 20 02 00
scsi0: Aborting CCB #13105 to Target 0
scsi : aborting command due to timeout : pid 13093, scsi0, channel 0, id
0, lun
0 Write (6) 06 30 18 02 00
scsi0: Aborting CCB #13106 to Target 0
scsi : aborting command due to timeout : pid 13094, scsi0, channel 0, id
0, lun
0 <4>scsi0: CCB #13102 to Target 0 Aborted
Write (6) 06 30 24 02 00

 
 
 

1. big disk problems - or: big-disk problems?

Hi there!

I have really big problems. I try to set up a 45 GB Western Digital
Caviar 450AA (secondary IDE controller, master-drive). I patched my
machine with the recommended patch cluster which also contains patch no.
110202-01 for the ata-drivers. I am able to fdisk the drive with a
geometry file using fdisk with options. I am also able to partition the
disk with the native solaris 8 x86 format tool. I label the disk - fine
so far. But when I try to build a filesystem on it, newfs terminates wih
errors. I afterwards tried to set up a scsi-disk with 4,1 GB (IBM DCAS
34330). The same problem occured: newfs (as well as mkfs with options)
terminated with the following error message:

mkfs: bad value for size: 0 must be between 1024 and 0
mkfs: size reset to default 0
mkfs: bad value for ntrack: 6 must be between 1 and 0
mkfs: ntrack reset to default 16
seek error on sector -1: invalid argument

That's pretty strange, isn't it? I don't know wheter Solaris x86 is that
different from Solaris SPARC edition. Perhaps I'm too dumb to get this
machine working and should put my fingers off Solaris x86 edition.

Could anybody in this world help me? Or has anybody the same problems?
You know - it's just for my collegues: they are now calling me brad...

Greetings

SERGEJ

2. Xfree setup for ATI MACH64 Proturbo

3. Problem with ext2 fs on large SCSI disk?

4. Drivers for HP DeskJet 820Cxi printer and WiseCom Accelerator IV Modem

5. Kyocera FS 1600 or FS 1600+ Printer drivers ( FS-1600 FS-1600+)

6. RDP Client (newbie)

7. problems mounting fs from disk

8. read -p hangs in ksh script if exec()'ed from other program

9. Request for help: Linux hardware/disk problems (EXT2-fs)

10. PROBLEM: Kernel 2.5.19 oops when copying files from SMBFS fs to VFAT fs

11. 2.4.8 fs corruption and subsequent fs problems with links

12. 2.4.18-pre7: Problems linking fs/fs.o

13. problems mounting NT fs on Linux fs ...