> >>I'm running openbsd 4.0 (yeh old I know but it's a vital system > >>that I'm replacing but it processes data that makes a lot of money). > > > >Better replace the disk tomorrow, then. Or, implement the software > >on a new system, and take the hit on some downtime while it's being > >replaced. > > > Thanks for the tip. Just bought one. > > >Those are signs of odd errors on the physical media itself. OpenBSD > >can (and may) crash due to bad sectors and failed writes. I did > >allow a system to limp along on a bad drive for nearly a year while > >I tried to source a very old (no longer available) drive. > > > > The old disk is a 40Gb IDE disk and the new one one is a 120Gb disk. > If I want to clone the disk can I just cat /dev/sd0 > /dev/sd1 if I > boot off the install cd?
No. Do a proper install, then do a dump|restore of the filesystems you need to preserve. > I will rebuild this system on another box but to make sure the disk > doesn't die instantly I want to clone it asap since it makes cash. > > I've got another system on the boil with a 36Gb 15k scsi disk and > decent hardware but I want to keep this mac mini server going just > long enough to role the new server out. > > Last night I connected a USB disk and tried to use dump to clone /dev/ > rwd0a but it was only dumping the first 4Gb's which was irritating to > put it mildly. I used dump -0auf /usb/root.dump /dev/rwd0a Why is your / that big? Do you really need to dump it as one whole? > I also tried dump -0auB 4198400 -f /usb/root.dump /dev/rwd0a and > still it bombs out asking for the next media to be inserted after 4gb's. > > Doesn't matter what I try still only dumps 4gb's. The system is a g4 > which is a 32bit cpu which is the only clue I thought of that would > limit me to 4gb's. > > > khalid
