OK, I have a problem with my Debian installation. Here's what happened...
I had on this computer Debian and Ubuntu 64. Ubuntu I hardly used, and Debian was running out of space. So I decided to take the /swap of Ubuntu (1GB) to the Debian installation and dedicate all to Debian. I used GParted Live CD to perform the tasks. As many of you see coming, this ended up in a terribble error: Grub error 17. Being convinced only Grub had a problem, I decided to download Ubuntu 32bit 7 and have this install the grub to restore the system. It indeed, as live CD, recognized the Debian partition and all files were there.
I then thought why not use the same swap partition for both installations. So after Ubuntu was ready installing I tried to reboot into Debian. This did start up, but gets stuck why booting up. It gets stuck at the following messages:
Mounting: /dev/sda8 on /root failed: no such device (sda8 is the swap)
Begin: running /scripts/local-bottom
Done
Done
Begin: running /scripts/init-bottom
Mount: Mounting /root/dev on /dev/.static/dev failed: no such file or directory
Done
Mount: mounting /sys on /root/sys failed
Mount: mounting /proc on /root/proc failed
Target filesystem doesn't have /sbin/init
Busybox v1.3.3 (Debian 1:1.1.3-4) built-in shell (ash)
enter "help" for a list of built-in commands
/bin/sh: can't access tty; job control turned off
(initramfs)
So now I am stuck. I can access the files from Ubuntu, but I'd like to have my Debian back. Can anybody help me to get my Debian starting again? Where can I start looking for a solution?
Thanks in advance,
Cheers,
Bart
folkert
06-09-2007, 05:23 AM
Mounting: /dev/sda8 on /root failed: no such device (sda8 is the swap)
It sounds like the partition number of your debian installation changed from sda8 to someting else, did you edit de /etc/fstab file acordingly?
Alpine CH
06-11-2007, 04:24 PM
Hi Folkert,
This I tried, but it keeps changing it back when I start Debian up.
Any other idea's?
Thanks en Bedankt,
Cheers,
Bart
IsaacKuo
06-11-2007, 04:36 PM
Is that EXACTLY what the error message was? I find it strange for there to be something saying "(sda8 is the swap)".
Depending on the exact error message, your true problem might be swsusp attempting to mount a (currently nonexistent) swap partition. If it fails, then you're left in an unbootable state--not even single user mode will work. I haven't had a chance to explore whether a GRUB "noresume" boot option will fix it.
It sounds like you aren't familiar with installing or using GRUB. Is that right?
Oh--please post what the contents of /etc/fstab are, and what partitions currently exist on the drive.
Alpine CH
06-12-2007, 01:07 AM
Hi IsaacKuo,
Indeed I am not having much experience with GRUB at all. I am just using linux for daily business, not really the expert here.
This is exactly the message with the exception of (sda8 is the swap):o . This I put in to clarify it a bit (which seems to cause more confusion then help - sorry for that:( ). At this point it stops, or rather, it is in the busybox shell. And I have no clue how to get furhter.
I'll try the noresume option when I have a chance. Then I'll post the fstab, don't have the computer with me right now. I'll try to post it tonight or tomorrow morning (GMT+2).
Thanks for the help,
Cheers,
Bart
IsaacKuo
06-12-2007, 09:03 AM
I'm not sure what's going on, but in any case there's a really helpful sticky in the "How I Did it" forum which gives great tips on repairing GRUB. I used it because GRUB documentation is generally so confusing and not helpful.
Alpine CH
06-12-2007, 01:21 PM
Hi Isaac,
Here is the requested fstab. I aslo attached the setup of the partitions.
Next to the Dell restore partitions and XP partition, there is a share (5GB) and Ubuntu 32bit and of course the Debian 64.
Any suggestions how to continu or how to use busybox to repair the system?
Cheers,
Bart
IsaacKuo
06-12-2007, 02:14 PM
Okay, I had a misunderstanding that your screenshots have started to clear up. I was under the impression that there was only one Linux OS on this hard drive.
It's not clear to me which /etc/fstab is posted in your screenshot. I'm going to assume for the moment that you know what you're doing and posted the one on sda7.
So, if I understand correctly, sda5 is an Ubuntu install and GRUB is pointed at sda5. Sda7 is the Debian install. Is that correct?
Please post the contents of /boot/grub/menu.lst from both sda5 and sda7. (Oh, don't use screenshots--insert text with the tag).
A proper entry for Debian will look something like this:
Notice that the root is specified in two places. Make sure both are pointed to sda7; I'm not positive what the way to specify sda7 is for GRUB partition numbering. It might be (sd0,6).
trilarian
06-12-2007, 02:56 PM
Hi Isaac,
Here is the requested fstab. I aslo attached the setup of the partitions.
Next to the Dell restore partitions and XP partition, there is a share (5GB) and Ubuntu 32bit and of course the Debian 64.
Any suggestions how to continu or how to use busybox to repair the system?
Cheers,
Bart
This may or may not be the problem, but something easily overlooked - are you sure you are looking at the correct FSTAB? What I mean is, you will have to mount your Debian partition then look at the /etc/fstab from that mount point. Seeing /media/disk suggest you are doing this, but wanted to double check.
Also, can you post your /boot/grub/menu.lst please? Depending on if you have /boot as a partition or under / of the distro install, you may need to use your mount point to the Debian install in your path.
What I'm guessing is that sda8 used to be used differently, and once you merged two partitions the old numbers in your grub menu became invalid.
EDIT ==>> Haha, IsaacKuo posted while I was typing, so some of my response overlays his~
Alpine CH
06-13-2007, 03:17 AM
Hi guys,
First of all, thanks for taking the time to help me out.
Really appreciate it. :)
It's not clear to me which /etc/fstab is posted in your screenshot. I'm going to assume for the moment that you know what you're doing and posted the one on sda7.
This may or may not be the problem, but something easily overlooked - are you sure you are looking at the correct FSTAB? What I mean is, you will have to mount your Debian partition then look at the /etc/fstab from that mount point. Seeing /media/disk suggest you are doing this, but wanted to double check.
Yes, I am convinced I have the right fstab. This is the fsab of the debian partition, I double-checked it before posting.
Here are the GRUB menu lists of both partitions. No more screenshots ;)
Debian Partition (sda7):
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/sda8 ro pci=nomsi
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,7)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(single-user mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
title Debian GNU/Linux, kernel 2.6.18-3-amd64 (single-user mode)
root (hd0,7)
kernel /boot/vmlinuz-2.6.18-3-amd64 root=/dev/sda8 ro pci=nomsi single
initrd /boot/initrd.img-2.6.18-3-amd64
savedefault
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
title Ubuntu, kernel 2.6.17-11-generic (on /dev/sda5)
root (hd0,4)
kernel /boot/vmlinuz-2.6.17-11-generic root=/dev/sda5 ro quiet splash pci=nomsi
initrd /boot/initrd.img-2.6.17-11-generic
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
title Ubuntu, kernel 2.6.17-11-generic (recovery mode) (on /dev/sda5)
root (hd0,4)
kernel /boot/vmlinuz-2.6.17-11-generic root=/dev/sda5 ro single
initrd /boot/initrd.img-2.6.17-11-generic
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
# title Ubuntu, kernel 2.6.17-10-generic (on /dev/sda5)
# root (hd0,4)
# kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro quiet splash pci=nomsi
# initrd /boot/initrd.img-2.6.17-10-generic
# savedefault
# boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
# title Ubuntu, kernel 2.6.17-10-generic (recovery mode) (on /dev/sda5)
# root (hd0,4)
# kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda5 ro single
# initrd /boot/initrd.img-2.6.17-10-generic
# savedefault
# boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
title Ubuntu, memtest86+ (on /dev/sda5)
root (hd0,4)
kernel /boot/memtest86+.bin
savedefault
boot
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Windows XP Media Center Edition
root (hd0,1)
savedefault
makeactive
chainloader +1
and here is the Ubuntu GRUB list (sda5):
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=6889f464-46fb-4ffd-9dac-a8e176222090 ro
## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=6889f464-46fb-4ffd-9dac-a8e176222090 ro single
initrd /boot/initrd.img-2.6.20-15-generic
title Ubuntu, memtest86+
root (hd0,4)
kernel /boot/memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Windows XP Media Center Edition
root (hd0,1)
savedefault
makeactive
chainloader +1
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Debian GNU/Linux, kernel 2.6.18-4-amd64 (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.18-4-amd64 root=/dev/sda8 ro pci=nomsi
initrd /boot/initrd.img-2.6.18-4-amd64
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Debian GNU/Linux, kernel 2.6.18-4-amd64 (single-user mode) (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.18-4-amd64 root=/dev/sda8 ro pci=nomsi single
initrd /boot/initrd.img-2.6.18-4-amd64
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Debian GNU/Linux, kernel 2.6.18-3-amd64 (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.18-3-amd64 root=/dev/sda8 ro pci=nomsi
initrd /boot/initrd.img-2.6.18-3-amd64
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Debian GNU/Linux, kernel 2.6.18-3-amd64 (single-user mode) (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.18-3-amd64 root=/dev/sda8 ro pci=nomsi single
initrd /boot/initrd.img-2.6.18-3-amd64
savedefault
boot
Thanks,
Cheers,
Bart
IsaacKuo
06-13-2007, 08:28 AM
Based on the menu.lst entries, it seems that GRUB is currently loading from the Ubuntu partition, and the Debian entries are "partly" messed up. The "root (hd0,6)" lines do point correctly to sda7, but the kernel lines refer to /dev/sda8 rather than /dev/sda7. That would explain how it gets as far as busybox--it's running from the initial ramdisk image (initrd.img-2.6.18-3-amd64). However, when it gets around to trying to mount the "main" root file system, it fails.
The entries for menu.lst on the Debian partition are all the way wrong; they refer to sda8 on both lines. Assuming you keep GRUB pointed to the Ubuntu partition, then this doesn't really matter.
Alpine CH
06-13-2007, 09:31 AM
Hi Isaac
That was what I have been missing all the time. It had shifted the partitions, but it has never crossed my mind to look at the GRUB menu list to see whether it had shifted as well. Changing it to sda7 was exactly just the thing that brought it to boot. Learned something once more today.
Thanks for your patience and help.:D
Cheers,
Bart
trilarian
06-13-2007, 10:34 AM
Funny how one number in one config file being off by one digit can bring a system screeching to a halt, huh? Anyway, glad you are up and running again.
Alpine CH
06-14-2007, 02:25 AM
Yeah, just one number one easily oversees and then the problems start....
At least I have my beloved Debian back, that was worth the whole effort!!!
Thank you all for helping,
Cheers,
Bart
setinkhan
11-05-2007, 01:38 PM
Hi all, I put a used HD in a computer which had a HD failure. It was running Win 98, and was replaced by a newer and faster model. I want to install a linux OS on here. I got "FreeSpire" and tried it at home booting from the CD and it worked great. I came in to work this moring and tried to install it and I was told there were no active partitions. I used a boot disk and fdisk, formatted the drive and then tried again. I know the HD is good. This time it started to boot but then came to
Busy Box V1.13 (Debian 1:1.1.3-ubuntu3+0) Built-in shell (ash)
Enter 'help' for a list of built-in commands
/bin/sh:can't access tty; job control turned off
(initramfs)
I have read all the responeses and are pretty much lost. I have no idea what Grub is or how to start using it. If you can point me in the right direction I can start getting this to work. Any other help you can give me would also be greatly appreicated.
Thanks
setinkhan
11-05-2007, 01:54 PM
I'm trying to install FreeSpire on a old win98 computer. I tried the install and I was told there were no active partitions. I ran fdisk and formatted the C. Then I tried again and it started to boot but hung at
BusyBox V1.1.3 (Debian 1:1.1.3-3ubuntu3+0 Built-in shell (ash)
Enter 'help' for a list of built-in commands
/bin/sh:can't access tty; job control turned off
(initramfs)
Now I have read all the post here and I have no idea what GRUB is. This is kind of my first experience with Linux (installing it), and I would really want to use this.
Any help you can give me or if you can point me in the right direction I'd be very grateful.
Thanks, Steve
Alpine CH
11-06-2007, 11:21 AM
Hi there and Welcome,
First, before some one else tells you off, you are not supposed to post your problem in someone else's topic. Better to start your own thread, this would give you way more feedback. Now people will ignore it. Guidelines you'd find everywhere on this site, especially on the signatures of the moderators (bwkaz, jefro, saikee etc).
As to your question. I have not really the experience on how to solve it, but it sounds like you have a problem in the basic system. Grub, the boot loader that starts up the OSs on your computer seems not able to find the correct bootable system. In my case, it pointed to the wrong partition, in your case I have no idea.
Have a look on the booting tips of saikee. He is a true specialist, being able to boot more OS I will ever have in my whole life. on a single computer using Grub. Start from there and work your way further.
Good luck,
Cheers,
Bart
saikee
11-06-2007, 11:50 AM
setinkhan,
Can I ask you to start a new thread?
Your information is confusing to others searching this thread for Debian and 64 bit.
Your problem is relating to Freespire and so you should have a title like
"Help needed to install Freespire"
You should tell other the destils of the PC that you managed to run it successfully at home and the one that did not in the office.
You also need to tell us if you can run Freespire as a Live CD and if the office machine has been protected against installation of OS without the knowledge of the IT department.
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.