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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktino022_594fygjrep3zd8zdmg6...@mail.gmail.com
Bug#607301: 1.) More 'No Boot' findings and 2.) effected Grub files; Debian web site grub2 1.99~rc1-6 to rc1-12 changelog text, effected by Bug#622224.
Regarding Bug #607301 No Grub Boot, relation to Bug #64 No Grub Changelogs. Subject: no changelogs created. Grub file sets effected are Debian web site grub2 1.99~rc1-6 to rc1-12 . Quick changing daily Grub Release Candidate files are effected by this. To make Grub maintainers aware, and also to check I am using the correct list. On 11.04.2011 I submitted a notice just for the Grub files effected that I went to look at. a 'BROKEN LINKS notice' for Debian Grub-pc and Grub-rescue-pc to http://lists.debian.org/debian-www/2011/04/msg00086.html I received a response email back highlighting known bug #64. A summary of my submission to debian-www is:- I was hoping to use the following Debian links for: 1.99~rc1-6 to: rc1-12 http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-12/changelog but there is no Debian web site grub2 1.99~rc1-6 to rc1-12 changelog text yet. Changelog link is positioned at the right hand side column called 'Debian Resources'. http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-12/changelog for package pages: http://packages.debian.org/sid/admin/grub-pc and http://packages.debian.org/sid/admin/grub-rescue-pc --- Changing subject back to fault finding bug #607301. Another observation whilst using Debian grub-rescue-cdrom 1.99~rc1-6 to find my /dev/sda1 from the grub-rescue-cdrom command line: grub ls (cd) (cd,msdos1) (fd0) My note: This last ls command takes 3 minutes and 37 seconds to complete on my machine. (cd) (cd,msdos1) (fd0) is displayed instantly, along with the flashing cursor at the end of the same line. the command completion is signified 3 mins, 37 secs later by:- the cursor doing a 'carriage return and line feed' to display: grub -( The flashing cursor appearing on this next line.) I assume that grub is searching unsucessfully for other devices, such as my /sda, then eventually times out. --- For more previous detailed information on Debian bug #607301 at:- http://lists.debian.org/cgi-bin/search?query=607301 I achieved 13 hits when I tried just now. The reason ? Some of my entries have either been reallocated and or closed. In my mind incorrectly, but in good faith. It's not a problem to me. Either way, there is more of my own work details and results in them. --- 07.04.2011 To correct one mistake I made in my earlier posting. While I experimented with grub-rescue-cdrom 1.99~rc1-6 again and editing the default 'GNU/Linux','Booting a command list' to:- echo 0 setparams 'GNU/Linux' echo 1 echo 2 set root=(hd0,1) echo 3 echo linux /vmlinuz root=/dev/sda1 linux /vmlinuz root=/dev/sda1 echo 4 initrd /initrd.img --- 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 0 setparams GNU/Linux 1 2 set root=(hd0,1) 3 linux /vmlinuz root=/dev/sda1 error: hd0 cannot get C/H/S values. 4 5 initrd /initrd.img Press any key to continue... --- So the 'error: hd0 cannot get C/H/S values' message resulted from the stanza ' linuz /vmlinuz root=/dev/sda1 ' probably due to the ' set root=(hd0,1) ' stanza, not working. I am 'best effort' guessing here, I just do not know. This corrects my mistake with my previous post on this observation --- Pressing the Tab key on the keyboard to use the 'command completion' facility while editing the stanza:- set root=( as inset root=([TAB]gives:- Possible devices are: cd fd0 --- Other than keep trying the latest code, does anybody have any ideas what other information I should provide, for me to help progress a resolution to my symptom :- error: hd0 cannot get c/h/s values please ? Again, thanks to all. Regards, McTech. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=dc-7r6vp8hmftwxz6dq1+jos...@mail.gmail.com
Bug#607301: Installation-Report: No Boot with Silicon Image SiI 3114 SATA/Raid Controller + single SATA disk drive and GNU/Linux Debian 6.0.0 i386 New install. No raid array used.
Miguel Figueiredo wrote If I understood correctly: Using a Sil 3114 Sata raid controller you are only able to boot sucessfully in rescue mode. My appologies Miguel, I have not made myself clear. My fault. In response to your question Miguel, my short answer is 'no'. I cannot 'rescue - boot' the newly installed pc debian system with, or from, rescue mode, with the aid of the 'rescue cdrom' disk and it's Grub GNU/Linux 'Boot Command List'. The 'rescue cdrom' disk, boots itself in the pc OK ! Having booted the rescue-disk itself, I cannot use the running rescue disk's GNU/Linux 'Command List' to 'rescue - boot' the debian system previously installed on hard disk. McTech wrote at Message #27 received at 607...@bugs.debian.org Subject: No boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, SATA, SiI 3114 Date: 06.03.2011. Fails to boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, The rescue disk boots itself ok, but it does not rescue the machine. The pc does not boot in conjunction with the rescue disk, after succesfully installing from, (except auto booting) versions of :- Debian 6.0.0, wheezy weekly build , unstable-20.02.2011 and also experimemtal-20.02.2011, and experimental-04.03.2011. After I set the rescue-disk-pc GNU/Linux parameters to :- set params 'GNU/Linux' (as it comes, a blank line here) set root=(hd0,1) linux /boot/vmlinux-2.6.37-2-486 root=/dev/sda1 initrd /boot/initrd.img-2.6.37-2-486 The rescue-disk-pc Boot Symptom is :- error: hd0 cannot get c/h/s values error: you need to load the kernel first. press any key to continue grub ls (cd) (cd,msdos1) (fd0) Today, 10.04.2011, I can see Ubuntu's https://launchpad.net/ubuntu/natty/+source/grub2/1.99~rc1-10ubuntu1 I can also see the following Debian link is there at http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-10/changelog but no Debian web site, Grub rc1-10 changelog text yet. http://packages.debian.org/changelogs/pool/main/g/grub2/ no rc1-10 entry yet. I will wait a while. --- Minor corrections to errors I made in my previous 04.04.2011 posting:- Using debian-rescue-cdrom Grub 1.99~rc1-6 should be Using Debian grub-rescue-cdrom 1.99~rc1-6 issue suappears should be issue appears . root@grml / # /dev/sda0(just to see) should be root@grml / # ls /dev/sda0 (just to see) ls: cannot access /dev/sda0 : No such file or directory. Again, thank your help Miguel. It is appreciated. Regards, McTech. I am progressing this potential grub symptom in help-g...@gnu.org I am not sure how I specify specific message or bug numbers, or join / link up the seperate entries there at help-grub. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimngjoda_bbq1jpkxvw_jcirje...@mail.gmail.com
Bug#607301: Cannot boot from debian-6.0.1a-i386-DVD Binary-1 20110322-15:11 and sid 29.03.2011 and debian-rescue-cdrom Grub 1.99~rc1-6 Symptom: error: hd0 cannot get C/H/S values
To address your kind response to me Miguel; I read all the links you gave me for my 'Silicon Image 3114' SATA/Raid controller chip. I also followed and read the sub links. I shall certainly be on the look out for disk corruptions. I could not see any mention of my 'NO BOOT' symptom in the links. including your pointer which eventually lead to Bug 10480 Summary: sil3114 yields ext3_new_block: Allocating block in system zone I came across: https://ata.wiki.kernel.org/index.php/Sata_sil Known problems Some reports of data corruption when paired with NVIDIA chipsets. McTech; I have an ALADDIN5 chipset. For my clarity, that's a number five. The great item I learned from your tip, was that I should not depend searching so much on http:groups.google.com I do not remember coming across your links in my own searching, so thank you. I suppose I was using different search arguments. I thought I had done such a thorough job. I am indebted to you for expanding my search horizons Miguel. If I get data corruption errors, such as kernel: EXT3-fs error kernel: EXT2-fs error or some such, I will know where to look and what to try. So far, I have had no data corruption errors that I am aware of, but then I have not been explicitly looking for them. I have seen no error messages re data corruption, I do get my:- Searching for Boot Record from SCSI..Not Found Boot Failure and that is after a complete installation, of about, I don't know, 15 or 20 various successfull install data transfers. See my /sbin/e2fsck -nv /dev/sda1 clean output below. Of course, I will be looking out in my install logs in future. cat lspci -nn.txt anddmesg -s 100 Output from lspci -nn lspci -nnvvvxxx I will keep a look out for the symptoms described in the following link :- https://bugzilla.kernel.org/show_bug.cgi?id=10480 Comment #8 From Jan Kara 2008-04-24 They (the error messages) generally mean the filesystem is corrupted. In this particular case, bitmap of used blocks is corrupted as system blocks (most likely inode table) are marked as freed in the bitmap of used blocks and then we tried to allocate from there... Miguel, Using grml-daily-sid 110316 codename grml-live-autobuild [2011-03-16] the following is a disk analysis report from my single disk system :- root@grml / # mount /dev/sda1 ... /dev/sda1 on /mnt/sda1 type ext3 (rw) root@grml / # umount /dev/sda1 root@grml / # /sbin/e2fsck -nv /dev/sda1 e2fsck 1.41.12 (17-May-2010) /dev/sda1 was not cleanly unmounted. check forcedMcTech?? Pass1. Checking inodes, blocks, and sizes Pass2. Checking directory structure Pass3. Checking directory connectivity Pass4. Checking reference counts Pass5. Checking group summary information 113443 inodes used (1.16%) 954non-contiguous files (0.8%) 166non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 7293/60/0 1390543 blocks used (3.57%) 0 bad blocks McTech 1 large file 89420 regular files 9396 directories 12character device files 25block device files 2 fifos 419 links 14578 symbolic links (13474 fast symbolic links) 1 socket 113853 files Currently, this disk and controller seems all right to me. So thank you Miguel. I am not sure if the following is the correct protocol. I shall continue my efforts by sending an email Installation-report with package: grub-rescue-pc-1.99~rc1-6 to help-g...@gnu.org. http://lists.gnu.org/archive/html/help-grub/ http://lists.gnu.org/mailman/listinfo/help-grub , and hopefully temporarily put to sleep this thread, Bug#607301 Debian Package: installation-reports here at; http://lists.debian.org/debian-boot/2011/02/msg00320.html I hope this is the correct procedure. If I am standing on anybody's toes, my appologies in advance. Correct procedural guidance is always welcome here. Mucho gracias Miguel F, Melhores cumprimentos. Thank you for your help and time. Best regards,McTech -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTin==Bm50Q9CitBnieT1Lmm2+=i...@mail.gmail.com
