Hi
I just did a system update and after I've rebooted it doesn't boot up any
more.
All I'm getting is a blank screen with a curser blinking at the top left
corner of the screen.
This system was running 7.0-STABLE
Any ideas as to how I can get it back up?
Regards
Reinhold
_
Hi
I just did a system update and after I've rebooted it doesn't boot up any
more.
All I'm getting is a blank screen with a curser blinking at the top left
corner of the screen.
This system was running 7.0-STABLE
Any ideas as to how I can get it back up?
Regards
Reinhold
__
A little update.
I can boot into freebsd using the life cd and can mount the disk when I'm
in fixit.
But from there on I have no idea what to do to fix this problem.
Can any one please help
Thanks
On Thu, October 23, 2008 19:51, Reinhold wrote:
> Hi
>
>
> I just did a system update and after I
On Thu, 23 Oct 2008 21:40:23 +0100 (BST)
Reinhold <[EMAIL PROTECTED]> wrote:
> A little update.
>
> I can boot into freebsd using the life cd and can mount the disk when
> I'm in fixit.
>
> But from there on I have no idea what to do to fix this problem.
Some quick checks:
- use fdisk (for exam
"Reinhold" <[EMAIL PROTECTED]> writes:
> A little update.
>
> I can boot into freebsd using the life cd and can mount the disk when I'm
> in fixit.
>
> But from there on I have no idea what to do to fix this problem.
Try reinstalling the bootloader. You can do that by going into the
sysinstall d
On Thu, October 23, 2008 21:57, Torfinn Ingolfsen wrote:
>
> Some quick checks:
> - use fdisk (for example: fdisk ad0) to check if the correct slice is
> active - use boot0cfg -v to check the bootcode of the disk you are booting
> from
>
Hi
Thanks for getting back to me.
Here is the info I have f
On Thu, October 23, 2008 22:02, Lowell Gilbert wrote:
>
> Try reinstalling the bootloader. You can do that by going into the
> sysinstall disk partitioning screens, but not changing any slice or
> partitioning settings.
>
Hi
I tried to do this as well with no success,
What I did notice was that i
Found the problem
Its not Freebsd, its the pci raid controller.
It was suggested to me on daemonforums.org to unplug all the drives and
then plug them in one by one until it happened again, and it did, it
happened when I plugged the first drive into the controller.
Any ways, now I have to figure
