LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices

Reply
 
Search this Thread
Old 08-28-2004, 06:14 PM   #1
geomatt
Member
 
Registered: Mar 2004
Location: PA
Distribution: Slackware 12.0
Posts: 315

Rep: Reputation: 30
Afraid to reboot after upgrade to 10.0


Hi everyone,

I just upgraded to Slack 10.0 from 9.1 following the instructions in UPGRADE.TXT. As per that document I ran lilo and got the following error message:

root@slack:~# lilo
Fatal: VolumeID read error: sector 0 of /dev/sda not readable

I'm not sure what this means since linux is on /dev/hda4 on my system and /dev/sda is not mentioned anywhere in /etc/lilo.conf.

For more info I ran lilo -v and got:

root@slack:~# lilo -v
LILO version 22.5.9, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda4
Fatal: VolumeID read error: sector 0 of /dev/sda not readable


I'm not sure what any of this means and so I don't want to reboot for fear of not being able to boot linux. Anyone have any advice - are my fears ungrounded, or is this something I should fix before shutting down??

Thanks,
geomatt



And here's the uncommented parts of my /etc/lilo.conf in case it helps diagnose what's going on here:

# Start LILO global section
boot="/dev/hda4"
vga="773"
image="/boot/vmlinuz"
root="/dev/hda4"
label="linux"
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
append="hdc=ide-scsi"
 
Old 08-29-2004, 01:42 AM   #2
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hi

what i think ur
boot="/dev/hda4"

should be
boot=/dev/hda

i have this entry in my lilo.conf

keep us posted , on what do u get ????

regards

gaurav
 
Old 08-29-2004, 08:01 AM   #3
geomatt
Member
 
Registered: Mar 2004
Location: PA
Distribution: Slackware 12.0
Posts: 315

Original Poster
Rep: Reputation: 30
masand,
Thanks for the reply. The reason it is hda4 is because I am dual booting with windows xp and my linux lives on hda4. I tried getting rid of the quotes, but it didn't have any effect.

I do have some new info that may be helpful. Googling on the error message got me the advice that I should add the line

disk=/dev/sda inaccessible

to /etc/lilo.conf. I did this and then ran lilo and got:

root@slack:~# lilo -v
LILO version 22.5.9, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda4
Warning: bypassing VolumeID scan of drive flagged INACCESSIBLE: /dev/sda
Using MENU secondary loader
Calling map_insert_data

Boot image: /boot/vmlinuz -> vmlinuz-ide-2.4.26
Added linux *

Writing boot sector.
/boot/boot.0304 exists - no boot sector backup copy made.


Seems better. But I am still worried about booting with warnings from lilo. Maybe I am being paranoid but I had a bit of a scare a couple weeks ago with lilo and now I'm not taking any chances.

geomatt
 
Old 08-29-2004, 08:16 AM   #4
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hi there
what i think is that u need to specify the boot partion xclusively when u have ur /boot on different drive
i think u should give it a try

try changing
boot=/dev/hda

this is for the lilo to tell that ot ned to boot from the hard disk /dev/hda
here is my lilo.conf

-----------------------------------------

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# For CD-Writer
#append="hdb=ide-scsi"

# For BMP Boot Image
bitmap=/boot/ins64a.bmp
bmp-colors=14,11,;15,9,0
bmp-table=21,287p,2,4,175p
bmp-timer=73,29,12,8,0
install=/boot/boot-bmp.b

#menu-scheme=Wb
boot = /dev/hda
prompt
timeout = 1200
#VESA framebuffer console @ 800x600x64k
vga = 788

image=/boot/vmlinuz-2.6.3gm8
label=2.6.3gm8
initrd=/boot/initrd-2.6.3gm8.img
read-only
append="root=/dev/hda4"



other = /dev/hda1
label = windows
table = /dev/hda
# DOS bootable partition config ends

-------------------------------------------------

i have removed the other entries

regards
 
Old 08-30-2004, 12:12 PM   #5
geomatt
Member
 
Registered: Mar 2004
Location: PA
Distribution: Slackware 12.0
Posts: 315

Original Poster
Rep: Reputation: 30
Hey thanks for the reply.
I ended up doing a clean new installation of Slack 10.0 since I had lots of other issues to deal with. So far so good. Now I gotta try reinstalling some stuff that is not in the standard Slack distro.
Cheers,
geomatt
 
Old 08-30-2004, 12:50 PM   #6
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hey

good that u up and working
but u should get to the root of the problem so that it can be avoided in the future,that help u learn

and keep us posted too ,if u get it

regards
 
Old 07-28-2006, 08:21 AM   #7
alienDog
Member
 
Registered: Apr 2004
Location: Europe
Distribution: Debian, Slackware
Posts: 505

Rep: Reputation: 46
Quote:
Originally Posted by masand
hi

what i think ur
boot="/dev/hda4"

should be
boot=/dev/hda
Makes no difference, I have the same problem and i have:

boot=/dev/hda

Lilo still complains about being unable to read sector 0 of sda (which is quite normal as the sda it's referring to is a removable usb harddrive that is kilometers away from the machine at the moment, I would be amazed if it would be accessible). I will try

disk=/dev/sda inaccessible

trick in lilo.conf as soon as I get home. What I do not understand is why lilo is so worried about the absense of sda since the drive in question has absolutely nothing to do whatsoever with the boot process. This is by far the most stupid bug (or misfeature) I've ever run into.

As far as I know, the message:

Warning: LBA32 addressing assumed

is harmless.

Last edited by alienDog; 07-28-2006 at 08:24 AM.
 
Old 07-28-2006, 08:37 AM   #8
alienDog
Member
 
Registered: Apr 2004
Location: Europe
Distribution: Debian, Slackware
Posts: 505

Rep: Reputation: 46
Whoops, previous posting seems to have been two years ago Anyway Lilo still does this.
 
  


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
No login window after upgrade & reboot. respin4 Red Hat 4 05-23-2005 11:14 PM
Afraid I Have Been Compromised robpom Linux - Security 12 03-31-2005 01:50 AM
need advice: will reinstall winxp, but afraid of hurting fc2 parv Fedora 4 09-26-2004 06:00 PM
ipupdate.pl (afraid.og) error ;( ilhbutshm Linux - Software 1 05-26-2004 08:26 AM
no sound after reboot (after upgrade) Gates1026 Linux - General 8 03-12-2004 12:33 AM


All times are GMT -5. The time now is 08:07 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration