lehan
asked on
Can't stat /dev/rdsk/... error message
Hi all,
I am having this strange problem which is causing me to bang my head against the wall!! read on...
I have a Sun Blade 2000 with a single 73GB disk running Solaris 8.
the disk is partitioned into / and /space
This is a development system for one of our customers and we are required to have a spare backup drive of the existing root drive, just in case.
I used ufsdump/ufsrestore to make an exact image of the root drive on the backup drive but after running "installboot" command and rebooting I get the annoying "can't stat /dev/rdsk/c1t1d0sx" error message and the system puts me in maintenance mode. If I try to run fsck, I get the same message. The disk can be detected using format and probe-scsi. Also, /etc/vfstab reflects the correct drive.
I have tried replacing the "dev, devices and path_to_install" files and directories from CDROM but to no gain...
any help is greatly apprecieted.
thx
lehan
I am having this strange problem which is causing me to bang my head against the wall!! read on...
I have a Sun Blade 2000 with a single 73GB disk running Solaris 8.
the disk is partitioned into / and /space
This is a development system for one of our customers and we are required to have a spare backup drive of the existing root drive, just in case.
I used ufsdump/ufsrestore to make an exact image of the root drive on the backup drive but after running "installboot" command and rebooting I get the annoying "can't stat /dev/rdsk/c1t1d0sx" error message and the system puts me in maintenance mode. If I try to run fsck, I get the same message. The disk can be detected using format and probe-scsi. Also, /etc/vfstab reflects the correct drive.
I have tried replacing the "dev, devices and path_to_install" files and directories from CDROM but to no gain...
any help is greatly apprecieted.
thx
lehan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think dd will work ok but remember whichever way you choose, unless you physically swap the disk connections between your boot and backup you will have to edit /etc/vfstab to reflect the new root device and also the OBP NVRAM boot device alias.
ASKER
Sorry for the late feedback, I was away for a while.
I tried several procedures including your procedure but to no gain.
I finally was able to solve it using the dd command. Only trick was to modify the /etc/dfstab to reflect the new drive and then reboot at the end of dd. the system throws an fsck error but it continues to boot normally. I had to then remodify dfstab to original state, reboot one more time and all worked fine from then. I had a functioning exact mirror image of my original drive.
The dd command I used was as follows:
dd if=/dev/rdsk/c0t0d0s2 of=/dev/rdsk/c0t1d0s2 bs=128k
where: 0t0d0s2 is original disk & c0t1d0s2 is new disk
slice 2 represents the entire disk.
Thanks for all your help.
I tried several procedures including your procedure but to no gain.
I finally was able to solve it using the dd command. Only trick was to modify the /etc/dfstab to reflect the new drive and then reboot at the end of dd. the system throws an fsck error but it continues to boot normally. I had to then remodify dfstab to original state, reboot one more time and all worked fine from then. I had a functioning exact mirror image of my original drive.
The dd command I used was as follows:
dd if=/dev/rdsk/c0t0d0s2 of=/dev/rdsk/c0t1d0s2 bs=128k
where: 0t0d0s2 is original disk & c0t1d0s2 is new disk
slice 2 represents the entire disk.
Thanks for all your help.
ASKER
Correction: make the disk entry changes in the /etc/vfstab and the /etc/dfstab. Sorry!
ASKER
I was also thinking of cloning the disks using the "dd" command, any suggestions on that?
Thank you for your input so far.
lehan