Grub error: unknown filesystem after installation
I have an old computer.
(CPU: P II 233 MHz, RAM: 512 MB, DDR2, HDD: 40 GB) I was installed Debian 6.0 sqeeze without graphical interface successfully. This is the ONLY operating system on the computer. After reboot I have this message: Quote:
Quote:
I was found lots of issues, but nothing have worked. I was tried to boot Debian netinst CD in Rescue mode, and changed the /boot/grub/grub.cfg, but nothing has changed! I tried to test, which line is the bugous line in the config file by this simply method: I was added this line before the first line in the config: Quote:
After that I tried to run an fsck with -f (force) option, but no errors found. Tried to detect badblock: # badblocks /dev/sda ...no problems found. OK, reinstall the GRUB... Quote:
OK, try to reinstall Debian... (Might be something wrong in the installation???) The installation successfully, and try to boot the system. The problem doesn't fixed yet. Here is my partitioning: drive part.size mount point filesystem /dev/sda1 8GB / ext.3 /dev/sda2 20 GB /home ext.3 /dev/sda3 10 GB /www ext.3 (apache document root) /dev/sda4 2 GB SWAP SWAP The grub.cfg: Quote:
|
Go get bootinfoscript and post the RESULTS.txt. That way we can see what is where as far as grub is concerned.
|
The bootinfoscript result
This is the bootinfoscript result:
Quote:
|
Looks sane to me - sorry, nothing obviously wrong jumps out at me.
|
Yes it looks pretty good.
However I do not like the fact that there is such a thing as /etc/lilo.conf on your system. This could be a problem. Running, as root; Code:
apt-get purge lilo Code:
update-grub Code:
grub-install /dev/sda I would use a live CD and chroot in to run them. |
I was removed the lilo, and all of the lilo's config files, and reinstalled the grub without any errors, but the problem is still exists.
Is there any other way to start my Debian on my PC? |
Better run the boot info script again so we can see if anything else has changed.
My theory is that this is due to an installer foul up. Only one bootloader should have been installed. This also means that there may be a fault in grub as installed on your system currently. The Boot info script may give us a clue. The results you posted before showed no problem, just the additional lilo files. When Ubuntu was introducing Grub2 they tried to let both grub versions co-exist on systems. This worked for most folks. For the ones that it didn't, however, it was a total wreck. Removing just about every trace of both systems and reinstalling grub2 was the cure. I think you may need to do that. Before doing so we really should look at the information again and see if there is an alternative. |
I think it is a herdweric problem, and tried something...
I found a very old harddisk at my home. (341 MB :D) The device is very old, but it works yet. I was put it to my computer as a master drive, and I was make a new installation with it. The newly insterted disk mounted to /boot. NOW: The grub can recognize the filesystem on the sda1 (The newly inserted disk), and the error message has changed. Quote:
This is the result of the bootinfoscript now: Quote:
"sdb1: Location of files loaded by Grub: ..." The grub tries to load files from the root filesystem, but the Grub can't recognize the filesystem on sdb1 (hd1,msdos1)!!! But why can't recognize the fs on sdb1?! We can see that the filesystem is ext4 on the all disc, except the sdb4, where the fs is swap solaris. The rescue disc, and oter live linuxes are recognize the fs without errors. Let's try something... This is the output of command 'fdisk -l': Quote:
This might be problem. The solution can be resize of the sdb1 partition. ...but how can I calculate that where is the cylinder boundary? |
I was started the GParted on the Ubuntu Live CD, and created a new partition table with it.
After that I was make a new Debian installation. The problem seems solved. All partitions are recognizable for Grub, but there is the next problem: When the GRUB starting up: Quote:
Quote:
|
I think your approach is really interesting. That is a very small HDD, surprised the install fits.
I am a little concerned about that as you should have the grub.cfg file for sdb1 also in the results from the boot info script. Here are "symbolic" menu entries for your installs. Code:
echo "Adding Debian on sda1" >&2 Code:
update-grub If it doesn't work try it with the install on sdb1 and install that grub on the sda MBR (grub-install /dev/sda). If you have had Ubuntu installed on this computer before I don't see that this can be a hardware problem but one never knows for sure. I still think this is some installer error. That is an old computer though so it could be just too old for this. You have booted the install disk and Ubuntu LiveCD on it, though, so I think it should run. There is the package "grub-legacy" in the Debian Squeeze repo. This is the old Grub version. You could try it also. To do that you need to completely purge your current grub, as root; Code:
apt-get purge grub-pc grub-common Code:
apt-get install grub-legacy grub-common If this is a hardware based problem it has to be related to grub-pc, I think. Grub-legacy may do the trick. If not you could purge grub completely and make sure all directories and files are gone (/boot/grub, /etc/default/grub and /etc/grub.d) and install lilo which is even older and surely should be compatible with your hardware. I don't know a thing about using lilo but I am sure there is documentation. |
Quote:
I have the same problem, my freshly installed Precise Pangoline on USB drive refuses to boot. Grub2 simply says "unknown filesystem" on the linux partition in the drive, even if it's mountable without errors (I'm running a fsck just now to be sure, but I suspect it won't solve the problem). Code:
Disk /dev/sdb: 500.1 GB, 500107862016 bytes Code:
sync ; echo 3 > /proc/sys/vm/drop_caches ; qemu-system-i386 -hda /dev/sdb Regards Avio |
This may be or may not be a grub-pc problem.
I think it is an install problem with the Ubuntu installer. This could be wrong but there is supposed to be a major overhaul of ubiquity during the 12.10 dev cycle. I do not have a usb stick. I know, I am a grumpy geezer and should get one. I do have a usb drive. Dual Sata external enclosure. Have no trouble booting from it under Xubuntu 12.04 (will be off of here Friday) or any of the Debian installs on there or the 2 Xenix installs on there. What happens if you turn off your other drives when you try to boot from the usb device? Is grub for the usb device installed on your primary drive? That would be your internal sda drive. This is a grub-pc problem. If you can boot to the thing with the othe drives turned off (I can do that in my bios) try installing the grub from your usb device on the sda internal. If you use the box with out the usb stick you can put what ever other grub you normally use back on there in chroot before leaving the usb installed OS. If you use MS on the internal you will have to use testdisk, the MS install disk or some other tool. Don't know for sure what they would be. Don't think anyone needs to boot to MS anyway. The song and dance about the overlapping partition table is not the problem. If you use gparted to partition your drive with several installes cfdisk will not open because of that very problem. Grub does not care as long as it is pointed to the correct partition. |
Thank you widget for your help!
Your answer (#10) is works! |
That is good to hear.
|
Sorry for the late reply, I tried some of your suggestions.
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
As a side-note, I also had problems with the graphical part of grub2. On my main machine, a gentoo installation on top of a recent PC, grub2 isn't able to go into graphical mode. I tryed almost everything to fix it, to no avail. This makes me think that grub2 has still some bug to correct before it can be considered as reliable as grub-legacy. Regards Avio |
All times are GMT -5. The time now is 01:58 AM. |