AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080925171652.3827299c@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<abdallah.harb@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E056C984C@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 25 Sep 2008 17:20:15 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: Abdallah Harb <abdallah.harb@onstor.com>
Subject: Re: Kernal Failure
Message-ID: <20080925172015.5d209e32@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E056C984C@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C984C@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I suspect they are not using an approved CF card, or it's a bad card.
None are shown as detected in the boot up messages.

You should see stuff like this, which you don't see:

.
.
.
pcmcia: registering new device pcmcia0.0
scsi0 : pata_pcmcia
ata1: PATA max PIO0 cmd 0x90000000dc000000 ctl 0x90000000dc00000e bmdma 0x0000000000000000 irq 56
ds1511 ds1511: rtc core: registered ds1511 as rtc0
.
.
.

And much more, like

.
.
.
Waiting 1sec before mounting root device...
ata1.00: CFA: CF 1GB, 06/07/29, max PIO2
ata1.00: 2060352 sectors, multi 0: LBA 
ata1.00: configured for PIO0
scsi 0:0:0:0: Direct-Access     ATA      CF 1GB           06/0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 2060352 512-byte hardware sectors (1055 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 2060352 512-byte hardware sectors (1055 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI removable disk
.
.
.


On Thu, 25 Sep 2008 17:06:02 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Andy,
> 
>    Abdallah is having no success in booting a 3510 in the hardware
> lab. He sent this text file to me. After looking at the boot message I
> thought perhaps the /etc/fstab file was messed up on the CF. Abdallah
> gave me the CF he was trying to boot from and the master flash. I
> checked the fstab and mdrive_fstab files on his flashes and they
> looked fine. He is running the system with rev 1.0.8 proms but Brian
> S said the system should boot. I checked his SSC prom environment and
> it appears to be correct as well.
> 
>  
> 
> Any ideas?
> 
>  
> 
> Larry
> 
>  
> 
> ________________________________
> 
> From: Abdallah Harb 
> Sent: Thursday, September 25, 2008 4:12 PM
> To: Larry Scheer
> Subject: Kernal Failure
> 
>  
> 
> Larry,
> 
>  
> 
> Can you please take a look at this attachment of a Cougar (3510) boot
> up capture?
> 
> It occurred on some units with new compact flash cards
> (un-configured).
> 
>  
> 
> The failure occurs prior to getting to the configuration menu and
> displays the following:
> 
> "Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)"
> 
>  
> 
> Any idea what might be causing this failure?
> 
>  
> 
> Thanks,
> 
> Abdallah
> 
>  
> 
>  
> 
>  
> 
>  
> 
