Booted into the slack rescue disk this morning (busybox) and tried email the
log but the telnet can't handle pipes or something (it didn't work :-() so
I'll guess I'll have to write the whole thing down.
fdisk did recognize all the partitions as they were on the PIIX controllers
the disks come from (on the hd[e-h] devices) I was unable to mount anything
tho' mount /dev/hdh3 /mnt/hd gave me a file doesn't exist (mnt/hd dir
exists) support for the required filesystems is compiled in.
Also, the /dev/d<x>p<y> devices didn't exist, so I probably have to create
them myself perhaps then I can mount. I'll check the files for the
major/minors.
The dmesg in busy box returned more data then the kernel itself spewed
during boot. I've never seen that before? Is it writing extra debuging info
nowadays?
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "freaky" <freaky@bananateam.nl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Saturday, October 26, 2002 4:06 PM
Subject: Re: KT333, IO-APIC, Promise Fasttrak, Initrd
> On Sat, 2002-10-26 at 07:53, freaky wrote:
> > So that would be data on the MBR, or partition table? Perhaps win
doesn't
> > have probs because it can handle to partitions types properly. MSI told
me
>
> No its seperate. The hpt/promise raid "borrows" part of the disk and
> hides it.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/