2001-10-18 23:33:45

by jimmy

[permalink] [raw]
Subject: UNABLE TO BOOT WITH 2nd SCSI DRIVE

Hello,

I hope you can shed a light to my problem. The server
works just fine with a single SCSI drive.
Unfortunately, when we add the 2nd SCSI drive, the
system does not boot.

VFS: Cannot open root dev "802" or 08:02
Please append correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:02

We have tried all SCSI ID combinations with no
success. LILO 'append="root=/dev/sda2"' command line
does not work. 802 above is our /dev/sda2 root
partition. We thought Adaptec driver is reshuffling
the drives however 'AIC7XXX=no_reset' LILO command
line does not work either.

I would be forever grateful if someone can offer a
hand.

Many thanks in advance for taking your time.

Jimmy

PS: Sorry if it looks like a cross-post. Server is
running out of disk space and we need to get the 2nd
drive added to the system. My apologies.

Here is some diagnostic information:

P3 866 MHz, BX M/b, 512 MB Ram, 9.1 GB SCSI IBM hd.
(works fine)
2nd HD: Cheetah 15000 RPM 36 GB hd (gives problem when
added to the system)
Adaptec 29160 Ultra160 SCSI adapter

Redhat 7.1, 2.4.2 Enterprise kernel (Adaptec Driver is
built into the kernel, not as module)

Kernel command line:
auto BOOT_IMAGE=x ro root=802
BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
root=/dev/sda2

/proc/scsi/scsi:
Attached devices:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: DNES-309170W Rev: SAH0
Type: Direct-Access ANSI SCSI
revision: 03

/etc/lilo.conf:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=5
message=/boot/message
linear
default=x
append="root=/dev/sda2"

image=/boot/vmlinuz-2.4.2-2
label=linux
initrd=/boot/initrd-2.4.2-2.img
read-only
root=/dev/sda2

image=/boot/vmlinuz-2.4.2-2enterprise
label=x5
# initrd=/boot/initrd-2.4.2-2enterprise.img
read-only
root=/dev/sda2


DMESG:
Linux version 2.4.2-2enterprise (root@localhost) (gcc
version 2.96 20000731 (X Net 5.0 2.96-81)) #1 Sun May
13 12:35:36 GM
T+4 2001
BIOS-provided physical RAM map:
BIOS-e820: 000000000009fc00 @ 0000000000000000
(usable)
BIOS-e820: 0000000000000400 @ 000000000009fc00
(usable)
BIOS-e820: 0000000000010000 @ 00000000000f0000
(reserved)
BIOS-e820: 0000000000500000 @ 00000000ffb00000
(reserved)
BIOS-e820: 000000001fdf0000 @ 0000000000100000
(usable)
BIOS-e820: 000000000000d000 @ 000000001fef3000 (ACPI
data)
BIOS-e820: 0000000000003000 @ 000000001fef0000 (ACPI
NVS)
Scan SMP from 40000000 for 1024 bytes.
Scan SMP from 4009fc00 for 1024 bytes.
Scan SMP from 400f0000 for 65536 bytes.
Scan SMP from 40000000 for 4096 bytes.
On node 0 totalpages: 130800
zone(0): 4096 pages.
zone DMA has max 32 cached pages.
zone(1): 126704 pages.
zone Normal has max 989 cached pages.
zone(2): 0 pages.
zone HighMem has max 1 cached pages.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
mapped APIC to ffffe000 (fee00000)
Kernel command line: auto BOOT_IMAGE=x ro root=802
BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
root=/dev/sda2
Initializing CPU#0
Detected 868.653 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1730.15 BogoMIPS
Memory: 512088k/523200k available (1451k kernel code,
10724k reserved, 78k data, 180k init, 0k highmem)
Dentry-cache hash table entries: 65536 (order: 7,
524288 bytes)
Buffer-cache hash table entries: 32768 (order: 5,
131072 bytes)
Page-cache hash table entries: 131072 (order: 8,
1048576 bytes)
Inode-cache hash table entries: 32768 (order: 6,
262144 bytes)
VFS: Diskquotas version dquot_6.5.0 initialized
CPU: Before vendor init, caps: 0387fbff 00000000
00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0387fbff 00000000
00000000 00000000
CPU serial number disabled.
CPU: After generic, caps: 0383fbff 00000000 00000000
00000000
CPU: Common caps: 0383fbff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Getting VERSION: 40011
Getting VERSION: 40011
Getting ID: 0
Getting ID: f000000
Getting LVT0: 700
Getting LVT1: 400
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000040
ESR value after enabling vector: 00000000
calibrating APIC timer ...
..... CPU clock speed is 868.6803 MHz.
..... host bus clock speed is 133.6430 MHz.
cpu: 0, clocks: 1336430, slice: 668215
CPU0<T0:1336416,T1:668192,D:9,S:668215,C:1336430>
mtrr: v1.37 (20001109) Richard Gooch
([email protected])
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb120, last
bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd v1.8
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
block: queued sectors max/low 340021kB/208949kB, 1024
slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
hdc: ATAPI 48X CDROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 48X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.12
NET4: Frame Diverter 0.46
loop: loaded (max 8 devices)
i810_rng: cannot reserve RNG region
Software Watchdog Timer: 0.05, timer margin: 60 sec
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by
Andrey V. Savochkin <[email protected]> and others
PCI: Found IRQ 12 for device 01:02.0
divert: allocating divert_blk for eth0
eth0: Intel Corporation 82557 [Ethernet Pro 100],
00:D0:B7:BD:D2:84, I/O at 0xc400, IRQ 12.
Board assembly 721383-009, Physical connectors
present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
cipcb: CIPE driver vers 1.4.5 (c) Olaf Titz 1996-2000,
100 channels, debug=1
cipcb: cipe_alloc_dev 0
divert: not allocating divert_blk for non-ethernet
device cipcb0
divert: not allocating divert_blk for non-ethernet
device dummy0
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory:
438M
agpgart: agpgart: Detected an Intel i815 Chipset.
agpgart: AGP aperture is 64M @ 0xd0000000
[drm] AGP 0.99 on Intel i810 @ 0xd0000000 64MB
[drm] Initialized i810 1.1.0 20000928 on minor 63
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
PCI: Found IRQ 11 for device 01:00.0
IRQ routing conflict in pirq table for device 00:1f.4
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER,
Rev 6.1.7
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Wide Channel A, SCSI Id=7, 32/255
SCBs

Vendor: IBM Model: DNES-309170W Rev: SAH0
Type: Direct-Access ANSI SCSI
revision: 03
scsi0:0:6:0: Tagged Queuing enabled. Depth 8
Attached scsi disk sda at scsi0, channel 0, id 6, lun
0
(scsi0:A:6): 40.000MB/s transfers (20.000MHz, offset
31, 16bit)
SCSI device sda: 17916240 512-byte hdwr sectors (9173
MB)
Partition check:
sda: sda1 sda2 sda3
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind
32768)
ip_conntrack (4087 buckets, 32696 max)
ip_tables: (c)2000 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 180k freed
Adding Swap: 120476k swap-space (priority -1)

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com


2001-10-18 23:44:37

by Jeffrey W. Baker

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE



On Thu, 18 Oct 2001, jimmy wrote:

> Hello,
>
> I hope you can shed a light to my problem. The server
> works just fine with a single SCSI drive.
> Unfortunately, when we add the 2nd SCSI drive, the
> system does not boot.

You've made sure that your original drive (the IBM) has the lowest ID
number on the bus?

> P3 866 MHz, BX M/b, 512 MB Ram, 9.1 GB SCSI IBM hd.
> (works fine)
> 2nd HD: Cheetah 15000 RPM 36 GB hd (gives problem when
> added to the system)

Looks like you put a UW drive (the IBM) on the same u160/lvd channel as a
u160/lvd drive (the Seagate). Should work fine but this is where I would
focus my suspicion.

Note that a UW bus needs to be really, really short. How long is your
cabling end-to-end?

-jwb

2001-10-19 01:09:21

by Jim Roland

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE

Check to make sure the SCSI IDs assigned on the drives (see the jumpers on
each drive) are all unique. 2 drives set with no jumpers to the same ID
(SCSI #0) will not let your system boot...all drives must be unique.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jim Roland, RHCE (RedHat Certified Engineer)
Owner, Roland Internet Services
"The four surefire rules for success: Show up, Pay attention, Ask
questions, Don't quit."
--Rob Gilbert, PH.D.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

----- Original Message -----
From: "jimmy" <[email protected]>
To: <[email protected]>
Sent: Thursday, October 18, 2001 6:33 PM
Subject: UNABLE TO BOOT WITH 2nd SCSI DRIVE


> Hello,
>
> I hope you can shed a light to my problem. The server
> works just fine with a single SCSI drive.
> Unfortunately, when we add the 2nd SCSI drive, the
> system does not boot.
>
> VFS: Cannot open root dev "802" or 08:02
> Please append correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 08:02
>
> We have tried all SCSI ID combinations with no
> success. LILO 'append="root=/dev/sda2"' command line
> does not work. 802 above is our /dev/sda2 root
> partition. We thought Adaptec driver is reshuffling
> the drives however 'AIC7XXX=no_reset' LILO command
> line does not work either.
>
> I would be forever grateful if someone can offer a
> hand.
>
> Many thanks in advance for taking your time.
>
> Jimmy
>
> PS: Sorry if it looks like a cross-post. Server is
> running out of disk space and we need to get the 2nd
> drive added to the system. My apologies.
>
> Here is some diagnostic information:
>
> P3 866 MHz, BX M/b, 512 MB Ram, 9.1 GB SCSI IBM hd.
> (works fine)
> 2nd HD: Cheetah 15000 RPM 36 GB hd (gives problem when
> added to the system)
> Adaptec 29160 Ultra160 SCSI adapter
>
> Redhat 7.1, 2.4.2 Enterprise kernel (Adaptec Driver is
> built into the kernel, not as module)
>
> Kernel command line:
> auto BOOT_IMAGE=x ro root=802
> BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
> root=/dev/sda2
>
> /proc/scsi/scsi:
> Attached devices:
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: IBM Model: DNES-309170W Rev: SAH0
> Type: Direct-Access ANSI SCSI
> revision: 03
>
> /etc/lilo.conf:
> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=5
> message=/boot/message
> linear
> default=x
> append="root=/dev/sda2"
>
> image=/boot/vmlinuz-2.4.2-2
> label=linux
> initrd=/boot/initrd-2.4.2-2.img
> read-only
> root=/dev/sda2
>
> image=/boot/vmlinuz-2.4.2-2enterprise
> label=x5
> # initrd=/boot/initrd-2.4.2-2enterprise.img
> read-only
> root=/dev/sda2
>
>
> DMESG:
> Linux version 2.4.2-2enterprise (root@localhost) (gcc
> version 2.96 20000731 (X Net 5.0 2.96-81)) #1 Sun May
> 13 12:35:36 GM
> T+4 2001
> BIOS-provided physical RAM map:
> BIOS-e820: 000000000009fc00 @ 0000000000000000
> (usable)
> BIOS-e820: 0000000000000400 @ 000000000009fc00
> (usable)
> BIOS-e820: 0000000000010000 @ 00000000000f0000
> (reserved)
> BIOS-e820: 0000000000500000 @ 00000000ffb00000
> (reserved)
> BIOS-e820: 000000001fdf0000 @ 0000000000100000
> (usable)
> BIOS-e820: 000000000000d000 @ 000000001fef3000 (ACPI
> data)
> BIOS-e820: 0000000000003000 @ 000000001fef0000 (ACPI
> NVS)
> Scan SMP from 40000000 for 1024 bytes.
> Scan SMP from 4009fc00 for 1024 bytes.
> Scan SMP from 400f0000 for 65536 bytes.
> Scan SMP from 40000000 for 4096 bytes.
> On node 0 totalpages: 130800
> zone(0): 4096 pages.
> zone DMA has max 32 cached pages.
> zone(1): 126704 pages.
> zone Normal has max 989 cached pages.
> zone(2): 0 pages.
> zone HighMem has max 1 cached pages.
> Local APIC disabled by BIOS -- reenabling.
> Found and enabled local APIC!
> mapped APIC to ffffe000 (fee00000)
> Kernel command line: auto BOOT_IMAGE=x ro root=802
> BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
> root=/dev/sda2
> Initializing CPU#0
> Detected 868.653 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1730.15 BogoMIPS
> Memory: 512088k/523200k available (1451k kernel code,
> 10724k reserved, 78k data, 180k init, 0k highmem)
> Dentry-cache hash table entries: 65536 (order: 7,
> 524288 bytes)
> Buffer-cache hash table entries: 32768 (order: 5,
> 131072 bytes)
> Page-cache hash table entries: 131072 (order: 8,
> 1048576 bytes)
> Inode-cache hash table entries: 32768 (order: 6,
> 262144 bytes)
> VFS: Diskquotas version dquot_6.5.0 initialized
> CPU: Before vendor init, caps: 0387fbff 00000000
> 00000000, vendor = 0
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 256K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 0387fbff 00000000
> 00000000 00000000
> CPU serial number disabled.
> CPU: After generic, caps: 0383fbff 00000000 00000000
> 00000000
> CPU: Common caps: 0383fbff 00000000 00000000 00000000
> CPU: Intel Pentium III (Coppermine) stepping 06
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> Getting VERSION: 40011
> Getting VERSION: 40011
> Getting ID: 0
> Getting ID: f000000
> Getting LVT0: 700
> Getting LVT1: 400
> enabled ExtINT on CPU#0
> ESR value before enabling vector: 00000040
> ESR value after enabling vector: 00000000
> calibrating APIC timer ...
> ..... CPU clock speed is 868.6803 MHz.
> ..... host bus clock speed is 133.6430 MHz.
> cpu: 0, clocks: 1336430, slice: 668215
> CPU0<T0:1336416,T1:668192,D:9,S:668215,C:1336430>
> mtrr: v1.37 (20001109) Richard Gooch
> ([email protected])
> mtrr: detected mtrr type: Intel
> PCI: PCI BIOS revision 2.10 entry at 0xfb120, last
> bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Unknown bridge resource 2: assuming transparent
> PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society
> NET3.039
> Initializing RT netlink socket
> Starting kswapd v1.8
> Detected PS/2 Mouse Port.
> pty: 256 Unix98 ptys configured
> block: queued sectors max/low 340021kB/208949kB, 1024
> slots per queue
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes;
> override with idebus=xx
> hdc: ATAPI 48X CDROM, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> hdc: ATAPI 48X CD-ROM drive, 128kB Cache
> Uniform CD-ROM driver Revision: 3.12
> NET4: Frame Diverter 0.46
> loop: loaded (max 8 devices)
> i810_rng: cannot reserve RNG region
> Software Watchdog Timer: 0.05, timer margin: 60 sec
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by
> Andrey V. Savochkin <[email protected]> and others
> PCI: Found IRQ 12 for device 01:02.0
> divert: allocating divert_blk for eth0
> eth0: Intel Corporation 82557 [Ethernet Pro 100],
> 00:D0:B7:BD:D2:84, I/O at 0xc400, IRQ 12.
> Board assembly 721383-009, Physical connectors
> present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
> cipcb: CIPE driver vers 1.4.5 (c) Olaf Titz 1996-2000,
> 100 channels, debug=1
> cipcb: cipe_alloc_dev 0
> divert: not allocating divert_blk for non-ethernet
> device cipcb0
> divert: not allocating divert_blk for non-ethernet
> device dummy0
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory:
> 438M
> agpgart: agpgart: Detected an Intel i815 Chipset.
> agpgart: AGP aperture is 64M @ 0xd0000000
> [drm] AGP 0.99 on Intel i810 @ 0xd0000000 64MB
> [drm] Initialized i810 1.1.0 20000928 on minor 63
> SCSI subsystem driver Revision: 1.00
> request_module[scsi_hostadapter]: Root fs not mounted
> PCI: Found IRQ 11 for device 01:00.0
> IRQ routing conflict in pirq table for device 00:1f.4
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER,
> Rev 6.1.7
> <Adaptec 29160 Ultra160 SCSI adapter>
> aic7892: Wide Channel A, SCSI Id=7, 32/255
> SCBs
>
> Vendor: IBM Model: DNES-309170W Rev: SAH0
> Type: Direct-Access ANSI SCSI
> revision: 03
> scsi0:0:6:0: Tagged Queuing enabled. Depth 8
> Attached scsi disk sda at scsi0, channel 0, id 6, lun
> 0
> (scsi0:A:6): 40.000MB/s transfers (20.000MHz, offset
> 31, 16bit)
> SCSI device sda: 17916240 512-byte hdwr sectors (9173
> MB)
> Partition check:
> sda: sda1 sda2 sda3
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 4096 buckets, 32Kbytes
> TCP: Hash tables configured (established 32768 bind
> 32768)
> ip_conntrack (4087 buckets, 32696 max)
> ip_tables: (c)2000 Netfilter core team
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 180k freed
> Adding Swap: 120476k swap-space (priority -1)
>
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

2001-10-19 01:18:24

by jimmy

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE

Hello Jim,

Yes, the IDs are unique and in the correct order (9.1
GB IBM drive (boot) at ID:0, 36 GB 15K Cheetah at
ID:1) as I have mentioned in the first mail.

It might also be helpful to note that the following
error shows for both drives before kernel panic:

"parity error detected in Data-in phase"

Redhat 7.1 System with Adaptec Driver compiled into
the kernel.

Thanks,
Jimmy



--- Jim Roland <[email protected]> wrote:
> Check to make sure the SCSI IDs assigned on the
> drives (see the jumpers on
> each drive) are all unique. 2 drives set with no
> jumpers to the same ID
> (SCSI #0) will not let your system boot...all drives
> must be unique.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Jim Roland, RHCE (RedHat Certified Engineer)
> Owner, Roland Internet Services
> "The four surefire rules for success: Show up,
> Pay attention, Ask
> questions, Don't quit."
> --Rob Gilbert, PH.D.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> ----- Original Message -----
> From: "jimmy" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, October 18, 2001 6:33 PM
> Subject: UNABLE TO BOOT WITH 2nd SCSI DRIVE
>
>
> > Hello,
> >
> > I hope you can shed a light to my problem. The
> server
> > works just fine with a single SCSI drive.
> > Unfortunately, when we add the 2nd SCSI drive, the
> > system does not boot.
> >
> > VFS: Cannot open root dev "802" or 08:02
> > Please append correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on
> 08:02
> >
> > We have tried all SCSI ID combinations with no
> > success. LILO 'append="root=/dev/sda2"' command
> line
> > does not work. 802 above is our /dev/sda2 root
> > partition. We thought Adaptec driver is
> reshuffling
> > the drives however 'AIC7XXX=no_reset' LILO command
> > line does not work either.
> >
> > I would be forever grateful if someone can offer a
> > hand.
> >
> > Many thanks in advance for taking your time.
> >
> > Jimmy
> >
> > PS: Sorry if it looks like a cross-post. Server is
> > running out of disk space and we need to get the
> 2nd
> > drive added to the system. My apologies.
> >
> > Here is some diagnostic information:
> >
> > P3 866 MHz, BX M/b, 512 MB Ram, 9.1 GB SCSI IBM
> hd.
> > (works fine)
> > 2nd HD: Cheetah 15000 RPM 36 GB hd (gives problem
> when
> > added to the system)
> > Adaptec 29160 Ultra160 SCSI adapter
> >
> > Redhat 7.1, 2.4.2 Enterprise kernel (Adaptec
> Driver is
> > built into the kernel, not as module)
> >
> > Kernel command line:
> > auto BOOT_IMAGE=x ro root=802
> > BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
> > root=/dev/sda2
> >
> > /proc/scsi/scsi:
> > Attached devices:
> > Host: scsi0 Channel: 00 Id: 06 Lun: 00
> > Vendor: IBM Model: DNES-309170W Rev:
> SAH0
> > Type: Direct-Access ANSI
> SCSI
> > revision: 03
> >
> > /etc/lilo.conf:
> > boot=/dev/sda
> > map=/boot/map
> > install=/boot/boot.b
> > prompt
> > timeout=5
> > message=/boot/message
> > linear
> > default=x
> > append="root=/dev/sda2"
> >
> > image=/boot/vmlinuz-2.4.2-2
> > label=linux
> > initrd=/boot/initrd-2.4.2-2.img
> > read-only
> > root=/dev/sda2
> >
> > image=/boot/vmlinuz-2.4.2-2enterprise
> > label=x5
> > # initrd=/boot/initrd-2.4.2-2enterprise.img
> > read-only
> > root=/dev/sda2
> >
> >
> > DMESG:
> > Linux version 2.4.2-2enterprise (root@localhost)
> (gcc
> > version 2.96 20000731 (X Net 5.0 2.96-81)) #1 Sun
> May
> > 13 12:35:36 GM
> > T+4 2001
> > BIOS-provided physical RAM map:
> > BIOS-e820: 000000000009fc00 @ 0000000000000000
> > (usable)
> > BIOS-e820: 0000000000000400 @ 000000000009fc00
> > (usable)
> > BIOS-e820: 0000000000010000 @ 00000000000f0000
> > (reserved)
> > BIOS-e820: 0000000000500000 @ 00000000ffb00000
> > (reserved)
> > BIOS-e820: 000000001fdf0000 @ 0000000000100000
> > (usable)
> > BIOS-e820: 000000000000d000 @ 000000001fef3000
> (ACPI
> > data)
> > BIOS-e820: 0000000000003000 @ 000000001fef0000
> (ACPI
> > NVS)
> > Scan SMP from 40000000 for 1024 bytes.
> > Scan SMP from 4009fc00 for 1024 bytes.
> > Scan SMP from 400f0000 for 65536 bytes.
> > Scan SMP from 40000000 for 4096 bytes.
> > On node 0 totalpages: 130800
> > zone(0): 4096 pages.
> > zone DMA has max 32 cached pages.
> > zone(1): 126704 pages.
> > zone Normal has max 989 cached pages.
> > zone(2): 0 pages.
> > zone HighMem has max 1 cached pages.
> > Local APIC disabled by BIOS -- reenabling.
> > Found and enabled local APIC!
> > mapped APIC to ffffe000 (fee00000)
> > Kernel command line: auto BOOT_IMAGE=x ro root=802
> > BOOT_FILE=/boot/vmlinuz-2.4.2-2enterprise
> > root=/dev/sda2
> > Initializing CPU#0
> > Detected 868.653 MHz processor.
> > Console: colour VGA+ 80x25
> > Calibrating delay loop... 1730.15 BogoMIPS
> > Memory: 512088k/523200k available (1451k kernel
> code,
> > 10724k reserved, 78k data, 180k init, 0k highmem)
> > Dentry-cache hash table entries: 65536 (order: 7,
> > 524288 bytes)
> > Buffer-cache hash table entries: 32768 (order: 5,
> > 131072 bytes)
> > Page-cache hash table entries: 131072 (order: 8,
> > 1048576 bytes)
> > Inode-cache hash table entries: 32768 (order: 6,
> > 262144 bytes)
> > VFS: Diskquotas version dquot_6.5.0 initialized
> > CPU: Before vendor init, caps: 0387fbff 00000000
> > 00000000, vendor = 0
> > CPU: L1 I cache: 16K, L1 D cache: 16K
> > CPU: L2 cache: 256K
> > Intel machine check architecture supported.
> > Intel machine check reporting enabled on CPU#0.
> > CPU: After vendor init, caps: 0387fbff 00000000
> > 00000000 00000000
> > CPU serial number disabled.
> > CPU: After generic, caps: 0383fbff 00000000
> 00000000
> > 00000000
> > CPU: Common caps: 0383fbff 00000000 00000000
> 00000000
> > CPU: Intel Pentium III (Coppermine) stepping 06
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support...
> done.
> > Checking 'hlt' instruction... OK.
> > POSIX conformance testing by UNIFIX
> > Getting VERSION: 40011
> > Getting VERSION: 40011
> > Getting ID: 0
> > Getting ID: f000000
> > Getting LVT0: 700
> > Getting LVT1: 400
> > enabled ExtINT on CPU#0
> > ESR value before enabling vector: 00000040
> > ESR value after enabling vector: 00000000
> > calibrating APIC timer ...
> > ..... CPU clock speed is 868.6803 MHz.
> > ..... host bus clock speed is 133.6430 MHz.
> > cpu: 0, clocks: 1336430, slice: 668215
> > CPU0<T0:1336416,T1:668192,D:9,S:668215,C:1336430>
>
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

2001-10-19 09:06:27

by Russell King

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE

On Thu, Oct 18, 2001 at 04:33:59PM -0700, jimmy wrote:
> I hope you can shed a light to my problem. The server
> works just fine with a single SCSI drive.
> Unfortunately, when we add the 2nd SCSI drive, the
> system does not boot.

You've given all the information for the case that works, but no information
about the case that doesn't work.

> Host: scsi0 Channel: 00 Id: 06 Lun: 00

If this drive remains as ID 6, and your new drive has a lower ID, then
the new drive will become sda, and this one will move to sdb. A possible
solution would be to configure this drive as ID 0, and your new drive
as ID 1.

> Vendor: IBM Model: DNES-309170W Rev: SAH0
> Type: Direct-Access ANSI SCSI
> revision: 03
>...


> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.7
> <Adaptec 29160 Ultra160 SCSI adapter>
> aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs
>
> Vendor: IBM Model: DNES-309170W Rev: SAH0
> Type: Direct-Access ANSI SCSI
> revision: 03
> scsi0:0:6:0: Tagged Queuing enabled. Depth 8
> Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
> (scsi0:A:6): 40.000MB/s transfers (20.000MHz, offset 31, 16bit)
> SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)

What whould be really useful is the above message fragment for the case
where it doesn't boot, particularly which drives it's seeing and the
order it's seeing them.

--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html

2001-10-19 09:55:21

by jimmy

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE

Hello Russell,

> You've given all the information for the case that
> works, but no information
> about the case that doesn't work.

That is because the server is 8000 miles away from me
(other side of the contient) and I am unable to obtain
all the error messages except the kernel panic (last).

FYI, /dev/sda had ID:0 (old drive) and new drive had
ID:1. I have tried all ID configurations but nothing
worked on 2 drive system.

> What whould be really useful is the above message
> fragment for the case
> where it doesn't boot, particularly which drives
> it's seeing and the
> order it's seeing them.

It might also be helpful to note that the following
error shows for both drives before kernel panic:

"parity error detected in Data-in phase"

So, I assume the order of drives are fine. I am
clueless.

Many thanks.

Jimmy

PS: yahoo is being rejected by your mail server.

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

2001-10-19 10:29:53

by Nicholas Berry

[permalink] [raw]
Subject: Re: UNABLE TO BOOT WITH 2nd SCSI DRIVE

Well, I can see a problem. You say the IBM is ID 0.

The driver says it's ID 6. That means your new drive, as ID1, will become sda.

I think the jumper is wrong on your IBM.

Nik


>>> jimmy <[email protected]> 10/19/01 05:55AM >>>
Hello Russell,

> You've given all the information for the case that
> works, but no information
> about the case that doesn't work.

That is because the server is 8000 miles away from me
(other side of the contient) and I am unable to obtain
all the error messages except the kernel panic (last).

FYI, /dev/sda had ID:0 (old drive) and new drive had
ID:1. I have tried all ID configurations but nothing
worked on 2 drive system.

> What whould be really useful is the above message
> fragment for the case
> where it doesn't boot, particularly which drives
> it's seeing and the
> order it's seeing them.

It might also be helpful to note that the following
error shows for both drives before kernel panic:

"parity error detected in Data-in phase"

So, I assume the order of drives are fine. I am
clueless.

Many thanks.

Jimmy

PS: yahoo is being rejected by your mail server.

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com