[1462] in linux-scsi channel archive
Re: BT-956C + mutating partition table? (2.0.25)
daemon@ATHENA.MIT.EDU (kagel@quasar.bloomberg.com)
Mon Feb 24 18:14:50 1997
Date: Mon, 24 Feb 1997 12:12:56 -0500
From: kagel@quasar.bloomberg.com
To: ptb@dit.upm.es
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <199702231748.SAA04368@oboe.it.uc3m.es> (ptb@it.uc3m.es)
Reply-To: kagel@dg1.bloomberg.com
From: "Peter T. Breuer" <ptb@it.uc3m.es>
Date: Sun, 23 Feb 1997 18:48:41 +0100 (MET)
Can someone tell me why some "Begin" entries in this SCSI fdisk
table _seem_ to have mutated to 1024? I am almost sure they didn't start
life that way.
Device Boot Begin Start End Blocks Id System
/dev/sda1 * 1 1 100 102384 6 DOS 16-bit >=32M
/dev/sda2 152 152 184 33792 83 Linux native
/dev/sda3 185 185 217 33792 83 Linux native
/dev/sda4 218 218 4095 3971072 5 Extended
/dev/sda5 218 218 282 66544 83 Linux native
/dev/sda6 283 283 347 66544 83 Linux native
/dev/sda7 348 348 604 263152 83 Linux native
/dev/sda8 605 605 1117 525296 83 Linux native
/dev/sda9 1024 1118 1246 132080 83 Linux native
/dev/sda10 1024 1247 1311 66544 83 Linux native
/dev/sda11 1024 1312 1440 132080 82 Linux swap
/dev/sda12 1024 1441 2763 1354736 83 Linux native
/dev/sda13 2048 2764 4095 1363952 83 Linux native
/dev/sda3 on / type ext2 (rw)
/dev/sda5 on /var type ext2 (rw)
/dev/sda7 on /usr type ext2 (rw)
/dev/sda9 on /usr/local type ext2 (rw)
/dev/sda10 on /usr/X11R6 type ext2 (rw)
/dev/sda12 on /home type ext2 (rw)
/dev/sda13 on /backup type ext2 (rw)
none on /proc type proc (rw)
/dev/sda1 on /dosc type msdos (rw)
In contrast, dev/sdb on the same machien, which is rarely mounted,
seems quite sane:
Device Boot Begin Start End Blocks Id System
/dev/sdb1 1 1 39 313236 6 DOS 16-bit >=32M
/dev/sdb2 40 40 522 3879697+ 5 Extended
/dev/sdb5 40 40 167 1028128+ 83 Linux native
/dev/sdb6 168 168 295 1028128+ 83 Linux native
/dev/sdb7 296 296 423 1028128+ 83 Linux native
/dev/sdb8 424 424 428 40131 83 Linux native
/dev/sdb9 429 429 461 265041 83 Linux native
/dev/sdb10 462 462 475 112423+ 83 Linux native
/dev/sdb11 476 476 483 64228+ 83 Linux native
I have seen the same effect but worse on an SMP dual PP200 (AIR FX440 ?)
with an onboard aic7880 running ultrawide and that machine is clearly
unstable so I am a little worried. Is this something to worry about?
Or is it normal. Firmware incompatibility or what?
Kernel is 2.0.25. Thansk for any info, good or bad!!! Bootup nmesage
follows.
[SNIP]
linear personality registered
scsi: ***** BusLogic SCSI Driver Version 2.0.6 of 19 October 1996 *****
scsi: Copyright 1995 by Leonard N. Zubkoff <lnz@dandelion.com>
scsi0: Configuring BusLogic Model BT-956C PCI Wide SCSI Host Adapter
scsi0: Firmware Version: 4.28A, I/O Address: 0x330, IRQ Channel: 9/Level
scsi0: DMA Channel: None, BIOS Address: 0xDC000, Host Adapter SCSI ID: 7
scsi0: Scatter/Gather Limit: 128 of 8192 segments, Parity Checking: Enabled
scsi0: Synchronous Initiation: Enabled, Extended Disk Translation: Enabled
^^^^^^^^^^^^^^^^^^^^^^^^^^ Note this
scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi0: Total Queue Depth: 100, Mailboxes: 255, Initial CCBs: 64
scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi0: Host Adapter SCSI Bus Termination (Low/High): Enabled/Enabled
scsi0: Error Recovery Strategy: Default
scsi0: *** BusLogic BT-956C Initialized Successfully ***
scsi0: Target 0: Synchronous at 10.0 mega-transfers/second, offset 14
scsi0: Target 1: Synchronous at 10.0 mega-transfers/second, offset 14
scsi0 : BusLogic BT-956C
scsi : 1 host.
Vendor: SEAGATE Model: ST15230W Rev: 0638
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST15230W Rev: 0298
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
scsi : detected 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8386733 [4095 MB] [4.1 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8386733 [4095 MB] [4.1 GB]
[SNIP]
Software Watchdog Timer: 0.04, timer margin: 60 sec
scsi0: Warning: Extended Translation Setting (> 1GB Switch) does not match
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ See This!
scsi0: Partition Table - Adopting 64/32 Geometry from Partition Table
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ See This!
It looks like the controller BIOS Extended Disk Translation option (to remap
the geometry disks with >1024 cylinders so that DOS can use them) state has
been changed since you created the partition table. Either that or you have
changed controllers since partitioning that drive. I had a similar problem
with my system when I switched controllers from a Future Domain to BusLogic
958. The partition table created under the default translation mapping of the
Future Domain were incompatible with those expected by the BusLogic and REALLY
confused Linux. (I'd bet that MS-DOS fdisk reports the partitions sanely, it
did for me! Also DOS kept reporting bad sectors on this recently formatted
drive!) I finally had to archive and reformat that drive and create the
partition table from scratch with the BusLogic Controller's Translation mode
turned on. No trouble from either DOS or Linux since.
--
Art S. Kagel, kagel@quasar.bloomberg.com
A proverb is no proverb to you 'till life has illustrated it. -- John Keats
