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.
This one has me stumped. The Slack install on my laptop seemed to go well, I declined to install LILO as I plan on editing my existing Grub Menu.lst. But, I am getting the error:
Code:
Error 2: Bad File or Directory
Now, I am familiar with this message, but it doesn't make sense. vmlinuz-huge-smp-2.6.24.5-smp is located in the boot directory. There is no initrd. My fdisk -l
Code:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3824 30716248+ 83 Linux
/dev/sda2 3825 6374 20482875 83 Linux
/dev/sda3 6375 6629 2048287+ 82 Linux swap / Solaris
/dev/sda4 6630 19457 103040910 5 Extended
/dev/sda5 6630 13156 52428096 83 Linux
My menu.lst entry:
Code:
title Slackware 12.1
root (hd0,4)
kernel /boot/vmlinuz-huge-smp-2.6.24.5-smp root=/dev/sda5 ro
I have Slack installed on /dev/sda5. There is a symbolic link called vmlinuz in the directory as well, but, as you can see I have directed grub to the kernel intself.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
How did you format your Slackware partition? Ext3? There might be a problem with that, only newer grub installs are able to read the 256 byte inodes from the newer ext3 (upwards compatible with ext4, but not with older grub builds as I said).
I suggest you install the grub package from /extra and reinstall it to your hard disk - you can of course reuse your menu.lst. The Slackware 12.1 version doesn't have this limitation you are experiencing.
Last edited by titopoquito; 05-19-2008 at 05:08 PM.
Yes it is ext3, but I am not sure I understand. ALL of the partitions are ext3, including the Ubuntu Hardy I have installed on sda1. The grub installed is the one from the Ubuntu installation and that is the menu.lst I boot from. Never had a problem with ext3 before.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
Well, from what I understand the change is quite new. If you search a bit for it ("grub 256 bytes problem" should do) you will find your excact error message.
It's a recent change to ext3 to make shifting to ext4 easier.
PS: You do not have to reformat anything, only install grub again from within Slackware 12.1. Your Ubuntu install should work like it did before after this.
Last edited by titopoquito; 05-19-2008 at 05:24 PM.
Yes, thank you, I did read that from another post. But this Grub install is less than a month old from a just released distro, it is the newest version of grub. I doubt that this grub installation could be considered old. I guess it could be that I just have corrupt installation. Everything went to plan, so I thought. Didn't see anything unusual in the installation process.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
I don't know if Ubuntu patches grub to include the 256 byte inode stuff, but I would normally think so. Dunno why it fails, maybe your Ubuntu is just wayyyyy to old
Well, thank you anyway for your attempt to help. This is the fourth time I have tried to install Slack this year and have never been successful. The first time was on my desktop and got a "Disk 32" error and it would not install. Tried 12.0 on another laptop and it would not load the install disk. This install looked good and I thought I would be booting into Slack this tiime.
I had planned on having a second "stable" distro on this laptop because Hardy just does not perform well and I still get the occassional lock-up/freeze. It's also really odd that after I installed Slack (not having touch the other partitions), Ubuntu now boots without the splash screen, and stutters when it shuts down. It somehow got corrupted during the slack install. Don't know. Looks like me and Slack just weren't made for each other.
After studying the docs a little more, the README.initrd file indicates that an initrd may be necessary with the ext3 file system. Is it necessary to have an initrd? If so, is it possible to chroot into slack from another OS on the same disk to run the mkinitrd command as suggested in the docs? Or is it just easier to re-install and change the file system to ext2?
syg00, I did not install grub during the Slack install, I just edited an existing menu.lst from sda1 where Ubuntu is installed. From the entry I have for Slack above, which root directive should I remove?
root (hd0,4) ?
root=/dev/sda5 ?
I tried this line:
kernel (hd0,4) /boot/vmlinuz root=/dev/sda5
same error.
Thanks for your help, and if you would not mind, post back a sample of what you mean by the root directive.
BobNutfield,
Just to let you know, I boot Slackware from Ubuntu's grub and it works fine on Slack 12 and Slack 12.1. My Slackware install is ext3 also. So Ubuntu's grub is not the problem. I think syg00 found the problem. Uso no white space in the kernel line except before root=/dev/sda5.
Thanks for all your replies. I tried all of the suggestions and still get the same error 2 from grub. This has me stymied because I use the same grub entries to boot five different distros from one grub menu.lst on my desktop, and three years ago I used to boot Slack with the same type of entry (still had a copy of the old menu.lst).
brianL: Thank you for the suggestion, but this laptop is a dual core AMDX2 T57. The Slack docs say to use the huge.smp kernel to get the support for this processor. None-the-less, I chrooted into Slack from Ubuntu and attempted to run the mkinitrd command (from the instructions in the docs), but got a permission denied error and a /proc/partitions No such file or directory.
I can only conclude that the files in boot directory are corrupt. I cannot see anything wrong, but then these are binaries that you can't really look at.
tommcd: If you would not mind, could you post your entry from Ubuntu's menu.lst to boot Slack? I just want to verify that I am getting right.
I am going to try to re-install one more time. If it doesn't work, I guess I can scratch Slackware from my list of possibles.
tommcd: If you would not mind, could you post your entry from Ubuntu's menu.lst to boot Slack? I just want to verify that I am getting right.
Bob
I'm at work now, on a Windows machine. When I get home I'll post the Slackware entry from my menu.lst in Ubuntu. Expect it in about 4 hours (or maybe a bit less) from the time of this post.
I'm not sure about this, but I think you need these 2 lines in the menu.lst file
Code:
savedefault
boot
This goes after the kernel and initrd line, but you don't need a initrd for the huge-smp kernel. Also, see post #4 from this thread about using grub interactively to automafically boot any distro. It always works for me. http://ubuntuforums.org/showthread.php?t=393379
Your menu.lst entry looks ok to me though:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.