Bug#341248: [sarge] bogus Filesystem would be destroyed message

[Elliott Mitchell]

Is this truely a /grave/ bug with /lilo/?

Certainly you were able to use the force option, and LILO did its job;
this is annoying but not unusable. Certainly it didn't cause data loss.
The verbose flag told you what was going on, it had incorrectly detected
the presence of an NT FS. Is there anything left that justifies a grave
severity? Certainly this points to a pessimistic NTFS detector in LILO,
that detected NTFS where it wasn't present. Problem is if it wasn't so
pessimistic, it might destroy NTFS when it was present.

Depending on how things were setup, this could be blamed on the partition
table program you used, for failing to knock out a signature. Might this
be a documentation failure (then whose documentation?), for not telling
you to completely nuke the old boot block?

(note, I am not the maintainer)


-- 
(\___(\___(\__  --= 8-) EHM =--  __/)___/)___/)
 \BS (| [EMAIL PROTECTED] PGP 8881EF59 |)   /
  \_CS\   |  _  -O #include stddisclaimer.h O-   _  |   /  _/
\___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#341248: [sarge] bogus Filesystem would be destroyed message

[Eduard Bloch]

Package: lilo
Version: 22.6.1-6.2
Severity: grave

Hello,

I had problems upgrading an (almost) regular Woody system to Sarge
(bailed out in postinst, which is better than silent failure, though).

And its lilo version still has problems. Look:

netquarter:/# lilo
Fatal: Filesystem would be destroyed by LILO boot sector: /dev/hdc1
netquarter:/# lilo -v5
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 12:32:32 on May 25 2005
Debian GNU/Linux

raid_setup: dev=1602  rdev=1601
raid_setup returns offset =   ndisk = 0
 BIOS   VolumeID   Device
Reading boot sector from /dev/hdc1
geo_get: device 1601, all=1
pf_hard_disk_scan: (22,0) /dev/hdc
pf_hard_disk_scan: (22,1) /dev/hdc1
lookup_dev:  number=1600
lookup_dev:  number=1600
pf:  dev=1600  id=  name=/dev/hdc
geo_query_dev: device=1600
lookup_dev:  number=1600
lookup_dev:  number=0300
exit geo_query_dev
bios_dev:  device 1600
Warning: Int 0x13 function 8 and function 0x48 return different
head/sector geometries for BIOS drive 0x80
fn 08: 1024 cylinders, 255 heads, 63 sectors
fn 48: 29765 cylinders, 16 heads, 63 sectors
lookup_dev:  number=1600
bios_dev:  masked device 1600, which is /dev/hdc
bios_dev: geometry check found 0 matches
bios_dev: (0x80)  vol-ID=  *PT=08078DAE
bios_dev: PT match found 1 match (0x80)
NT partition: /dev/hdc 1 /dev/hdc1
pf_hard_disk_scan: (22,2) /dev/hdc2
pf_hard_disk_scan: (22,3) /dev/hdc3
pf_hard_disk_scan: (22,4) /dev/hdc4
pf_hard_disk_scan: (22,5) /dev/hdc5
pf_hard_disk_scan: (22,6) /dev/hdc6
pf_hard_disk_scan: (22,7) /dev/hdc7
pf_hard_disk_scan: (22,8) /dev/hdc8
pf_hard_disk_scan: (22,9) /dev/hdc9
  1600    /dev/hdc
pf_hard_disk_scan: ndevs=1
  1600    /dev/hdc
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
  1600    /dev/hdc
device codes (user assigned pf) = 1
device codes (user assigned) = 1
device codes (BIOS assigned) = 1
device codes (canonical) = 1
geo_query_dev: device=1601
lookup_dev:  number=1601
exit geo_query_dev
bios_dev:  device 1601
lookup_dev:  number=1600
bios_dev:  masked device 1600, which is /dev/hdc
bios_dev: geometry check found 0 matches
bios_dev: (0x80)  vol-ID=  *PT=08078DAE
bios_dev: PT match found 1 match (0x80)
Device 0x1601: BIOS drive 0x80, 255 heads, 1867 cylinders,
   63 sectors. Partition offset: 63 sectors.
registering bios=0x80  device=0x1601
Using Volume ID  on bios 80
part_verify:  dev_nr=1601, type=1
geo_get: device 1600, all=1
geo_query_dev: device=1600
lookup_dev:  number=1600
exit geo_query_dev
bios_dev:  device 1600
lookup_dev:  number=1600
bios_dev:  masked device 1600, which is /dev/hdc
bios_dev: geometry check found 0 matches
bios_dev: (0x80)  vol-ID=  *PT=08078DAE
bios_dev: PT match found 1 match (0x80)
Device 0x1600: BIOS drive 0x80, 255 heads, 1867 cylinders,
   63 sectors. Partition offset: 0 sectors.
registering bios=0x80  device=0x1600
Using Volume ID  on bios 80
lookup_dev:  number=1600
part_verify:  part#=1
Fatal: Filesystem would be destroyed by LILO boot sector: /dev/hdc1
netquarter:/# lilo -P ignore
Fatal: Filesystem would be destroyed by LILO boot sector: /dev/hdc1
netquarter:/# lilo -F
WARNING: '-F' override used. Filesystem on  /dev/hdc1  may be destroyed.

Proceed? [N/y]y
Added Linux *
Skipping /vmlinuz.old
Added Linux(hdc1)
You have new mail in /var/mail/root
netquarter:/# umount /boot 
netquarter:/# mount /boot/

The filesystem is still allright. No wonder, it is a pure ext2 FS.
netquarter:/# mount 
...
/dev/hdc1 on /boot type ext2 (rw)

The only problem I can see is that this system has been migrated from Windows
environment and I assume that hdc1 has been a windows boot partitition in the
past because strings shows me typical messages in the bootblock, created by
the format.exe utility from german Windows 9x.

However, no such problems appeared while Woody has been installed on that box
few years ago.

I will attach lilo.conf and the bootblock from hdc1 to this report.

Eduard.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.2
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages lilo depends on:
ii  debconf  1.4.59  Debian configuration management sy
ii  libc62.3.5-8.1   GNU C Library: Shared libraries an
ii  libdevmapper1.01 2:1.01.05-1 The Linux Kernel Device Mapper use

lilo recommends no packages.

-- debconf information excluded

-- 
* Alfie hätte auch gerne was von dem, was Joey geraucht hat, als er das
geschrieben hat...
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---   `install-mbr(8)', `/usr/share/doc/lilo/',
#   and