Problem dual booting with Windows

r3cursive · 03-25-2009, 12:17 PM

hi all

i got problem with this
i installed slackware 12.2 first, resize my /home partition with gparted, then installed windows i dont know windows will replace MBR, after restart lilo not work properly, so i use System Rescue CD to boot into my slackware then run liloconfig and replace it again

after that, i boot normally, but when i login with ordinary user this message appear

Code:

No directory, logging in with HOME=/

i think itś because the resize partition, am i right?

camorri · 03-25-2009, 12:26 PM

Quote:

i think itś because the resize partition, am i right?

Since you have added windoze, you would have added a partition for windoze. This has changed the partition numbering.

If you can boot to a command prompt, with slack, or a live CD, run the 'df' command, and look at the numbering in lilo.conf. I suspect you will see the problem then.

If not, then post the information, along with lilo.conf.

r3cursive · 03-25-2009, 10:35 PM

thanks for your respone camorri

iam not to understand how to read it, i hope this information will help

Code:

bash-3.1# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             28834744   7647040  19722980  28% /
tmpfs                   514596         0    514596   0% /dev/shm

Code:

bash-3.1# vi /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends

and here is for use fdisk

Code:

bash-3.1# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x85d685d6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         249     2000061   82  Linux swap
/dev/sda2             250        3896    29294527+  83  Linux
/dev/sda4            7721       19457    94277452+  83  Linux

camorri · 03-26-2009, 10:06 AM

Your lilo file looks O.K. Your root file system is on sda2.

There are some things that are confusing. You said in your first post you installed windoze. There are no partitions showing up for windoze. That is strange. Even if you replace the MBR after the install, the partiton(s) should still be there.

The partition numbering is also a little strange. sda1 is swap, this is a primary partition. It would appear sda2 is your / partition, and is also primary. There is no sda3, but there is a sda4??? If sda4 is primary, that is O.K. but I do not understand why it is not seen as sda3. Linux will assign the numbers in ascending sequence, unless you have a extended partition. Then what you see will look like this...

Quote:

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1019 8185086 83 Linux
/dev/sda2 1020 19457 148103235 5 Extended
/dev/sda5 1020 1528 4088511 82 Linux swap / Solaris
/dev/sda6 1529 19457 144014661 83 Linux

This is from my main system.

I believe the problem is sda4 has not got mounted. Note, it did not show up in the 'mount' command you ran. That would explain the error message you got. You could try a mount command. Try a 'mount /dev/sda4' and see what happens.

r3cursive · 03-26-2009, 11:31 AM

iam really sorry for make you confuse..
after that i delete windows partition from system rescue cd..
i just wondering, maybe becouse i delete my windows partition, then partition number become strange like this?

i try to mount /dev/sda4, is working good and i can access it

bgeddy · 03-26-2009, 12:26 PM

Quote:

after that i delete windows partition from system rescue cd..
i just wondering, maybe because i delete my windows partition, then partition number become strange like this?

This will cause a gap in the partition numbers. Note you also have an area of disk now not used between cylinder 3897 and 7720 inclusive. This will be where windows used to live.

You should make sure your /etc/fstab reflects your disk layout - in particular mounting /dev/sda4 to /home. To fix this you may need to boot up with the install disk (CD/DVD) and follow the instructions. In particular enter:

Code:

hugesmp.s root=/dev/sda2 rdinit= ro

Then fix your fstab and restart. Alternatively you may get away with booting as normal and fixing fstab.

camorri · 03-26-2009, 12:27 PM

Quote:

iam really sorry for make you confuse..

You didn't confuse me, the things that were showing in your posts were not making sense.

I can only assume deleting the windoze partition made for some of the strange numbering.

Quote:

i try to mount /dev/sda4, is working good and i can access it

Good, glad you got it going.

r3cursive · 03-26-2009, 01:47 PM

finally, everything works normally now
bgeddy and camorri, thanks for all your help