Hi,
Recently, I have configured my ES-250 Sun Enterprise server to mirror
the two disks using Solstice 4.2 (OS 8)
I was able to mirror the two disks (c0t0d0s.. and c0t12d0s..)
sucessfully.
Each disk lay out as followed
root  s0
usr   s1
swap  s3
opt   s4
home  s5
var   s6
unassigned  s7  (is used to contain the state
database)

Everything was working fine until I decided to simulate by
switch the drive and location of these.
Upon powering off the system, I removed c0t0d0 and
placed it in c0t8d0.  I then removed c0t12d0
(mirror)and placed it in c0t0d0 and then powering the
system on, I can see the following
Sun Enterprise 250  400MHZ
OpenBoot 3.22   1024 MB Memory ...
Ethernet Address 0:3:ba:....  Host ID ...
Initialize memory
Boot device:  disk  file and args:
Then it just sit there, like it waiting for something.
I waited and waited for hour and still nothing
changed.  I can see the power LED is on and that's
the only LED is lid on the ES.-250, the other 5 LED is off.

I tried to place the disks back to its original location and
boot but it still failed, and resulted the same as mention above.

Now, neither one of these disks (Primary and mirror) boot.
I booted from CD and tried to mount the root by
issuing this command
# mount /dev/dsk/c0t0d0s0 /mnt
and it said
mount: no such device
Mount: can not mount /dev/dsk/c0t0d0s0
I figured if I can mount the root then I can go in and modified
the /etc/vfstab and boot w/o the SVM.
My two questions are
Does anyone know how I can mount this root partition?
This is the only one I can't not mount.
The other slices mount no problem at all.

Phong

[ Post a follow-up to this message ]

Did you try to fix this partition using the fsck command.

fsck /dev/rdsk/c0t0d0s0

See the manpage for fsck, you may need use -o b=32 option to correct
some superblock problems. the -N option will show you all alternative
superblocks to use.


"phongle" <phongle_1959@yahoo.com> a écrit dans le message de news:
15da5e75.0306271859.58009f31@posting.google.com...
quote:

> Hi,
> Recently, I have configured my ES-250 Sun Enterprise server to mirror
> the two disks using Solstice 4.2 (OS 8)
> I was able to mirror the two disks (c0t0d0s.. and c0t12d0s..)
> sucessfully.
> Each disk lay out as followed
> root  s0
> usr   s1
> swap  s3
> opt   s4
> home  s5
> var   s6
> unassigned  s7  (is used to contain the state
> database)
>
> Everything was working fine until I decided to simulate by
> switch the drive and location of these.
> Upon powering off the system, I removed c0t0d0 and
> placed it in c0t8d0.  I then removed c0t12d0
> (mirror)and placed it in c0t0d0 and then powering the
> system on, I can see the following
> Sun Enterprise 250  400MHZ
> OpenBoot 3.22   1024 MB Memory ...
> Ethernet Address 0:3:ba:....  Host ID ...
> Initialize memory
> Boot device:  disk  file and args:
> Then it just sit there, like it waiting for something.
> I waited and waited for hour and still nothing
> changed.  I can see the power LED is on and that's
> the only LED is lid on the ES.-250, the other 5 LED is off.
>
> I tried to place the disks back to its original location and
> boot but it still failed, and resulted the same as mention above.
>
> Now, neither one of these disks (Primary and mirror) boot.
> I booted from CD and tried to mount the root by
> issuing this command
> # mount /dev/dsk/c0t0d0s0 /mnt
> and it said
> mount: no such device
> Mount: can not mount /dev/dsk/c0t0d0s0
> I figured if I can mount the root then I can go in and modified
> the /etc/vfstab and boot w/o the SVM.
> My two questions are
> Does anyone know how I can mount this root partition?
> This is the only one I can't not mount.
> The other slices mount no problem at all.
>
> Phong

[ Post a follow-up to this message ]

Yep got that problem on my SGI at the moment. I tried xfs_restore but that
said there are lots of errors and it fixed most probs but I decided to
recover all the data I can and pull the rest from my DLT backup tape
system. I'm going to first run dd on the disk to write zero to the whole
disk then I'll partition it and do a new mkfs. I will then test the disk
for bad blocks and errors. I take it you have the data on tape or another
media?

Khalid Schofield

On 28 Jun 2003, phongle wrote:
quote:

> Yes, I tried to fsck and it said "Cannot read block 143272224.  I
> tried to a different super block and it said the same thing.
> Do you have any other ideas?
> Thanks
> Phong
> phongle_1959@yahoo.com (phongle) wrote in message news:<15da5e75.030627185
9.58009f31@posting.google.com>... 
>

[ Post a follow-up to this message ]