Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Aug 1997 21:48:54 -0700 (PDT)
From:      Ian Kallen <ian@gamespot.com>
To:        freebsd-hackers@freebsd.org
Subject:   dead disk
Message-ID:  <Pine.BSF.3.95q.970817213738.6917B-100000@ns2.gamespot.com>

next in thread | raw e-mail | index | archive | help
What a grrrreat weekend I'm having    >:'L    
ugh!

Evidently one of the "spare disks" we had laying around that I had thought
would suit me for my needs for additional disk space must have majorly
malfunctioned: what was my system disk went south on me.  I nabbed another
disk (brand new this time, it had been allocated for another project but I
need to get this machine back to life...), installed 2.2-970816.  Now I
have my old dead disk in an enclosure.  When I try to fsck it, I get this
crap:

Aug 18 04:34:58 scorn /kernel: , retries:2
Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033
csi:1,79,7,3b asc:16,0 Data s
ynchronization mark error field replaceable unit: 15
Aug 18 04:34:59 scorn /kernel: , retries:1
Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033
csi:1,79,7,3b asc:16,0 Data s
ynchronization mark error field replaceable unit: 15
Aug 18 04:34:59 scorn /kernel: , FAILURE
Aug 18 04:34:59 scorn /kernel: pid 162 (fsck), uid 0: exited on signal 8
(core dumped)

Everything was fine until I stuck that damn other disk...arg.  Anyway,
either of the partitions, if I try to access them, I'm SOL. However, I can
see the disklabel fine.  See:

# disklabel sd3
# /dev/rsd3c:
type: SCSI
disk: sd0s1
label:
flags:
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 1012
sectors/unit: 2074592
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:    65536        0    4.2BSD        0     0     0   # (Cyl.    0 - 31)
  b:   262144    65536      swap                        # (Cyl.   32 -
159)
  c:  2074592        0    unused        0     0         # (Cyl.    0 -
1012*)
  e:  1746912   327680    4.2BSD        0     0     0   # (Cyl.  160 -
1012*)

So is all hope lost for this disk?  To rub my face in it, the back up of
this system was incomplete and munged.  Any suggestions for reviving this
poor beast would be most appreciated!

Thanks,
-Ian

--
Ian Kallen						ian@gamespot.com	
	Director of Technology and Web Administration
		SpotMedia Communications
http://www.gamespot.com/		http://www.videogamespot.com/





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970817213738.6917B-100000>