Copying disk - what am I doing wrong?

#11 (**permalink**) 01-16-2008, 10:35 AM

On 2007-10-21, Dave <nowhere@nowhere.com> wrote:

> # luxadm set_boot_dev /dev/dsk/c1t0d0s0
>
> which updated boot-device in the EEPROM

Ahh, I didn't know about that. That's useful.

> Its a bit worrying I don't feel as confident at restoring data from a
> damaged disk as I used to on the Ultra 80. But I guess I'll find a way!

<AOL>

--
"Be thankful that you have a life, and forsake your vain
and presumptuous desire for a second one."
[email me at huge {at} huge (dot) org <dot> uk]

#12 (**permalink**) 01-16-2008, 10:35 AM

On Oct 21, 8:20 am, Dave <nowh...@nowhere.com> wrote:
> Trinean wrote:
> > "Dave" <nowh...@nowhere.com> wrote in messagenews:47194738@212.67.96.135...
> >> Is there anything else I have overlooked, before I have another go at
> > this?
>
> >http://www.sunshack.org/data/sh/2.1/...data/syshbk/co...
>
> > Trinean
>
> Thanks everyone. I *finally* got there:
>
> Filesystem size used avail capacity Mounted on
> /dev/dsk/c1t1d0s0 19G 7.1G 12G 38% /
> /devices 0K 0K 0K 0% /devices
> ctfs 0K 0K 0K 0% /system/contract
> proc 0K 0K 0K 0% /proc
> mnttab 0K 0K 0K 0% /etc/mnttab
> swap 14G 1.4M 14G 1% /etc/svc/volatile
> objfs 0K 0K 0K 0% /system/object
> /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
> 19G 7.1G 12G 38%
> /platform/sun4u-us3/lib/libc_psr.so.1
> /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
> 19G 7.1G 12G 38%
> /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
> fd 0K 0K 0K 0% /dev/fd
> swap 14G 1.1M 14G 1% /tmp
> swap 14G 40K 14G 1% /var/run
> /dev/dsk/c2t3d0s2 67G 64G 2.9G 96% /mnt
> /dev/dsk/c1t2d0s7 135G 64G 70G 48% /export/home
> /dev/dsk/c1t1d0s3 108G 18G 88G 18% /usr/local
> /vol/dev/dsk/c0t6d0/l
> 622M 622M 0K 100% /cdrom/l
>
> but not without a lot of hassles.
>
> I was getting close at some points to thinking it would be easier to
> reinstall the OS on the new disk and then copy what I needed back from
> the original root partition.
>
> What was odd was to find the root partition of a disk could be
> /dev/dsk/c1t1d0s1 when in to top or bottom slot of the Blade 2000.
> Unlike the SCSI disks I am used to, the 'cx' where x was 1 or 2, do not
> stay constant with the two slots.
>
> Randy's suggestion of:
> 1. mv /a/etc/path_to_inst /a/etc/path_to_inst.original
> 2. rm /a/etc/path_to_inst.old
> 3. devfsadm -v -C -r /a
>
> did not work for me - it simply never updated /a/etc/install

devfsadm -v -C -r /a -p /a/etc/path_to_inst will update /a/etc/
path_to_inst. But in order to get /dev/dsk right, remove /dev/dsk
before do devfsadm.

Anyway, I am glad you already work it out.

Victor

>
> Finally more by luck than skill I got to the point it would boot if I typed
>
> OK> boot disk0
>
> rather than
> OK> boot disk
>
> Then the page Trinean pointed me to on Sunshackhttp://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/co...
>
> got that fixed with:
>
> # luxadm set_boot_dev /dev/dsk/c1t0d0s0
>
> which updated boot-device in the EEPROM
>
> Its a bit worrying I don't feel as confident at restoring data from a
> damaged disk as I used to on the Ultra 80. But I guess I'll find a way!

#13 (**permalink**) 01-16-2008, 10:35 AM

On Oct 22, 10:13 am, victorfeng1...@yahoo.com wrote:
> On Oct 21, 8:20 am, Dave <nowh...@nowhere.com> wrote:
>
>
>
> > Trinean wrote:
> > > "Dave" <nowh...@nowhere.com> wrote in messagenews:47194738@212.67.96.135...
> > >> Is there anything else I have overlooked, before I have another go at
> > > this?
>
> > >http://www.sunshack.org/data/sh/2.1/...data/syshbk/co...
>
> > > Trinean
>
> > Thanks everyone. I *finally* got there:
>
> > Filesystem size used avail capacity Mounted on
> > /dev/dsk/c1t1d0s0 19G 7.1G 12G 38% /
> > /devices 0K 0K 0K 0% /devices
> > ctfs 0K 0K 0K 0% /system/contract
> > proc 0K 0K 0K 0% /proc
> > mnttab 0K 0K 0K 0% /etc/mnttab
> > swap 14G 1.4M 14G 1% /etc/svc/volatile
> > objfs 0K 0K 0K 0% /system/object
> > /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
> > 19G 7.1G 12G 38%
> > /platform/sun4u-us3/lib/libc_psr.so.1
> > /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
> > 19G 7.1G 12G 38%
> > /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
> > fd 0K 0K 0K 0% /dev/fd
> > swap 14G 1.1M 14G 1% /tmp
> > swap 14G 40K 14G 1% /var/run
> > /dev/dsk/c2t3d0s2 67G 64G 2.9G 96% /mnt
> > /dev/dsk/c1t2d0s7 135G 64G 70G 48% /export/home
> > /dev/dsk/c1t1d0s3 108G 18G 88G 18% /usr/local
> > /vol/dev/dsk/c0t6d0/l
> > 622M 622M 0K 100% /cdrom/l
>
> > but not without a lot of hassles.
>
> > I was getting close at some points to thinking it would be easier to
> > reinstall the OS on the new disk and then copy what I needed back from
> > the original root partition.
>
> > What was odd was to find the root partition of a disk could be
> > /dev/dsk/c1t1d0s1 when in to top or bottom slot of the Blade 2000.
> > Unlike the SCSI disks I am used to, the 'cx' where x was 1 or 2, do not
> > stay constant with the two slots.
>
> > Randy's suggestion of:
> > 1. mv /a/etc/path_to_inst /a/etc/path_to_inst.original
> > 2. rm /a/etc/path_to_inst.old
> > 3. devfsadm -v -C -r /a
>
> > did not work for me - it simply never updated /a/etc/install
>
> devfsadm -v -C -r /a -p /a/etc/path_to_inst will update /a/etc/
> path_to_inst. But in order to get /dev/dsk right, remove /dev/dsk
> before do devfsadm.

remove /dev/rdsk too.

>
> Anyway, I am glad you already work it out.
>
> Victor
>
>
>
> > Finally more by luck than skill I got to the point it would boot if I typed
>
> > OK> boot disk0
>
> > rather than
> > OK> boot disk
>
> > Then the page Trinean pointed me to on Sunshackhttp://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/co...
>
> > got that fixed with:
>
> > # luxadm set_boot_dev /dev/dsk/c1t0d0s0
>
> > which updated boot-device in the EEPROM
>
> > Its a bit worrying I don't feel as confident at restoring data from a
> > damaged disk as I used to on the Ultra 80. But I guess I'll find a way!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode