SEO

Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
drive's MBR that lilo uses. I installed the new drive, but the boot
floppy disk wouldn't work. I temporarily reinstalled the old "hda" drive
and booted up. Couldn't make a new bootdisk with "mkbootdisk". Using a
modified "lilo", I installed LILO to a floppy disk. Reinstalled the new
drive as /dev/hda and booted up with the "lilo" floppy disk. I attempted
to install "lilo" on both /dev/hda and /dev/hdc(this contains the linux
RedHat 9.0 system). Couldn't boot up with either hard disk. Looked in
"dmesg" and found the following:

hda: IC35L040AVVA07-0, ATA DISK drive
hdb: FUJITSU MPB3043ATU, ATA DISK drive
blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03bea44, I/O limit 4095Mb (mask 0xffffffff)
hdc: MAXTOR 6L040J2, ATA DISK drive
blk: queue c03bed60, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 80418240 sectors (41174 MB) w/1863KiB Cache, CHS=5005/255/63, UDMA(100)
hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: task_no_data_intr: error=0x04 { DriveStatusError }
hdb: 8448300 sectors (4326 MB), CHS=525/255/63, UDMA(33)
hdc: host protected area => 1

What does "host protected area => 1" mean. I looked in the KT4V bios for
something to turn off the protection, but found nothing.

Am I forever going to have to boot up with a floppy disk?

"Jack Owens" <jack@cox.net> wrote in message
news:VIP5b.119380$Ij4.109402@news2.central.cox.net ...
> Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
> drive's MBR that lilo uses. I installed the new drive, but the boot
> floppy disk wouldn't work. I temporarily reinstalled the old "hda" drive
> and booted up. Couldn't make a new bootdisk with "mkbootdisk". Using a
> modified "lilo", I installed LILO to a floppy disk. Reinstalled the new
> drive as /dev/hda and booted up with the "lilo" floppy disk. I attempted
> to install "lilo" on both /dev/hda and /dev/hdc(this contains the linux
> RedHat 9.0 system). Couldn't boot up with either hard disk. Looked in
> "dmesg" and found the following:
>
> hda: IC35L040AVVA07-0, ATA DISK drive
> hdb: FUJITSU MPB3043ATU, ATA DISK drive
> blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
> blk: queue c03bea44, I/O limit 4095Mb (mask 0xffffffff)
> hdc: MAXTOR 6L040J2, ATA DISK drive
> blk: queue c03bed60, I/O limit 4095Mb (mask 0xffffffff)
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: host protected area => 1
> hda: 80418240 sectors (41174 MB) w/1863KiB Cache, CHS=5005/255/63,
UDMA(100)
> hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: task_no_data_intr: error=0x04 { DriveStatusError }
> hdb: 8448300 sectors (4326 MB), CHS=525/255/63, UDMA(33)
> hdc: host protected area => 1
>
> What does "host protected area => 1" mean. I looked in the KT4V bios for
> something to turn off the protection, but found nothing.
>
> Am I forever going to have to boot up with a floppy disk?

it may be the bios *virus protection* option

(that prevents writing to the boot sector)
>

philo wrote:
> "Jack Owens" <jack@cox.net> wrote in message
> news:VIP5b.119380$Ij4.109402@news2.central.cox.net ...
>
>>Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
>>drive's MBR that lilo uses. I installed the new drive, but the boot
>>floppy disk wouldn't work. I temporarily reinstalled the old "hda" drive
>>and booted up. Couldn't make a new bootdisk with "mkbootdisk". Using a
>>modified "lilo", I installed LILO to a floppy disk. Reinstalled the new
>>drive as /dev/hda and booted up with the "lilo" floppy disk. I attempted
>>to install "lilo" on both /dev/hda and /dev/hdc(this contains the linux
>>RedHat 9.0 system). Couldn't boot up with either hard disk. Looked in
>>"dmesg" and found the following:
>>
>>hda: IC35L040AVVA07-0, ATA DISK drive
>>hdb: FUJITSU MPB3043ATU, ATA DISK drive
>>blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
>>blk: queue c03bea44, I/O limit 4095Mb (mask 0xffffffff)
>>hdc: MAXTOR 6L040J2, ATA DISK drive
>>blk: queue c03bed60, I/O limit 4095Mb (mask 0xffffffff)
>>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>ide1 at 0x170-0x177,0x376 on irq 15
>>hda: host protected area => 1
>>hda: 80418240 sectors (41174 MB) w/1863KiB Cache, CHS=5005/255/63,
>
> UDMA(100)
>
>>hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
>>hdb: task_no_data_intr: error=0x04 { DriveStatusError }
>>hdb: 8448300 sectors (4326 MB), CHS=525/255/63, UDMA(33)
>>hdc: host protected area => 1
>>
>>What does "host protected area => 1" mean. I looked in the KT4V bios for
>>something to turn off the protection, but found nothing.
>>
>>Am I forever going to have to boot up with a floppy disk?
>
>
> it may be the bios *virus protection* option
>
> (that prevents writing to the boot sector)
>
>
>
Virus protection is turned off.

Jack Owens wrote:

> Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
> drive's MBR that lilo uses. I installed the new drive, but the boot
> floppy disk wouldn't work.

Have you read the "Hard-disk-upgrade" HOWTO (or mini-HOWTO)?
It's very good, in my experience.

Alternatively, you could get tomsrtbt -- linux on a floppy --
or Knoppix -- linux on a CD --
and install lilo from that,
assuming you have everthing in place on your new disk.

--
Timothy Murphy
e-mail: tim@birdsnest.maths.tcd.ie
tel: +353-86-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

Jack Owens <jack@cox.net> ha scritto:

>Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
>drive's MBR that lilo uses. I installed the new drive, but the boot
>floppy disk wouldn't work. I temporarily reinstalled the old "hda" drive
You should post lilo.conf and tell where it's located, output of running
lilo and from where you executed it (I assume you partitioned,
formatted, and filled hda?)

>hdc: host protected area => 1
>
>What does "host protected area => 1" mean. I looked in the KT4V bios for
Nothing important, this is just one of those messages developers like to
put to clobber boot messages, they like to see something theirs
everytime their box boots (ie, like "not 100% native mode: will probe
irqs later").

--
giulioo@pobox.com

Giulio Orsero wrote:
> Jack Owens <jack@cox.net> ha scritto:
>
>
>>Recently, S.M.A.R.T said my /dev/hda needed to be replaced. This is the
>>drive's MBR that lilo uses. I installed the new drive, but the boot
>>floppy disk wouldn't work. I temporarily reinstalled the old "hda" drive
>
> You should post lilo.conf and tell where it's located, output of running
> lilo and from where you executed it (I assume you partitioned,
> formatted, and filled hda?)
>
>
>>hdc: host protected area => 1
>>
>>What does "host protected area => 1" mean. I looked in the KT4V bios for
>
> Nothing important, this is just one of those messages developers like to
> put to clobber boot messages, they like to see something theirs
> everytime their box boots (ie, like "not 100% native mode: will probe
> irqs later").
>
lilo.confrompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-8
label=2.4.20-8
append="root=LABEL=/12"
read-only
initrd=/boot/initrd-2.4.20-8.img

image=/boot/vmlinuz-2.4.20-8
label=linux
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/12"

other=/dev/hda3
optional
label=DOS

OUTPUT from lilo execution:

[root@ip68-5-146-253 root]# lilo
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Added 2.4.20-8
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Added linux *
Fatal: First sector of /dev/hda3 doesn't have a valid boot signature

NOTE: new hardisk only has 2 primary partitions

Jack Owens <jack@cox.net> ha scritto:

>image=/boot/vmlinuz-2.4.20-8
> label=2.4.20-8
> append="root=LABEL=/12"
> read-only
> initrd=/boot/initrd-2.4.20-8.img
>
>image=/boot/vmlinuz-2.4.20-8
> label=linux
> initrd=/boot/initrd-2.4.20-8.img
> read-only
> append="root=LABEL=/12"
The above 2 sections use the same kernel with same options, what's the
purpose?

>OUTPUT from lilo execution:
>[root@ip68-5-146-253 root]# lilo
>Warning: BIOS drive 0x82 may not be accessible

>NOTE: new hardisk only has 2 primary partitions

You didn't say:
- from where you are executing lilo (it's the lilo on a floppy?; is it
in hdc from where you booted?). What the exact command line?
- where is the lilo.conf you showed (you have restored it onto hda?)
- what's on hda now? You say 2 partitions, is it hda1 for swap and hda2
for root fs? Is it hda1 for /boot and hda2 for rootfs (no swap?)
- you booted from hdc and mounted hda under some dir?

1)
If you booted from hdc and want to make hda bootable by running lilo (so
that next boot the system will boot from hda), then you need to add to
lilo.conf (that I suppose is into hda)

disk = /dev/hda
bios = 0x80

this is because if you boot from hdc lilo is confused and does not now
that hda will be the 1st hd on next boot. This should eliminate the
message about 0x82 not accessible.

2)
then you need to comment out all the "other = " part (the dos label)
since you didn't restore a dos/win partition on hda.

3)
If you want to boot from hda a linux install that is into hda you ave
another problem; have you recreated the disk labels (/12) on hda? If not
you'd better modifying lilo.conf:
comment out:
append="root=LABEL=/12"
add:
root = /dev/hdaX where X is the right number for the root fs


So, it all depends on what's exactly your config now.

--
giulioo@pobox.com

Giulio Orsero wrote:
......
> - what's on hda now? You say 2 partitions, is it hda1 for swap and hda2
> for root fs? Is it hda1 for /boot and hda2 for rootfs (no swap?)
> - you booted from hdc and mounted hda under some dir?
>
> 1)
> If you booted from hdc and want to make hda bootable by running lilo (so
> that next boot the system will boot from hda), then you need to add to
> lilo.conf (that I suppose is into hda)
>
> disk = /dev/hda
> bios = 0x80
>
> this is because if you boot from hdc lilo is confused and does not now
> that hda will be the 1st hd on next boot. This should eliminate the
> message about 0x82 not accessible.
>
> 2)
> then you need to comment out all the "other = " part (the dos label)
> since you didn't restore a dos/win partition on hda.
>
> 3)
> If you want to boot from hda a linux install that is into hda you ave
> another problem; have you recreated the disk labels (/12) on hda? If not
> you'd better modifying lilo.conf:
> comment out:
> append="root=LABEL=/12"
> add:
> root = /dev/hdaX where X is the right number for the root fs
>
>
> So, it all depends on what's exactly your config now.
>

There is one swap partition on hda1 and one linux partition on hda2.
Both have clean file systems. I tried "root=/dev/hdc2' but that didn't
work. However, you got me to thinking and the following "lilo.conf"
works just fine:
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-8
label=linux
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/12"

Really appreciate your time and effort. It help me solve the problem.