SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have installed Slackware 14 on a disk with 4096 byte physical sectors. Lilo installs OK because I dumped the boot sector to make sure it was there. I have Slack on sda and Win7 on sdb. When I try to boot I get the Win7 loader from sdb. The only way I can boot is to use the install disk specifying my installed root.
Has anyone else seen this problem?
Here is my drive as seen during boot:
ata1.00: ATA-8: ST500DM002-1BD142, KC45, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA ST500DM002-1BD14 KC45 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 2:0:0:0: [sda] 4096-byte physical blocks
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Here is the fdisk output:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x26d7f011
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 629147647 314572800 83 Linux
/dev/sda2 629147648 645924863 8388608 82 Linux swap
/dev/sda3 645924864 976773167 165424152 83 Linux
Here is the lilo install output:
LILO version 23.2 (released 09-Apr-2011)
* Copyright (C) 1992-1998 Werner Almesberger (until v20)
* Copyright (C) 1999-2007 John Coffman (until v22)
* Copyright (C) 2009-2011 Joachim Wiedorn (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Compiled at 14:13:34 on Aug 20 2012
Running Linux kernel 3.2.29-smp on i686
Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/sda
0800 26D7F011 /dev/sda
0810 D97237F5 /dev/sdb
0830 67F15ADC /dev/sdd
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
device codes (canonical) = 7
Warning: Unable to determine video adapter in use in the present system.
Using MENU secondary loader
Secondary loader: 18 sectors (0x3600 dataend).
bios_boot = 0x80 bios_map = 0x80 map==boot = 0 map S/N: 26D7F011
Mapping message file /boot/boot_message.txt
Message: 1 sector.
BIOS data check will include auto-suppress check
Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-3.2.29-smp
Setup length is 32 sectors.
Mapped 11838 sectors.
Added Slack-14 *
BIOS VolumeID Device
80 26D7F011 0800
81 D97237F5 0810
82 67F15ADC 0830
Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.
Map file size: 74752 bytes.
RAID device mask 0x0000
2 warnings were issued.
Thanks for the replies. First of all here is my lilo.conf.
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt
# Append any additional kernel parameters:
#timeout = 5
# Normal VGA console
vga = normal
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Slack-14
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
Previously I had Fedora 13 (required by my job) on /dev/sda1 and Slackware on /dev/sda3. Fedora booted OK so I assume the boot order is correct. Now I am running Fedora in VirtualBox, a much better solution.