gmirror issue?

[Marin Atanasov]

Hi,

I was doing some tests under 8.0-RC1 and noticed that when I set-up a
root partition with gmirror, after the first reboot with the new
mirrored root partition the system is not able to continue the boot process.

The error message that is being printed is this:

pid 63 (swapon), uid 0: exited on signal 11
....
pid 65: (fsck), uid 0: exited on signal 11
Segmentation fault
Unknown error; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!


The full details about the implementation setup I'm using with
gmirror/gvinum are described here:
http://www.daemonforums.org/showthread.php?p=27010#post27010

Regards,
Marin
_______________________________________________
freebsd-geom@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-geom
To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."

[Marin Atanasov]

Marin Atanasov wrote:

> Hi,
>
> I was doing some tests under 8.0-RC1 and noticed that when I set-up a
> root partition with gmirror, after the first reboot with the new
> mirrored root partition the system is not able to continue the boot
> process.
>
> The error message that is being printed is this:
>
> pid 63 (swapon), uid 0: exited on signal 11
> ....
> pid 65: (fsck), uid 0: exited on signal 11
> Segmentation fault
> Unknown error; help!
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> The full details about the implementation setup I'm using with
> gmirror/gvinum are described here:
> http://www.daemonforums.org/showthread.php?p=27010#post27010
>
> Regards,
> Marin
>

Forgot to mention that this error only occurs the first time you boot
into your 8.0-RC1 system, after when you have set-up root with the new
mirror filesystem. This does not apply for 7.2

Also the real issue for this is that /etc/fstab contains one new line at
the end of the file like this:
^@^@^@^@

Removing that line fixes this.

Another thing that I've noticed is that /boot/loader.conf content it
missing. Needs to be re-created again.

And then you can boot into your mirrored root partition.

Does anyone know why these happen - I mean the strange entry in fstab
and the empty loader.conf files?

Regards,
Marin
_______________________________________________
freebsd-geom@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-geom
To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."

[Sean C. Farley-2]

On Thu, 1 Oct 2009, Marin Atanasov wrote:

> Marin Atanasov wrote:
>> Hi,
>>
>> I was doing some tests under 8.0-RC1 and noticed that when I set-up a
>> root partition with gmirror, after the first reboot with the new
>> mirrored root partition the system is not able to continue the boot
>> process.
>>
> Forgot to mention that this error only occurs the first time you boot
> into your 8.0-RC1 system, after when you have set-up root with the new
> mirror filesystem. This does not apply for 7.2
>
> Also the real issue for this is that /etc/fstab contains one new line
> at the end of the file like this:
> ^@^@^@^@

While I cannot help with the other issues, I wanted to state I have seen
this too.  I see these characters when installing via a serial
connection (using VirtualBox).  They appear after every line I paste
into the telnet connection (mode character).

Are you doing something similar?

Sean
--
scf@...
_______________________________________________
freebsd-geom@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-geom
To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."