From: "freaky" <freaky@bananateam.nl>
To: <linux-kernel@vger.kernel.org>
Subject: Re: KT333, IO-APIC, Promise Fasttrak, Initrd
Date: Sat, 26 Oct 2002 16:19:00 +0200 [thread overview]
Message-ID: <006a01c27cfa$a167ae30$1400a8c0@Freaky> (raw)
In-Reply-To: 1035641191.13244.108.camel@irongate.swansea.linux.org.uk
There's no data loss that I know off... Shouldn't I atleast have notices
something if data was overwritten? Shouldn't the partition tables be corrupt
then? (Both disk manager and linux fdisk see them correctly). Don't get me
wrong :-) I'm not saying you're wrong, I wouldn't dare :-), I just find it
strange I haven't noticed anything and I've been running this setup for
several weeks now. Is there anyway I could see this block so I can see it
actually did create it? Perhaps it's written on space unlikely to be used?
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/
>
>
prev parent reply other threads:[~2002-10-26 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 19:32 KT333, IO-APIC, Promise Fasttrak, Initrd freaky
2002-10-25 21:11 ` Alan Cox
2002-10-25 21:10 ` freaky
2002-10-25 21:51 ` Alan Cox
2002-10-26 6:53 ` freaky
2002-10-26 14:06 ` Alan Cox
2002-10-26 14:19 ` freaky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006a01c27cfa$a167ae30$1400a8c0@Freaky' \
--to=freaky@bananateam.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox