ecord on the MBR of device 0x80, if
such a boot record is desired, this is one way to have it
written. Use of mbr is the other
way to force writing to the MBR of device 0x80.
regards,
drbob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
drbob wrote:
I'll post here if the changes I suggest above have any effect.
regards,
drbob
Before I did this I tried a few different settings in lilo.conf and had
some success :-).
Setting raid-extra-boot=mbr-only avoided the error I was seeing previously:
:/etc# lilo -v
LILO ve
Alvin Oga wrote:
what exaactly did you type BEFORE you removed the bad disk ??
raidhotadd, raidhotremove, etc, etc.. is required ( aka good idea )
I use mdadm to manage my array. The command was
mdadm --set-faulty /dev/md1 /dev/hda1 --remove /dev/md1 /dev/hda1
(repeated for the other par
put it in at the same
time as I replaced the failed raid drive).
I haven't changed lilo.conf since I set the array up a year ago so I had
been hoping things would "just work" oh well :-)
I'll post here if the changes I suggest above have any effect.
regards,
drbob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Mike Bird wrote:
On Sun, 2006-01-15 at 09:59, drbob wrote:
I've replaced a failed disk in my raid 1 setup. I replaced the disk (hda
on-board ide), however the system then hung on reboot, this was because
hda, being blank, had no MBR. The second disk (hde) is plugged i
board
controller? This would appear to be a simple way around the issue but
I'm not sure if this would break the array in some other way.
Any help solving this would be much appreciated.
regards,
drbob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
drbob wrote:
Hello,
I'm trying to implement an opevpn server on my debian box. The first
step was to recompile my kernel (2.4.32) with TUN?TAP support built
in. I did this and created the /dev/net/tun device however it does not
work. cat /dev/net/tun returns:
cat: /dev/net/tun:
r the
only suggestion there is to link /usr/include/linux and /usr/include/asm
to the current kernel source directory, afaik this is not the debian way
and I don't know what else I'd break if I did this. Is there a better
way to solve the problem?
regards,
drbob
--
To UNSUBSCRIBE,
8 matches
Mail list logo
