On 10/15/09, PJ wrote:
> While trying to learn and understand the dump-retore process, I messed
> up the ad4s1a partition and could not boot. To fix it I restored a
> dumpfile of ad12s1a which is, for all intents and purposes, the same as
> ad4s1a. I then boot from ad4 and surprise, surprise...
>
On Thu, 15 Oct 2009 19:08:12 -0400, PJ wrote:
> Gag is really about the simplest you can find... it is installed on the
> main drive that is selected by bios and it works from there. I have
> found it to be quite safe and reliable. Only difficulty is sometimes to
> figure ;out what dist it is boot
Polytropon wrote:
> On Thu, 15 Oct 2009 14:42:24 -0400, PJ wrote:
>
>> But sysinstall will overwrite all the info on the disk and that defeats
>> the whole purpose of the exercise.
>>
>
> If you only change a slice's state and add an MBR, it won't
> do anything to the data inside the slice
On Thu, 15 Oct 2009 14:42:24 -0400, PJ wrote:
> But sysinstall will overwrite all the info on the disk and that defeats
> the whole purpose of the exercise.
If you only change a slice's state and add an MBR, it won't
do anything to the data inside the slice.
> What complicates matters is the u
Polytropon wrote:
> On Thu, 15 Oct 2009 12:22:29 -0600 (MDT), Warren Block
> wrote:
>
>> The /etc/fstab from ad12 will point at ad12. After restoring on ad4,
>> did you edit fstab to now have ad4 entries?
>>
>
> Ha! Excellent point; I missed to see this obvious thing.
> Next to booting,
Polytropon wrote:
> On Thu, 15 Oct 2009 12:13:08 -0400, PJ wrote:
>
>> add another thought...
>>
>> If I change the mbr on the ad12 then mount ad4s1a to /mnt copy
>> /mnt/boot/boot0 to /boot/boot0.tmp and then copy the modified
>> /boot/boot0 (for ad4) back to /mnt/boot/ and then umount ad4s1a
On Thu, 15 Oct 2009 12:22:29 -0600 (MDT), Warren Block
wrote:
> The /etc/fstab from ad12 will point at ad12. After restoring on ad4,
> did you edit fstab to now have ad4 entries?
Ha! Excellent point; I missed to see this obvious thing.
Next to booting, the /etc/fstab mechanism is very importan
On Thu, 15 Oct 2009, PJ wrote:
While trying to learn and understand the dump-retore process, I messed
up the ad4s1a partition and could not boot. To fix it I restored a
dumpfile of ad12s1a which is, for all intents and purposes, the same as
ad4s1a. I then boot from ad4 and surprise, surprise...
On Thu, 15 Oct 2009 12:13:08 -0400, PJ wrote:
> add another thought...
>
> If I change the mbr on the ad12 then mount ad4s1a to /mnt copy
> /mnt/boot/boot0 to /boot/boot0.tmp and then copy the modified
> /boot/boot0 (for ad4) back to /mnt/boot/ and then umount ad4s1a --- I
> should be ok, OK? Hav
On Thu, 15 Oct 2009 12:07:17 -0400, PJ wrote:
> I see from the boot process that this should fix it...
> # fdisk -B -b /boot/boot0 ad4
> but...
> how do I get this onto the right disk? If I boot from ad4 or ad12 and
> change the mbr, then it will be the ad12 that will be booting from ad4
> and vic
On Thu, 15 Oct 2009 11:36:56 -0400, PJ wrote:
> I imagine it is something in the boot files... but how to fix that?
The easiest way is to prepare the disk with sysinstall. The
steps usually involve:
1. creation of slice, usually covering whole disk
2. marking the slice "active"
PJ wrote:
> While trying to learn and understand the dump-retore process, I messed
> up the ad4s1a partition and could not boot. To fix it I restored a
> dumpfile of ad12s1a which is, for all intents and purposes, the same as
> ad4s1a. I then boot from ad4 and surprise, surprise...
> #df shows we h
PJ wrote:
> While trying to learn and understand the dump-retore process, I messed
> up the ad4s1a partition and could not boot. To fix it I restored a
> dumpfile of ad12s1a which is, for all intents and purposes, the same as
> ad4s1a. I then boot from ad4 and surprise, surprise...
> #df shows we h
While trying to learn and understand the dump-retore process, I messed
up the ad4s1a partition and could not boot. To fix it I restored a
dumpfile of ad12s1a which is, for all intents and purposes, the same as
ad4s1a. I then boot from ad4 and surprise, surprise...
#df shows we have been booted from
14 matches
Mail list logo
