FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 04-26-2011, 06:16 PM
techy techtech
 
Default Bug#607301: I think I misunderstood The SiI 3114 User Manual Page 5. " HDDs Function Normally When Not in RAID Sets. "

Jump to the last 5 paragraphs in this post, at my tag date 21.04.2011 .
I believe I have made a mistake with my configuration set up.

13.04.2011. Otherwise:
The error symptom persists using grub-pc 1.99~rc1-12 on same pc:
AMD K6-2 cpu, Aladdin V chipset system with only one SATA Non raid,
hard disk attached to the SiI 3114 Raid controller.
In the bios:-
1st boot device set to SCSI.
2nd Boot device set to CDROM
With the cdrom empty. The error symptom persists:
"
SiI 3114 SATARaid BIOS Version 5.3.14
Silicon Image, Inc.
Press <Ctrl+S> or F4 to enter RAID utility
0 ST3160815AS 149GB

No valid device! Press any key to continue...
or)
Press <Ctrl+S> or F4 to enter RAID utility

Searching for Boot Record from SCSI..Not Found
Searching for Boot Record from CDROM..Not Found

Boot Failure
Reboot and Select proper Boot device
or insert Boot Media in selected Boot device
Press any key when ready "

---

# less /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST3160815AS_9...A

---
When trying to start the already installed system on /sda1
via the rescue disk in the cdrom drive, using
grub-rescue-cdrom 1.99~rc1-12 from grub-rescue-pc 1.99~rc1-12
The rescue cdrom itself successfully boots on the same machine.

Editing the rescue disk 'GNU/Linux, boot command list'
to experiment only, to help identify where the error messages
are coming from.
I have no intention to boot the system with this experiment edit.

GNU GRUB version 1.99~rc1-12

echo 1 set root=(hd0,1)
set root=(hd0,1)
echo 2
echo 3
echo 4 linux /vmlinuz root=/dev/sda1
/vmlinuz root=/dev/sda1
echo 5
echo 6 end.

Then booting with F10 followed by a quick press of
the Pause/Break key on the keyboard to stop the
screen output timing out and disappearing, gave:

Booting a command list

1 set root=(hd0,1)
2
3
4 Linuz /vmlinuz root=/dev/sda1
error: hd0 cannot get C/H/S values.
5
6 end.

Press any key to continue...
----------------------------------------------

21.04.2011.
It looks like I have made, at least, another mistake.
Reviewing my issue yet again, I decided to check out
when booting up, the Silicon Image Bios message :-
" No valid device! Press any key to continue... "
Yes, the first error message encountered.
I know to follow the first error indication.

I have been searching on the net and discovered
that there are TWO basic types of firmware for the card.
1.) With RAID ( SATARaid )
2.) WithOUT RAID ( SATALink )
Going back and rereading my SATA/Raid card documentation,
along with the internet entries I have since found,
without realising, I had assumed, there would be no change in firmware.
To date, I have not touched the firmware.
I have not loaded the non raid firmware when I started
using a single sata attached hard disk drive.
I thought it would make fault finding easier,
by making things less complex, with just one hard disk.

I will have to rethink the SATARaid User's Manual page 5.
" HDDs Function Normally When Not in RAID Sets. "
copyright 2003 Silicon Image Inc.

I thought the " No valid device! " message meant no valid raid array.
I now believe it means;
that there is no valid Direct Access Storage Device (DASD), that
the BIOS can communicate with. If so, I need to either :-
1.) Install a second disk to make a valid RAID array, or
2.) Change the SiI 3114 to (non raid) SATALink firmware.

For what it's worth,
grub-rescue-cdrom 1.99~rc1-12 and rc1-13 has the same symptoms.
Although this post started life as an Installation Report.
It is now what may probably be a user error (mine).
So with hindsight, I should not be posting on this mailing list.
For politeness and completeness, I will attempt to take this
issue to it's conclusion, elsewhere if need be,
then update a final posting here. I'm learning.

Regards, McTech.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTino022_594fYGJrEp3zD8ZDMg6S1g@mail.gmail.com ">http://lists.debian.org/BANLkTino022_594fYGJrEp3zD8ZDMg6S1g@mail.gmail.com
 

Thread Tools




All times are GMT. The time now is 08:33 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org