Hi,
Thank you, now the problem is solved. But while I was testing an
exact same mborad I got from ebay, I noticed that the replacing board
name my SATA differently from the old board, its designated as ad10
and ad12 instead of ad4 and ad6. What is the mechanism that underlie
this?? thank you!!
On Mon, 30 Mar 2009 08:20:46 -0400, Tsu-Fan Cheng tfch...@gmail.com wrote:
But while I was testing an
exact same mborad I got from ebay, I noticed that the replacing board
name my SATA differently from the old board, its designated as ad10
and ad12 instead of ad4 and ad6. What is the mechanism
On Monday 30 March 2009 14:46:08 Polytropon wrote:
Note that this change of the device name usually requires changes
in /etc/fstab, e. g. ad4 - ad10 to make the system start on this
hardware.
fstab problem can be solved by using glabel sensibly. Also, isn't
ATA_STATIC_ID supposed to solve
Hi,
I was having a little trouble with my computer, first thought was
that the mboard was fried, but later found out it was the power supply
and replaced it. The computer started but failed to boot, here is what
it's been complaining,
exec /sbin/init error 8
exec /sbin/init.bak error 8
exec
On Sun, 29 Mar 2009 14:23:13 -0400, Tsu-Fan Cheng tfch...@gmail.com wrote:
init: not found in path /sbin/ (a lot of paths)
panic: no init
what is that??
The init process is the root of the FreeBSD startup, and the last
part of the OS loader cannot find it, so the OS cannot start.
