I've posted the following message in the newsgroups
and a couple other places, without much success. I
got this address as I was about to try the mkraid
--force option when I saw this address. Executing
the actual command frightened me away by saying it
was about to destroy the contents of my drive...
I'd really like to try and recover this. Amongst
other things, it has a copy of my genealogy on it
that I've spent way too many hours on. (yes, i have
a backup, but it's really just in html form...)
----------original message----------
Having big trouble with my server here. Anyone have any
advice?
This unit was working perfectly fine. I powered it
off, transported it to the office, and powered it back on.
I was very careful and the machine did not get dropped,
shaken, bumped, or severely jarred in any way.
Don't even know what the "bad magic" error means...
sdc, sdd, sde, sdf drives are all in one external chassis,
while sdg and sdh are in individual external chassis. sda
and sdb are internal.
(Running rh6.1 on a sparc u2)
Here's the log clipping from booting up:
----------------
Mar 30 20:06:00 nachoz kernel: scsi : detected 1 SCSI cdrom 8 SCSI disks total.
Mar 30 20:06:00 nachoz kernel: esp0: target 6 asynchronous
Mar 30 20:06:00 nachoz kernel: Uniform CDROM driver Revision: 2.56
Mar 30 20:06:00 nachoz kernel: esp0: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp0: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 2 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdd: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 3 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sde: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 4 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdf: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdg: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdh: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: Partition check:
Mar 30 20:06:00 nachoz kernel: sda: sda1 sda3
Mar 30 20:06:00 nachoz kernel: sdb: sdb1 sdb2 sdb3
Mar 30 20:06:00 nachoz kernel: sdc: sdc1 sdc3
Mar 30 20:06:00 nachoz kernel: sdd:Dev 08:30 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sde:Dev 08:40 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdf:Dev 08:50 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdg:Dev 08:60 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdh: sdh1 sdh3
----------------
If I try running the following, I get:
# e2fsck /dev/sdg
e2fsck 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdg
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
My raidtab is as follows:
----------------
#
# compatible (old) RAID0 setup:
#
raiddev /dev/md1
raid-level 0
nr-raid-disks 3
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdh1
raid-disk 0
device /dev/sdb2
raid-disk 1
device /dev/sdg1
raid-disk 2
raiddev /dev/md2
raid-level 0
nr-raid-disks 4
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
device /dev/sde1
raid-disk 2
device /dev/sdf1
raid-disk 3
----------------
It isn't starting the module properly, I have to do
insmod raid0. After that, I get:
# cat /proc/mdstat
Personalities : [raid0]
read_ahead not set
unused devices: <none>
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: TOSHIBA Model: XM-5401TASUN4XCD Rev: 1036
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
# more /proc/scsi/esp/*
::::::::::::::
0
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0062ff8
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 6 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
6 00000081 [0f,04] yes no
::::::::::::::
1
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0078cbc
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 1 2 3 4 ]
Target # config3 Sync Capabilities Disconnect Wide
1 000000c3 [0f,04] yes yes
2 000000c3 [0f,04] yes yes
3 000000c3 [0f,04] yes yes
4 000000c3 [0f,04] yes yes
::::::::::::::
2
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0085aec
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
--
Andy Harrison
Time Warner Cable of Maine
Road Runner Associate Systems Administrator
[EMAIL PROTECTED]
ICQ: 1467660 AIM: AndyHarrisonRR
