| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
How Do I Rebuild the Root Disk???
I have a client that has a DEC3000 running V3.2C. We want to update it
to V4.0B. I've upgraded the firmware, to V6.9, and updated the Turbo
code...
In trying to do the install, we've run into several brickwalls with
disk space. In various attempts at linking files to other devices,
deleting files, etc. we've managed to fragment the drive.
So, I actually have 2 questions?
1.) When the installupdate fails, how does it delete the files it was
writing to disk "before" it decided it had no more space?
We noticed that the installupdate fails and immediately comes back to
single user mode... ???
2.) How do you rebuild an hard drive, ie: the drive that houses the /
partition?
In VMS you would boot standalone backup and then restore from tape. Is
there something similar in d-Unix?
thanks,
/Mic
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 8659.1 | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Thu Jan 30 1997 18:31 | 10 | |
Boot the distribution media for the version you want to restore. Prior to V4 you had three options; Basic, Advanced and System Management. Chose system management. This will provide a root file system that you can use to recreate the original root and restore your backup. There might be a few extra steps for mirrored root file systems, so check the LSM documentation. V4 also offers a system management option, though I recall it being a little less obvious. | |||||
| 8659.2 | partition a not big enough? | STOSS1::HORVATH | Thu Jan 30 1997 18:43 | 23 | |
Mic,
I'm not familiar with v4.0, however I ran into your problem before
under 3.2c while doing an upgrade that is why see not 8651, I'm taking
precautions. The install book page f-15 says installupdate needs 24004
blocks on root 198840 on usr and 430 on var for 3.2c.
My guess is that your unable to boot. The upgrade may not have
effected the bootblock or file domain root assuming your using ADVFS
so boot from cdrom. Booting from cdrom I consider equivalent to
standalone VMS mode. Select System Management Option, then type
/sbin/bcheckrc to mount / and /usr /var. Once / is mounted you will be
able to vrestore your backup of /. One gotcha I ran into is the
version of vrestore, If you patched it, the vrestore on the CDROM may
not work on your saveset because the new vdump may not be read with the
old vresore. This is a different problem, however, but
one that drove me nuts.
If your using UFS type mount -u to mount root rw then will have to
mount /usr I believe manually. Type /usr/sbin/fsck to repair file systems.
Hope this Helps,
Jeff
| |||||
| 8659.3 | I'll give it a shot! | SCASS1::GALVIN | The Energizer Bunny's Trainer... | Thu Jan 30 1997 22:09 | 4 |
Thanks to .1 and .2, I'll give it a shot! I'll report back...
/Mic
| |||||