I removed the second controller and nothing changes. Something is
gimped up with debian on my system. I'll try another daily installer,
but I might have to switch distros here.
On 7/28/06, Frans Pop <[EMAIL PROTECTED]> wrote:
On Friday 28 July 2006 19:06, Ryan Rawson wrote:
&
designed to rescue a root part on a md
device - it doesn't seem to be trying to start the md device. I had
to modprobe raid1 and mdrun by hand, but I still ended up with the
busy error.
On 7/28/06, Geert Stappers <[EMAIL PROTECTED]> wrote:
On Thu, Jul 27, 2006 at 12:21:48PM -0700, R
Rescue mode doesn't work for me. When I try to start the md array I
end up with the same "device or resource" busy error.
Luckly the system is more or less scratch so reinstalling is not a big deal.
-ryan
On 7/27/06, Frans Pop <[EMAIL PROTECTED]> wrote:
On Thursday 27
Thanks for that.
So I assume I would just get the debs to some machine on the network
and scp them over right after the installation and perform a dpkg -i
on that... or is there a different/easier strategy?
-ryan
On 7/27/06, maximilian attems <[EMAIL PROTECTED]> wrote:
In-Reply-To=<[EMAIL PROT
Package: installation-reports
Boot method: netinst iso, cdrom boot
Image version: etch beta2 & daily July 26, 2006
Date: July 26th evening.
Machine: AMD CPU, NForce2 mobo Chipset.
Processor: AMD Athlon XP 2500+
Memory: 512 MB
Partitions:
this is typed in by hand since I can't boot the system:
5 matches
Mail list logo
