SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So I got Slack to the point were it sees my sda drive(where I have windows). YAY! But I have a problem mounting it, this is the error
Quote:
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Please check that the disk is entered correctly.
and then in the window it has another error saying
Quote:
An error occurred while loading devices:/devsdadevsda:
Retrieving data from devices is not supported.
Then my other problem is with Lilo, I get it to prompt it to boot Linux, Slackware(the new kernel, i will get to that in a second), and Windows, but when I choose windows it flickers, then just goes back to the menu. the code I have in lilo is this
Quote:
# Windows bootable partition config begins
image = /dev/sda
root = /dev/sda
label = Windows
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Windows bootable partition config ends
I'm not sure if it's the coding or if it's Lilo...
Finally, my new kernel I compiled(I was fallowing shilo.is-a-geek guild) does't work, it gets to this point were it says "panic" and it stops trying to boot. Now I don't know what information you need for this, so just ask and I will do my best to previde it.
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Please check that the disk is entered correctly.
Im guessing your windows partition is sitting on /dev/sda1
try: mount -t ntfs /dev/sda1 /mnt/hd <---if its a ntfs partition, or..
mount -t vfat /dev/sda1 /mnt/hd
BUT I would double check to see where your windows partition is sitting on with: fdisk -l
Quote:
# Windows bootable partition config begins
image = /dev/sda
root = /dev/sda
label = Windows
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Windows bootable partition config ends
This should read as the following, but as I said earlier double check with: fdisk -l
# Windows bootable partition config begins image = /boot/thenameofyourvmlinuz root = /dev/sda1
label = Windows
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Windows bootable partition config ends
look in /boot dir to check what your vmlinuz is named
I'm still using the 2.4.29 kernel because I haven't figured out what I did wrong compliling 2.6.14
This is the part that you want of the fdsik -l you want
Quote:
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9728 78140128+ 7 HPFS/NTFS
Ok, so I did what p0f said and it's mounted, I changed my fstab to match it, so now it says
Quote:
/dev/sda1 /mnt/hd ntfs noauto,users,ro 1 1
Now I don't understand what you mean by the vmlinuz thing, how would that boot into windows?
# Windows bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Windows
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Windows bootable partition config ends
Unless I misunderstood you, that didn't work.
Quote:
# Windows bootable partition config begins
other = /dev/sda1
table = /dev/sda
label = Windows
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Windows bootable partition config ends
And that gets an error on line 48 or above...whick is the last line.
Thanks for the help so far, I can atleast mount my other HD.
Now I don't understand what you mean by the vmlinuz thing, how would that boot into windows?
u misunderstood me, it was not me(rkrishna)"also i pointed tht error in my first post as a question"
Quote:
I haven't figured out what I did wrong compliling 2.6.14
try a new compiling, start from fresh, free ur mind
use 2.4!! fix problems there then compile 2.6, i dont like people suggesting to use 2.6 for silly problems like scsi emulation...
i am not giving a windows recovery lecture, sorry (and without warranty -ur risk)
i hope u have erased the windows boot from the boot sector("i dodnt suggest u to fix by booting with xp cd--> enter into recovery mode-> then fixmbr"-this is the option)before doing tht u have one more option, boot with bootdisk of windows 98 "fdisk /mbr(check this command)" and try booting if u can boot into windows then it is a lilo problem.
otherwise try the "fixmbr" command as i mentioned and boot with slack installation disk to ur machine(hope u know the command it is there in the fist screen of installation)run lilo
I have put nothing on the windows hard drive. Lilo, Slack, the MBR everything linux related is on the linux hard drive, i made sure of that.
There is nothing wrong with Windows at the moment.
Now I still don't understand what you mean with the /boot/[insert something here] thingy...
There is nothing wrong with Windows at the moment.
but i thought u were mentioned about-"cant boot windows from lilo" that means u cann't access win now right??if u can access forget about previous post
Quote:
Now I still don't understand what you mean with the /boot/[insert something here] thingy...
still it is not me
Code:
# Windows bootable partition config begins
image = /boot/thenameofyourvmlinuz
if this is the one u mentioned then i wil make it clear for u
actually this line is for linux ,(that was an error) and we usually put the name of bzimage, according to our convenience,(like vmlinuz-2.6.15.4)
Ok, first, Windows is fine, I just go into my BIOS and change the set up so it boots into my SATA drive instead of hd0...
Next, I put "/boot/vmlinuz" because that is the vmlinuz in my /boot/ directory...and it didn't work... Now I know you know what your doing, I don't lol, and incase you haven't noticed I'm still under n00b status. thanks for being patient though.
ioo...i am really confused, sorry..some questions
1.can u can go to windows from the lilo screen now?
2.so u installed lilo to the mbr of disk having windows right?
3.u have 2 hard disk?
windows in /dev/sda adn linux in /dev/hda???
linux part of lilo wil have this form
give correct partition,
4."do u have a seperate boot partition"??-->this is important
Code:
image = /boot/vmlinuz
root = /dev/hda7 -->if u have seperate boot partition give tht partition id here
label = Linux
read-only
5.WHILE RUNNING LILO, ARE U GETTING ERROR MESSAGES??
ioo...i am really confused, sorry..some questions
1.can u can go to windows from the lilo screen now?
2.so u installed lilo to the mbr of disk having windows right?
3.u have 2 hard disk?
windows in /dev/sda adn linux in /dev/hda???
linux part of lilo wil have this form
give correct partition,
4."do u have a seperate boot partition"??-->this is important
Code:
image = /boot/vmlinuz
root = /dev/hda7 -->if u have seperate boot partition give tht partition id here
label = Linux
read-only
5.WHILE RUNNING LILO, ARE U GETTING ERROR MESSAGES??
Ok, here we go...
1.I can not get into windows from Lilo
2.No, I installed the mbr to the disk that has linux
3.correct, sda is windows, and hda1 is linux
4.I have a couple partitions, I have the main one with Linux, a Swap, and one that doesn't work to well lol.
5.If I put Lilo in Console, it says
Added Linux *
Added Windows
And thats it...
u can do it, by your self.
dont change the "boot flag". lilo is on mbr/(root partition of linux) make tht one bootable from "fdisk "(then only u wil c the lilo screen).
i think some pro with the partition info.(many questions arising in my mind) think about it and do it by urself
but boootable flab to the lilo partition, then try resolving it
best of luck
play around, change the boot flag (from fdisk )to your partition where lilo is installed. so that you dont get a windows boot loader screen.
edit lilo (run lilo) {take the kernel from the installation disk put it in your /boot, edit lilo, reboot}
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.