Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, cool. I gave the wrong pass earlier, it's Jeremy with a capital J.
To access it GT:
You have too many options, here's 2:
Open up a console:
ftp masterc.no-ip.org
It will ask you for username:
lq
and then for Pass:
Jeremy
and then your are in. To list the files:
ls
and then you can copy them or whatever.
Another way:
use gftp and go to: ftp://masterc.no-ip.org and login with the username and pass.
They should be there now if you want to check and then close the account.I named them pmdisk-1.tgz and pmdisk-2.tgz.Everything looked OK from my end
GT,if you get them alright, they'llgunzip as folders-just open the folder and cp each set of files to a floppy. pmdisk-1-boot is the boot disk and pmdisk-2-app is the one you'll be asked for after DOS has loaded.
Man,I sure hope I didnt get you killed with my tardiness
lynch
Ok cool, I will close the account, and move the files to the anonymous ftp folder so you don't have to worry about logging in to get them. If you need me to open it again, it won't be a problem lynch. So GT, to get these:
I was just thinking that the "lun0" part of this reminded me of when I enabled "scsi-emulation" for my cd-writer, there was an option in the kernel for "probe all lun's" or something like that. I mean, that partition table looks NOTHING like the ide stuff that i'm used to (except for the ide part :-)
/dev/ide/host0/bus0/target0/lun0/part4
I was just thinking that maybe you enabled scsi-emulation for your hard drives on accident, or it was there already, and some of the configuration was wrong, or you couldn't do that with your hardware or partition type.
It is the only thing I can think of... maybe something to look in to, maybe not.
Either way, Good Luck
do you know how to check your kernel configuration?
if not: go to /usr/src/linux and type "make menuconfig" check out the scsi section and maybe the ide section and see if everything is looking o.k.... if you need more clarity on that, let us know.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
The
/dev/ide/host0/bus0/target0/lun0/part4
is not from SCSI emulation, it's probably because he's running devfs,
which defaults to showing disks in this format.
/dev/hda4 is a symlink to /dev/ide/host0/bus0/target0/lun0/part4
Not that this helps solve his problem, just clears up that this is almost certainly NOT his problem. . .
GT:
can you post the results of:
cat /proc/filesystems
cat /proc/partitions
cd /usr/src/linux
make menuconfig
go to the filesystems option
go to the Native Language Support option
tell what you have checked there.
don't change anything.
Also, another possible solution is that you may not have support for
Windows Logical Disk Manager (Dynamic Disk) compiled into the kernel,
though I don't know if PM actually uses this type of partition. To compile it
in (it won't hurt), do the following:
cd /usr/src/linux
make menuconfig
go to File System
go to Partition Types
go to Windows Logical Disk Manager support
hit "y"
escape back out
save the configuration
make dep && make bzImage && make modules && make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz.WLDM
edit /etc/lilo.conf
add in
image = /boot/vmlinuz.WLDM
root = /dev/hdaX
label = Linux.WLDM
read-only
(Or however you want it if you care for it to be consistent with the rest of
your setup. hdX is your root partition).
lilo
if there are no errors, reboot. However, I seem to remember that RH has
some funky steps you have to go through to add a kernel to the LILO boot
manager, so you may need to double check the steps after making the
kernel. . .
And i don't think i need to compile Windows Logical Disk Manager becasue this happened while i didn't have linux on it...i did have Red Hat 7.3, i formatted my linux partiton, planning to resize my fat32 partition to give more space for my linux one, and then this all happened....
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
Quote:
> there is no cd /usr/src/linux
>
> And i don't think i need to compile Windows Logical Disk Manager
> becasue this happened while i didn't have linux on it...i did have Red Hat
> 7.3, i formatted my linux partiton, planning to resize my fat32 partition to
> give more space for my linux one, and then this all happened....
Right, but I thought you were in the recover what you can mode. If PM
has somehow munged your partition (for example, by making it fall under
the "Windows Logical Disk Manager" partition type), then you won't be
able to read the partition (correctly) under Linux unless you've got support compiled into the kernel. . .
Anyway, it looks like you don't have the kernel source installed (unless
there is a /usr/src/linux-2.x.xx). Unfortunately, the partition code must be
compiled in; it's not available as a module. If you want to try this route,
it may or may not be a solution. If it isn't, then you could end up spending
more time than it's worth on recompiling the kernel.
By the way, your partitions look fine, and you have VFAT support in your
kernel, which is good. I'm just guessing that perhaps PM has added
some bits to the partition table that causes your "fat32" partition to
appear to be some other beast.
Another "by the way", what is the command you issue to mount your
windows partition?
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
Right. I just changed the type of one of my partitions to P.M. Rec. and
rebooted. It didn't make a difference, I could still mount the partition
(as VFAT).
Let's try one more thing in Linux before I start to wonder. . .
Try changing the partition type from FAT32 (ID b) to FAT32 LBA (ID c).
write this partition table, reboot, make sure your BIOS is detecting the
drive as an LBA disk, and let me know what you get. . .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.