LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-25-2009, 09:37 AM   #1
ingmember
LQ Newbie
 
Registered: Oct 2009
Posts: 7

Rep: Reputation: 0
Linux does not boot on logical partitions anymore


Hello. I tried to post this thread to non-linux topic in general, but it didn't allow me telling me that I don't have "enough rights" or something like that...

Anyway...

...I had this GRUB bootloader working well for each Operating System and each OS start-up fine:

Ubuntu 9.04, kernel 2.6.28-11-generic
Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
Ubuntu 9.04, memtest86+
Other Windows operating systems
-> Windows 7
-> Windows Vista (recovery mode)
-> Windows XP
Debian GNU/Linux, kernel 2.6.26-2-686
Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)


Each Linux and Windows OSs were installed on separate partitions with Vista first, Seven 2nd, XP 3rd, Ubuntu 4th, Debian 5th.

However I wanted Windows bootloader be in charge, installed EasyBCD, rewrote Windows MBR, installed NeoGrub for Linux, clicked to configure menu.lst of NeoGrub, pasted the details of the GRUB above (see the NeoGrub configuration below), saved, then after reboot I had new Bootloader looking like this:

Windows 7
Windows Vista (recovery mode)
Windows XP
NeoGrub
-> Ubuntu 9.04, kernel 2.6.28-11-generic
-> Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
-> Ubuntu 9.04, memtest86+
-> Debian GNU/Linux, kernel 2.6.26-2-686
-> Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)

However when entering the NeoGrub and choosing any Linux to boot I have the following error message on screen:

For Ubuntu:

Booting 'Ubuntu 9.04, kernel 2.6.28-11-generic'

kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d68a3 ro quiet splash

Error 17: File not found

Press any key to continue...

For Debian:

root (hd0,7)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro quiet

Error 2: Bad file or directory type

Press any key to continue

How to fix this problem so that each Linux start-up?
Please, consider Iím a total newbie for Linux and right now Iím experimenting with all these OSs and I want to have this problem fixed.

I attach below NeoGrub Configuration and original menu.lst for Ubuntu and Debian. Maybe you need these to help me?

# NeoSmart NeoGrub Bootloader Configuration File
#
# This is the NeoGrub configuration file, and should be located at C:\NST\menu.lst
# Please see the EasyBCD Documentation for information on how to create/modify entries:
# http://neosmart.net/wiki/display/EBCD
title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu 9.04, memtest86+
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/memtest86+.bin
quiet

title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro quiet
initrd /boot/initrd.img-2.6.26-2-686

title Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro single
initrd /boot/initrd.img-2.6.26-2-686

Ubuntu menu.lst

# 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 use 'savedefault' 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=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=2ebe46ab-c5d8-4f15-a626-0162138d86a3

## 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## 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

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu 9.04, memtest86+
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
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/sda1
title Windows Vista (loader)
rootnoverify (hd0,0)
savedefault
makeactive
chainloader +1



Debian menu.lst

# 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-legacy-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=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro

## 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=quiet

## 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

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro quiet
initrd /boot/initrd.img-2.6.26-2-686

title Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro single
initrd /boot/initrd.img-2.6.26-2-686

### 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/sda1
title Windows Vista/Longhorn (loader)
root (hd0,0)
savedefault
makeactive
chainloader +1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Ubuntu 9.04, kernel 2.6.28-11-generic (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode) (on /dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro single
initrd /boot/initrd.img-2.6.28-11-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda7.
title Ubuntu 9.04, memtest86+ (on /dev/sda7)
root (hd0,6)
kernel /boot/memtest86+.bin
savedefault
boot

Thank you in advance!
 
Old 10-25-2009, 05:32 PM   #2
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,870

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
I've never used vista or EasyBCD but it looks like you have incorrect entries for both Ubuntu and Debain. There is no way for anyone here to know that unless you post your actual partition information from the "sudo fdisk -l" command run in a terminal. It's unclear to me if the two lists you posted at the beginning of your post are in the partition order or not? If the partition order changes, you need to make changes in your menu.lst accordingly.
 
Old 10-25-2009, 07:01 PM   #3
ingmember
LQ Newbie
 
Registered: Oct 2009
Posts: 7

Original Poster
Rep: Reputation: 0
Thank you for reply yancek
This is what I have:

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3133 25165791 7 HPFS/NTFS
/dev/sda2 3134 30401 219030210 5 Extended
/dev/sda5 3134 6266 25165791 7 HPFS/NTFS
/dev/sda6 6267 8224 15727603+ 7 HPFS/NTFS
/dev/sda7 8225 9791 12586896 83 Linux
/dev/sda8 9792 11358 12586896 83 Linux
/dev/sda9 11359 29357 144576936 7 HPFS/NTFS
/dev/sda10 29358 30401 8385898+ 82 Linux swap / Solaris

or like this

/dev/sda1 ntfs 24.00 GB boot (this is where Vista is installed)
/dev/sda2 extended 208.88 GB
-> /dev/sda5 ntfs 24.00 GB (Windows 7)
-> /dev/sda6 ntfs 15.00 GB (Windows XP)
-> /dev/sda7 ext3 12.00 GB (Ubuntu 9.04)
-> /dev/sda8 ext3 12.00 GB (Debian 5.0.3)
-> /dev/sda9 ntfs 137.88 GB
-> /dev/sda10 linux-swap 8.00 GB

Any ideas?
 
Old 10-25-2009, 08:23 PM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,870

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
Only two possibilities I can think of. Kernel files not there or UUID changed if partitions changed. Use whatever Live CD you have been and mount sda7 (Ubuntu) and then sda8(Debian) and navigate to the /boot directory to see if the kernel files listed in NeoGrub menu.lst are actually there.

Run the command 'blkid' (without quotes) as root user and compare the output of the UUID to the UUID's you have in your NeoGrub menu.lst to see if they are the same.

Your not getting to the Ubuntu or Debian kernels so if the above doesn't produce anything satisfactory, I'd go back to the EasyBCD documentation to see if you missed a step??
 
Old 10-25-2009, 09:29 PM   #5
ingmember
LQ Newbie
 
Registered: Oct 2009
Posts: 7

Original Poster
Rep: Reputation: 0
Well, instead of this:

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 2ebe46ab-c5d8-4f15-a626-0162138d86a3
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=2ebe46ab-c5d8-4f15-a626-0162138d86a3 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

I tried to put this:

# EasyBCD Documentation Home - NeoSmart Technologies Wiki
title Ubuntu 9.04, kernel 2.6.28-11-generic
root (hd0,6)
kernel /boot/vmlinuz-2.6.28-11-generic root=/dev/sda7 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet

and instead of this:

title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=UUID=66f39d0f-25d0-4be6-898b-2801e5dc7f6d ro quiet
initrd /boot/initrd.img-2.6.26-2-686

I put this:

title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/sda8 ro quiet
initrd /boot/initrd.img-2.6.26-2-686

But it still didn't work and gave me same errors in trying to start up Linuxes.

Then I put these commands after booting in Ubuntu Live CD:

sudo -s
ls /dev/disk/by-uuid -l
grub
find /boot/grub/menu.lst

And got this output:

ubuntu@ubuntu:~$ sudo -s
root@ubuntu:~# ls /dev/disk/by-uuid -l
total 0
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 2ebe46ab-c5d8-4f15-a626-0162138d86a3 -> ../../sda7
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 307D42176569349E -> ../../sda5
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 361C527B1FB7621B -> ../../sda9
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 3A9F5A300447C07C -> ../../sda6
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 66f39d0f-25d0-4be6-898b-2801e5dc7f6d -> ../../sda8
lrwxrwxrwx 1 root root 10 2009-10-26 11:51 6EE4675EE4672813 -> ../../sda1
root@ubuntu:~#


grub> find /boot/grub/menu.lst
(hd0,6)
(hd0,7)

grub>

Maybe this data can give you more info to help me?

Thank you.
 
Old 10-26-2009, 12:47 AM   #6
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,870

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
Looks like the UUID numbers are the same so that's not likely the problem. It doesn't matter if you have a menu.lst for Ubuntu or Debian. The NeoGrub has one and if you look at their entries they are pointing to the vmlinuz... files and if they exist in the appropriate place, they should boot. I've never used EasyBCD but it looks to me like there is some problem in the way it was setup. Check the Easy BCD documentation again. Don't know how to change it as it is a windows program. Your system was working correctly when you were using Grub for Linux?
 
Old 10-26-2009, 11:50 PM   #7
ingmember
LQ Newbie
 
Registered: Oct 2009
Posts: 7

Original Poster
Rep: Reputation: 0
Yes, this is the thing. All my five operating systems were working perfectly (I mean they were all loading). Yes, my system was working correctly.

Just before I made changes with EasyBCD I had Debian Linux grub responsible for all my OSs start up. I could load up Debian, Ubuntu, Seven, Vista or XP.

Just after rewriting Window's MBR any of my Linux won't start up anymore, but any Windows OS start up as usual, fine.

I belive I could fix Linux grub easily finding know-how in Google and put everything back in place. But just because I was using mostly Windows I didn't want to start up any Windows OS by clicking through a Linux Grub, so that was the reason I used EasyBCD.

I start thinking now maybe there are alternative boot loader managers I could use since this problem with EasyBCD gives a hard time. What do you think?
 
Old 10-27-2009, 12:24 AM   #8
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,870

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
If it was working with the Debian Grub, I'd go back to that. If you boot windows more than the Linux distro you can set the menu.lst to boot whichever version of windows you want by setting the default number in menu.lst.

Use your Debian CD and log in as root and type:

grub (get grub prompt: grub>)
here you would type:

root (hd0,7)
setup (hd0)
quit

should have Grub set to boot all.

Quote:
Just after rewriting Window's MBR any of my Linux won't start up anymore, but any Windows OS start up as usual, fine
When did you do this? While working with EAsyBCD? if you install windows to mbr then you need to configure windows boot files to boot other OS's which is what EasyBCD is supposed to do? Doesn't look like it was successful in your case but, as I said earlier, I've never used vista or EasyBCD but have read about a number of people who have successfully used it to boot Linux.
 
Old 10-27-2009, 07:11 AM   #9
Larry Webb
LQ Veteran
 
Registered: Jul 2006
Location: Crystal Beach, Texas
Distribution: Suse for mail +
Posts: 5,100
Blog Entries: 7

Rep: Reputation: 229Reputation: 229Reputation: 229
I am no EasyBCD man either, see if EasyBCD counts from 1 instead of 0.

In other words instead of
root (hd0,7)

make it
root (hd1,8)

Larry
 
Old 10-27-2009, 06:05 PM   #10
ingmember
LQ Newbie
 
Registered: Oct 2009
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks Larry, tried that, didn't work.

yancek, I did what you said and reinstalled Debian's grub successfully. All returned to the previous state, now I'm able to start-up any of OS successfully. Thank you for that!

As I'm very new to Linux, I have further questions, like how to I access Debian's menu.lst and what do I edit there, because when I logon Debian I only get a command line interface. But that's fine, I will google it and better close this topic so my questions don't spread ahead. And thank you so much for all attention and help provided. I've learned a lot more about this stuff thanks to you!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
how do I add partitions to drives that have Logical Volume (LVM) partitions? The MJ Linux - Software 5 08-17-2006 07:15 PM
cloning both partitions, dual boot system, master boot record, logical volume manager saranga2000 Linux - Hardware 3 01-10-2005 12:04 PM
CFDISK Logical partitions ZeroCoolJr Slackware 7 02-23-2004 07:20 AM
How to add logical partitions in linux ? copernicus Linux - General 2 10-21-2003 08:05 AM
Win98/Linux - dual boot : windows boot says logical drives exist past z ashpai Linux - Software 3 03-22-2001 10:00 AM


All times are GMT -5. The time now is 11:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration