Daniel Rock wrote:
James Dickens schrieb:
tried it again... same results... restores the damm efi label.. disk
starts on block 34 not 0, there is no slice 2... that solaris
ijnstaller demands
can not start any track at block 0.. so i can't create a backup slice
aka 2.
This is a SCSI disk? Then you can send SCSI commands directly to the
drive which overwrite sector 0.
I found a small test program to become famliar with USCSI I wrote a long
time ago. It can also be used to overwrite the label:
http://www.deadcafe.de/disk.c
While folks are on this topic, does anyone know a reason why Solaris is
so dead-set against giving you access to a block device that represents
a whole SCSI LUN? It's the second (after the various Windows flavours)
most annoying OS I use in terms of not letting you just blat data
straight to the disk.
Apart from this case of lifting the EFI curse from a disk, direct LUN
access was also handy for moving data between non-networked hosts with
no common partition scheme or filesystem support (e.g. AmigaOS and BeOS,
some years back). Writing tar files straight to disk blocks is better
than nothing in those cases. To do this on my old Sparc 5, I used to
have to make a label on the disk with format, then send the tar file
straight to slice 2, thus erasing the disk label. Without special magic
SCSI-banging progs, I couldn't go back the other way from my home BeBox
to my work Solaris machine.
It's also nice for hard disk disaster recovery; if for some reason the
old-style Solaris partition table got lunched (blatting straight to
slice 2 for instance), having a disk image stashed away somewhere else
is great for your confidence when you're relabelling the disk and
reconstructing filesystems.
-Jason
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
