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:
no, the md doesn't
On Thu, Jul 27, 2006 at 12:21:48PM -0700, Ryan Rawson wrote:
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.
Which device was detected/suggested by rescue? The md?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
no, the md doesn't exist at all. Only physical disks, using paths in
/dev/discs. What I did is to use alt-f2 before I hit that portion of
the rescue and tried to start the md array, which then failed with the
device or resource busy error.
Looks like rescue isn't really designed to rescue a
On Friday 28 July 2006 19:06, Ryan Rawson wrote:
no, the md doesn't exist at all. Only physical disks, using paths in
/dev/discs. What I did is to use alt-f2 before I hit that portion of
the rescue and tried to start the md array, which then failed with the
device or resource busy error.
In-Reply-To=[EMAIL PROTECTED]
hello,
Comments/Problems:
The machine is set to install on /dev/md0 raid1. The installer worked
like a charm, and on reboot into the live system I end up with major
failure, the scripts try to start the raid system with mdrun but I end
up with the error;
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
On Thursday 27 July 2006 20:18, Ryan Rawson wrote:
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?
You don't need to reinstall. Just use the rescue mode
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 July 2006 20:18, Ryan
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:
9 matches
Mail list logo
