kernel panic with ntfs slackware 14
Hi Friends,
I have a small problem. I have a 1TB HDD. This hard drive had windows. Then in Fedora I eliminated all Windows directories. Now that I have Slackware 14 I connect and start the pc. I get a Kernel Panic How I can fix this? |
Welcome to LQ!
Quote:
Quote:
Quote:
Quote:
What are the details of the PC? What is the error that you see? |
Internal DIsk
Windows Directories. Hard Disk Have 3 Partitions NTFS Install from DVD clean install(I Have disconnect HD) iCore 5(x64) 8GB 1 HD 500 GB (Slackware) 1 HD 1 TB (Disconnect) When Load OS read de HD y crash with KP |
If you removed Windows directories, then this will not affect Slackware.
Please clarify the disk arrangement. What do you mean by? Quote:
Did you install the huge kernel or the generic kernel with an initrd? What is causing the kernel to panic? |
1) Was this a full install?
2) Did you install the huge kernel or the generic kernel with an initrd? 3) What is causing the kernel to panic? --------------------------------------------------------------------------------------------------------------------------- 1) Yes full install 2) Huge kernel 3) I think that is ntfs package. |
Are you trying to install Slackware on an NTFS formatted partition?
It would be best to format the partition to a Linux format. The default is ext4. Perhaps this will help. http://docs.slackware.com/slackware:install |
Perhaps he reconnected the ntfs 1 TB drive after installing Slackware and borked up LILO's drive assignment. I would have him/her boot from the DVD, chroot in and rerun LILO if that is the case.
|
I use this hard drive as a backup, nothing more, other distributions read my hard drive
|
1) Did you accidentally install lilo on second hard drive? I'd go with mostlyharmless's suspicion.
2) Did you crate a separate partition for /boot and what file system? Regards. |
Perhaps the OP had Fedora installed on an internal 500GB hard disk, then attempted to install Slackware instead.
If the disk had not been completely reformatted prior to the Slackware install, or LILO was not installed in the MBR, then there may be a problem with a residual GRUB bootloader. |
Can you copy the messages that show up before and at the kernel panic? It'll be easier for people to help you out that way.
|
At the time I had installed Fedora.
I also had debian on the 500GB hard drive And they would they acknowledged the ntfs partition. Just slackware does not recognize the hard drive |
So is it just a single hard drive? How is it partitioned?
|
2 Partitions NTFS 2 Partitions have many files :-(
|
From post#3
Quote:
Quote:
|
I can not since returned kernel panic
|
So your problem is that you cannot successfully boot your Slackware install.
This suggests a problem with your bootloader setup but we would need the output requested in post#11. |
Slackware can't be installed to an NTFS partition.
|
You will need to boot with your installation media.
After logging in as root, don't run setup again but issue following command: Code:
fdisk -l You can also tell how these partitions are used. Consider the partitions that have Linux as System (as shown in fdisk -l) and do this (I assume /dev/sda1 has System Linux, adapt accordingly for the other ones case occuring): Code:
mkdir /P1 If you report the layout you find we will be able to help you. Also if you find the root partition, let's say as /P1 (with /etc in it), please do Code:
cat /P1/etc/fstab To avoid you the hassle of copying all that on a paper you could also mount an USB key. Plug it in, assuming it is recognized as /dev/sdb1 (you can check with cat /proc/partitions), mount it: Code:
mkdir /key Code:
cp /P1/etc/fstab /key/fstab.txt Code:
fdisk -l > /key/fdisk.txt Code:
umount /key |
Quote:
|
You might be able to load the linux kernel from NTFS, but no distro is going to be able to boot from an NTFS filesystem -except for one which loop-mounts an FS image from NTFS.
|
2 Attachment(s)
Quote:
Code:
chmod +x bbsplay.txt |
Yeah, well you got me there -I meant an installed system. Sounds pretty safe to assume the OP is not booting a fat kernel with a huge intrdfs inside...
|
Quote:
However, I agree that the OP is unlikely doing this way. |
Calling Troll on this guy... he did similar in the G+ slackware group... helping just lead to frustration as the answers kept changing and the story got more and more bizarre... sry, not buying this is a real problem.
Just like on G+, he never answers your questions with anything useful, never answers them the same way twice, and never gives you any idea of what is really going on... you could get more information from emacs psychoanalyze scripts. |
All times are GMT -5. The time now is 05:41 AM. |