Hello everybody.
I installed Debian 3.0 r0 on my Dell 4100 machine. Everything is OK, but I
noticed the following (little) problem. The last blocks (1, 2 or3) of some
partitions can't be accessed (using badblocks in read mode or dd).
The stange things are:
1: It only happens with some partitions (I can't figure out a
rule).
2: If those partitions has never been mounted since boot up, it
doesn't happen.
3: Once those partitions have been mounted, the problem will arise
(even after those partitions have been unmounted).
I observed this behavior with kernel 2.2.20 (from Debian 3.0). It also happens
with kernel 2.2.16 (from RedHat 7.0). I am pretty sure this is not a hardware
problem (tested with HD diagnostic tools).
My questions are:
Could this behavior lead to filesytem problems?
Is this behaviour universal or only applies to my installation? (I would be very
grateful if someone could test this in its machine).
Below is my current partition table. It was created using fdisk v2.11n (the one
from Debian 3.0 r0). I think it is OK (parted, cfdisk, sfdisk and Ranish
report no problem). In this partition scheme, the problem will happen with
partitions hda3 and hda9.
Thank you in advance.
Javier Miqueleiz.
(I am not subscribed to the list because of the great volume of the
traffic).
*************************************************************************
# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 2434 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 255 2048256 c Win95 FAT32 (LBA)
/dev/hda2 256 638 3076447+ c Win95 FAT32 (LBA)
/dev/hda3 * 639 1340 5638815 83 Linux
/dev/hda4 1341 2434 8787555 f Win95 Ext'd (LBA)
/dev/hda5 1341 1468 1028128+ fd Linux raid
autodetect
/dev/hda6 1469 1838 2971993+ fd Linux raid
autodetect
/dev/hda7 1839 1870 257008+ 83 Linux
/dev/hda8 1871 1902 257008+ 83 Linux
/dev/hda9 1903 1943 329301 82 Linux swap
/dev/hda10 1944 2434 3943926 c Win95 FAT32 (LBA)
*************************************************************************
Below are kernel messages:
*************************************************************************
# dmesg
Linux version 2.2.20 (root@europa) (gcc version 2.95.4 20011002 (Debian prerelease))
#5 Tue Jan 7 23:20:00 CET 2003
BIOS-provided physical RAM map:
BIOS-e820: 0009f000 @ 00000000 (usable)
BIOS-e820: 0fec0000 @ 00100000 (usable)
Detected 797428 kHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1592.52 BogoMIPS
Memory: 257188k/261888k available (1284k kernel code, 416k reserved, 2936k data, 64k
init)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k)
VFS: Diskquotas version dquot_6.4.0 initialized
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
256K L2 cache (8 way)
CPU: L2 Cache: 256K
CPU: Intel Pentium III (Coppermine) stepping 06
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch ([EMAIL PROTECTED])
PCI: PCI BIOS revision 2.10 entry at 0xfda95
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 262144 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=244b
PCI_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD200BB-75AUA1, ATA DISK drive
hdc: SAMSUNG SV0432A, ATA DISK drive
hdd: SAMSUNG DVD-ROM SD-612, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: WDC WD200BB-75AUA1, 19092MB w/2048kB Cache, CHS=2434/255/63
hdc: SAMSUNG SV0432A, 4112MB w/482kB Cache, CHS=8912/15/63, UDMA
hdd: ATAPI 32X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.11
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
linear personality registered
raid0 personality registered
raid1 personality registered
raid5 personality registered
(scsi0) <Adaptec AIC-7850 SCSI host adapter> found at PCI 2/11/0
(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs
(scsi0) Cables present (Int-50 YES, Ext-50 YES)
(scsi0) Downloading sequencer code... 415 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.33/3.2.4
<Adaptec AIC-7850 SCSI host adapter>
scsi : 1 host.
Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.03
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0
(scsi0:0:5:1) Synchronous at 10.0 Mbyte/sec, offset 15.
scsi : detected 1 SCSI generic 1 SCSI cdrom total.
3c59x.c 18Feb01 Donald Becker and others http://www.scyld.com/network/vortex.html
eth0: 3Com 3c905C Tornado at 0xdc00, 00:01:03:28:27:d6, IRQ 11
8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
MII transceiver found at address 24, status 782d.
Enabling bus-master transmits and whole-frame receives.
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
hdc: [PTBL] [524/255/63] hdc1 hdc2 hdc3
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13)
Creative EMU10K1 PCI Audio Driver, version 0.7, 23:20:46 Jan 7 2003
emu10k1: EMU10K1 rev 7 model 0x8022 found, IO at 0xdf80-0xdf9f, IRQ 11
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Adding Swap: 329288k swap-space (priority -1)
Adding Swap: 208836k swap-space (priority -2)
eth0: Initial media type Autonegotiate.
eth0: MII #24 status 782d, link partner capability 45e1, setting full-duplex.
*************************************************************************
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
