Package: installation-reports
Control: retitle -1 No reboot when installed with Debian v7.0 RC2 Wheezy
i386 on Sil 3114 + SATA drive.
Subject: No reboot when installed with Debian v7.0 RC2 Wheezy i386 on Sil
3114 + SATA drive.
I will use Wheezy 7.0 stable next time, which has since become available.
ISSUE:
I used the same hardware and configuration I detailed earlier in this
report.
GNU,Linux,Debian seemed to successfully install until the reboot.
POST (Power On Self Test) at reboot after installing, shows an error:-
No valid device ! Press any key to continue
MODULES/DRIVERS:
I know Drivers and BIOS have to match up together.
Is this the case with the GNU,Linux,Debian module/driver sata-sil version
2.4 ?
I was wondering which Silicon Image supplied BIOS should be flashed into
the Sil3114 controller to work with the Debian sata_sil v2.4 driver/module,
currently supplied in Wheezy Release Candidate 2 ? Is this my issue ?
I installed using Debian v7.0 RC2 Wheezy i386 20130420-14:50 using the
Graphical Installer,
and have " Sil 3114 SATARaid BIOS Version 5.3.14 " displayed during the
POST of the Motherboard AMIBIOS when connected to a single SATA drive,
which is the only drive in the machine.
Looking at an FAQ listing at www.siliconimage.com/support/ sil3114 PCI to 4
port SATA 150 controller;
Under the heading: "Which Driver and or BIOS should I use ? ( of course
for Microsoft) It says;
When selecting a driver for upgrade or installation, pick the latest
released driver for your Silicon Image controller part number. Install the
driver that is the same type as the BIOS you have installed for your
controller."
I have currently controller BIOS SATARaid (FakeRaid) but want the function
for controller BIOS IDE/nonRAID for use with Linux MDADM software raid.
ENVIRONMENT:
PARTITION DISKS: Guided Partitioning, Use the entire disk,
Select the entire disk, Select the disk to partition,
Partitioning Scheme: All files in one partition.
I resized /swap from 466.6Mb to 2.0GB and / from 159.6GB to 158GB,
This is an overview of your currently configured partitions.
SCSI2 (0,0,0) -160.0 GB ATA ST3160815AS
#1 primary 158.0GB B F ext4 /
#2 primary 2.0GB F swap swap
# /bin/lsmod (Just the interesting modules/drivers.)
ata-generic, pata_ali, sata_sil, scsi_mod, libata, mii, 3c59x.
# /bin/list-devices disk
/dev/sda (OK, correct, I have one hard disk installed.)
LOGS:
# bin/nano /var/log/syslog (Just the interesting lines follow.)
kernel: linux version 3.2.0-4-486 (gcc version 4.6.3 (debian 4.6.3-15) #1
debian 3.2.41-2
kernel: legacy DMI 2.0 present.
kernel: DMI: system manufacturer system name/ALADDIN5, BIOS 0626
kernel: WARNING:
at/build/buildd-linux_3.2.41-2-i386-BfAj4s/linux-3.2.41/arch/x86/pci/irg.c:206
pirg_ali_get +0x23/0x43()
kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
kernel: SCSI subsytem initialised
kernel: libata version 3.00 loaded.
kernel: sata_sil 0000:00:0e.0: version 2.4
kernel: PCI: setting IRQ 9 as level-triggered
kernel: sata_sil 0000:00:0e.0: found PCI INT -> IRQ 9
kernel: sata_sil 0000:00:0e.0: Applying R_ERR on DMA activate FIS errata fix
kernel: scsi0 : sata_sil
kernel: scsi1 : sata_sil
kernel: scsi2 : sata_sil
kernel: scsi3 : sata_sil
kernel: ata1:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec80 irg 9
kernel: ata2:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec00 irg 9
kernel: ata3:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec80 irg 9
kernel: ata4:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec00 irg 9
kernel: scsi4 : pata_ali
kernel: scsi5 : pata_ali
kernel: ata5: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq14
kernel: ata6: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq15
kernel: ata5.01: ATAPI: PIONEER DVD-RW DVR-110, 1.41, max UDMA/66
kernel: ata5.01: WARNING: ATAPI DMA disabled for reliability issues. It can
be enabled
kernel: ata5.01: WARNING: via pata_ali.atapi_dma modparm or corresponding
sysfs node.
kernel: ata5.01: configured for PIO4
kernel: ata1: SATA link down (SStatus 0 SControl 310)
kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
kernel: ata2.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133
kernel: ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
kernel: ata2.00: configured for UDMA/100
kernel: scsi 1:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ:0 ANSI:5
kernel: ata3: SATA link down (SStatus 0 SControl 310)
kernel: ata4: SATA link down (SStatus 0 SControl 310)
kernel: scsi 4:0:1:0: CD-ROM PIONEER DVD-RW DVR-110 1.41 PQ:0 ANSI:5
kernel: sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149
GiB)
kernel: sd 1:0:0:0: [sda] Write Protect is off
kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
kernel: sd 1:0:0:0: [sda] Write cache: enabled, Read cache: enabled,
doesn't support DPO or FUA
kernel: sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda
tray
kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
kernel: sr 4:0:1:0: Attached scsi CD-ROM sr0
kernel: sda: sda1 sda2
kernel: sd 1:0:0:0: [sda] Attached SCSI disk
kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
kernel: sr 4:0:1:0: Attached scsi generic sg1 type 5
...
anna: DEBUG: retrieving scsi-extra-modules-3.2.0-4.486.di 3.2.41-2
The end of the last interesting line of /var/log/syslog .
FAQ EXCERPTS:
at www.siliconimage.com/support/ sil3114 PCI to 4 port SATA 150
controller;
FAQ:
"How can I boot Windows from a drive or RAID set connected to a Silicon
Image controller?"
(I would like to boot GNU/Linux/Debian from a drive, eventually mdadm. Not
a RAID set.)
"In order to boot from a SATA drive or RAID set attached to a Silicon Image
controller, you must add the driver for the controller when prompted during
Windows setup installation so the OS bootstrap process can load the driver
to access the attached drives or RAID set during boot."
(I would like to use GNU/Linux/Debian driver code that boots from a SATA
drive.)
FAQ:
"I installed the required Driver but the storage controller is not working?"
"A Silicon Image storage controller driver that is fully installed but not
working is usually caused by an incompatibility between the BIOS installed
for the controller and the driver. Installing a type of driver that differs
from the installed BIOS type will not work. Problems with matching driver
and BIOS types sometime occur because the drivers require a later release
of BIOS to function correctly. Check the driver download page at Support
for the recommended BIOS version to use with the driver.
When installing or upgrading drivers and BIOS, be sure to always use the
same type of driver and BIOS. Use SATARAID drivers with SATARAID BIOS,
SATARAID5 drivers with SATARAID5 BIOS, and Medley RAID drivers with Medley
RAID BIOS. Use IDE/nonRAID drivers with IDE/nonRAID BIOS. Mixing BIOS and
driver types doesn't work.
You can usually identify the type of BIOS you have from the BIOS boot time
messages. IDE BIOS will have a message with "SATALink" during boot.
SATARAID and SATARAID5 will have a "SATARAID" message. Enter the BIOS
configuration menu by pressing F4 or CNTRL+S to determine whether you have
SATARAID or SATARAID5 BIOS. Only SATARAID 5 BIOS has support for RAID 5.
Medley RAID BIOS has a "Medley RAID" boot time message."
FAQ:
"Which Driver and or BIOS should I use ?
When selecting a driver for upgrade or installation, pick the latest
released driver for your Silicon Image controller part number. Install the
driver that is the same type as the BIOS you have installed for your
controller."
At the end of the install I had:-
Install the GRUB boot loader on a hard disk.
Install the GRUB boot loader to the master boot record? "YES"
Running "grub-install /dev/sda"...
Running "update-grub"... (My note: This step took quite a long time.)
Finish the installation
installation is complete, so it is time to boot into your new system...
When rebooting/ipl'ing the excerpts below appear on the screen.
WAIT...
Pri Slave : 1.41 Pioneer DVD-RW DVR-110
Sil 3114 SATARaid BIOS Version 5.3.14 2006 Silicon Image, Inc.
Press <Ctrl+S> or F4 to enter RAID utility
1 ST3160815AS 149GB
No valid device! Press any key to continue...
(My own note: Above is the first sign of a symptom. <<--*******)
or Press <Ctrl+S> or F4 to enter RAID utility
(The screen clears with a beep)
PCI Devices :Slot 4 RAIS: IRQ 9
Searching for Boot Record from SCSI.. Not Found
Searching for Boot Record from CDROM.. Not Found
Boot Failure
Reboot and Select proper device
Press any key when ready
(My note: End of attempted reboot.)
GOING FORWARD: It is the Silicon Image BIOS that issues the "No valid
device!"
Using the silicon Image FAQ above, my current SATARaid BIOS v5.3.4, in the
controller, wants two disks, to make up a Hardware FakeRaid set, while
ideally, although starting with a single disk, I wanted the IDE/nonRAID
Function in the controller BIOS and a matching function in the linux
sata_sil module/driver to run my SATA disks for mdadm.
I will try two drives next, to prove a point, then Wheezy 7.0 stable, which
has since become available, before I start flashing IDE/nonRAID to the
controller.
My objective is to get away from using the FakeRaid hardware function and
run the drives seperately with Software RAID.
Thank you to all who contributed to v7.0 Wheezy RC2 and Stable.
Regards McTech.
Replies to 70...@bugs.debian.org please, not my own email addrress.
