30 Mar
2007
30 Mar
'07
6:53 a.m.
Does anyone happen to know where I can find a "whole disk" device file within
NeXTstep?
I was going to clone the OS drive of a mono Slab onto another (identical
model) hard disk, figuring I'd just 'dd' the contents from one to the other.
Problem is there's no obvious "whole disk" device under /dev, either for the
OS drive or the "target" drive that I'm hanging off the back of the Slab.
/usr/adm/messages gives me a couple of relevant entries:
<drive name> as sd0 at sc0 target 1 lun 0
<drive name> as sd1 at sc0 target 2 lun 0
... where <drive name> is just the vendor's ID string (Seagate ST1480N) and
the drive's firmware revision. Unfortunately there's no such files as the
obvious /dev/sd0 or /dev/sd1. There are /dev/sd0<a..h> and /dev/sd1<a..h>
files, so maybe one of those (h?) corresponds to the whole disk? (according to
'mount', /dev/sd0a is the root OS partition)
I could just pull the OS drive out of the Slab and hook both drives up to a
Linux box and 'dd' there - but I thought I'd take the route of minimum
dismantling, and of course I assumed it'd be an easy 5 minute job :-)
cheers
Jules
30 Mar
30 Mar
7:27 a.m.
On Fri, 2007-03-30 at 08:53 -0500, Jules Richardson wrote:
Does anyone happen to know where I can find a
"whole disk" device file within
NeXTstep?
I was going to clone the OS drive of a mono Slab onto another (identical
model) hard disk, figuring I'd just 'dd' the contents from one to the other.
Problem is there's no obvious "whole disk" device under /dev, either for
the
OS drive or the "target" drive that I'm hanging off the back of the Slab.
/usr/adm/messages gives me a couple of relevant entries:
<drive name> as sd0 at sc0 target 1 lun 0
<drive name> as sd1 at sc0 target 2 lun 0
... where <drive name> is just the vendor's ID string (Seagate ST1480N) and
the drive's firmware revision. Unfortunately there's no such files as the
obvious /dev/sd0 or /dev/sd1. There are /dev/sd0<a..h> and /dev/sd1<a..h>
files, so maybe one of those (h?) corresponds to the whole disk? (according to
'mount', /dev/sd0a is the root OS partition)
I could just pull the OS drive out of the Slab and hook both drives up to a
Linux box and 'dd' there - but I thought I'd take the route of minimum
dismantling, and of course I assumed it'd be an easy 5 minute job :-)
Is there an rsd0? That'd be the raw version of the disk that you should
be able to copy. Another option might be sd0c which *should* be the
whole disk if it was set up bsdish.
Brian
cheers
Jules
11:27 a.m.
Brian Wheeler wrote:
Is there an rsd0? That'd be the raw version of
the disk that you should
be able to copy. Another option might be sd0c which *should* be the
whole disk if it was set up bsdish.
Someone else suggested sd0c too. I decided not to mess about with it any more
though and dropped the drives into a linux machine and dd'ed them there.
Seems to have done the trick anyway, but I'm a little wary now - although the
drives were identical vendor / models, the 'new' disk was reporting five more
cylinders than the 'old' one when under Linux (yet the same number of heads
and sectors per track), and I'm not sure of the reason for that.
Possibly there was a firmware "feature" in the "smaller" drive which
meant the
full drive capacity wasn't being utilised, but that seems like a pretty major
flaw in the days when a few MB here and there was precious. If not then why
someone / something (the NeXTstep installer, presumably) would format the
drive below total capacity, I don't know.
cheers
Jules
1:29 p.m.
On Friday 30 March 2007 14:27, Jules Richardson wrote:
Seems to have done the trick anyway, but I'm a
little wary now -
although the drives were identical vendor / models, the 'new' disk
was reporting five more cylinders than the 'old' one when under Linux
(yet the same number of heads and sectors per track), and I'm not
sure of the reason for that.
Two drives with the same model # and slightly different geometries isn't
at all unusual, at least for modern-ish disks.
Pat
--
Purdue University Research Computing --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
12:13 p.m.
On 30/3/07 13:53, "Jules Richardson" <julesrichardsonuk at yahoo.co.uk>
wrote:
Does anyone happen to know where I can find a "whole disk" device file within
NeXTstep?
My slab is set to show me the 'ugly' side of a NeXTStep boot, devices and
all so once I fit the new memory I borrowed from work I'll fire it up and
see what device it likes to play with.
Cheers
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
6259
days inactive
6259
days old
5 comments
5 participants
participants (5)
-
bdwheele＠indiana.edu -
bear＠typewritten.org -
julesrichardsonuk＠yahoo.co.uk -
pat＠computer-refuge.org -
witchy＠binarydinosaurs.co.uk