Cannot boot with Perc /2 raid controller

I have just built a system with K7D + 2 2400 MP, and the system hangs when I try to boot with my Perc/2 raid controller in. I have stripped down to just the following components;
2 2400 MP
Perc 2
1GB ECC ram
Sapphire ATI Radeon 9000
When I try to boot the machine it gets as far as trying to load the Perc /2 Bios and hangs.
The Perc works fine in my old system Tyan Tiger 133 with dual 733 PIII, it also seems to boot up fine in a Tyan Tiger S2460.
Any ideas on the cause or a work around?
Thanks.

Yeah, all the firmware & bios is up to date, have stripped things down to just the motherboard, graphics card & Perc. Tried PCI graphics to elliminate any conflicts there. I have disabled all the on-board controllers too.

Similar Messages

Hi, we have a G5 Blade server running OS X 10.5.8 with a dual Fibre Channel card. The OS does not read the card and cannot establish connection to the RAID controller. I have tried to move the card to another port with no luck. Ran all the updated softwar

Hi, we have a G5 Blade server running OS X 10.5.8 with adual Fibre Channel card. The OS does not read the card and cannot establishconnection to the RAID controller.
I have tried to move the card to another port with no luck.Ran all the updated software possible. Please can someone advice

Hi,
Was the card previously working in that machine? If it was and you have a G5 tower you could try the card in there. Here is a list of Apple fibre cards and cables which show what's compatible with what. http://support.apple.com/kb/HT1769
The card should appear in the System Profiler under Fibre Channel and PCI Cards.
All the best
Beatle

C240 M3S can't setup first boot with Cisco UCSC RAID SAS 2008M-8i Mezzanine in BIOS

Hi all,
I have a problem with C240 M3S with boot device.
1. There is a Cisco UCSC RAID SAS 2008M-8i Mezzanine in the C240 M3S
2. I set up the raid5 for four SAS disks with Cisco UCSC RAID SAS 2008M-8i Mezzanine
3. When I install the ESXi 5.5, it can be installed in SAS disks.
4.When I press F2 to setup bios for C240 M3S, I can't find the item for the raid of Cisco UCSC RAID SAS 2008M-8i Mezzanine
5. C240 M3S can't boot from the Cisco UCSC RAID SAS 2008M-8i Mezzanine
6. BIOS have been reloaded for many times, it can't work.
Anybody have any idea for this problem? Thank you!

Sorry,
I can't find the item of local storage.
I never setup the boot order ( default bios can find raid card, I don't know that raid can't be found at this time )
Would you please offer any references, thank you
By the way, I check the install guide for c240 m3
If the RAID controller does not appear in the system boot order even with the option ROMs for those
slots are enabled, the RAID controller option ROM might not have sufficient memory space to
execute. In that case, disable other option ROMs that are not needed for the system configuration to
free up some memory space for the RAID controller option ROM.
this means I want to turn off all option ROMs to get more memory ? However, I turn off all option ROMs, I still can't find the raid.
Thank you very much!!

T440p exactly once per two power ups cannot boot with USB mouse receiver insterted.

With inserted nano Logitech mouse receiver my Lenovo cannot boot once per two power ups.
Let say that I power off laptop. Power on, it just powers down itself after 3-4 seconds. I power up it again and everything is OK. It allways behave the same way: NOTOK >> OK.

engywook wrote:Erm, I dunno, I'd guess input-mouse. I have no idea what evdev is.
evdev is a generic input driver (you can use it for both your mouse and keyboard). If you do not know what the evdev driver is, you most likely are using the xf86-input-mouse driver.
To be sure you can use a
pacman -Q | grep xf86-input
from the command line and see which one comes up. Try switching to the other (you need to install it first of course). This gentoo wiki page may help you a bit how to configure your xorg.conf for an evdev driver: http://gentoo-wiki.com/HOWTO_Advanced_M … d_USB_Mice (note that you do not need most parts that are written there)
Does this solve your problem? If not, try using the vesa video driver temporarily to see if the problem is with your video card driver.
engywook wrote:Do I need to do something with pacman to get all the packages at the mirror? all I've really done so far is pacman -Sy or -Su whatever updates it.
No normally that should work. You don't get any results when doing
pacman -Ss pidgin
If so try to use another mirror and see if that helps.

K7D Master-L with Adaptec 2120S RAID-controller causing errors.

I just installed the Adaptec 2120S RAID-controller on my dual system.
Nothing works, I get BIOS errors, I can't get it to run BUT...
If I remove one CPU and just run one processor everything works great!
I saw a BIOS-fix for this problem (or similar) for the K8T Master2 FAR here:
http://www.msicomputer.com/support/bios_result.asp?platform=AMD&model=K8T_Master2_FAR&newsearch=1
So i figured they might share some common issues with this controller (or maybe not).
Still it might give a clue as to what is wrong.
Any help appriciated (not really happy about having one of the CPU in my drawer).

Just an update to this:
The problem is definately the onboard LAN controller. I've tried a Netgear card as well as a real PCI based Intel Pro 100 card and both are working great. When I take the PCI cards out and try to use the onboard LAN, I still get intermittent outages.
Very strange. If any MSI engineers are listening, I'd love to hear your opinions. According to the OS, there are no IRQ, memory, or other conflicts that might be to blame.
Norm

Cannot boot with new SSD

Installed new OWC 240G SSD in 2007 iMac. Started up with old HD in external case running OS 10.10.2. Initialized SSD with Disk Utilities, and it mounted on the desktop. Transferred contents from old HD to new SSD. Computer boots fine from old HD in external case, but does not boot with internal SSD. After displaying Apple symbol for a few seconds of the startup process, computer goes to a kernel panic and gets into a loop of retry message-Apple symbol-message-etc. The SSD shows on the desktop, but does not show as a startup disk in System Preferences pane. Disk Utilities shows drive is fine, but repair of permissions is grayed out. Window says permissions repair is only permitted on OS installed with an Apple installer. System folder on the SSD does not show the "blessed" symbol. Have tried recloning using Time Machine backup - same result. Installed eDrive on SSD with TechToolsPro, and can start up in eDrive thru TTP window, thus verifying all cabling. After booting with original internal HD installed in external case, SSD will show on desktop, but will disappear in a few minutes after a message says it was improperly ejected. Suggestions? Is there a way to access OS 10 software purchased and downloaded from Apple site?

Many possibilities here. Maybe a bad connection when you installed the drive. Maybe a bad drive. Maybe a bad SATA cable.
How did you format the drive? Should be Mac OS Extended Journaled. When you boot into the recovery drive, access disk utility from there and see if you can access the drive.
I have the same drive as you. What I did is use Disk Utility from the recovery drive of TM. I first re-formatted the SSD drive. Then I used Disk Utility to restore the whole drive of my original to the new SSD drive.
You can still download the Yosemite installer from the App Store in your purchases providing you downloaded it from the App Store already.

[SOLVED] Cannot boot with linux-3.5.3

Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)

because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51)

Cannot boot with PXE on new Intel I217-LM nic card

I imaged a new Dell 5540 with nic I-218LM perfectly by inserting the driver.
After that I did the same with the Lenovo T540p with nic I-217LM which is the same driver "E1D6232.inf" and when I boot into PXE (after changing bios to UEFI network to both or legacy) it finds the SCCM/WDS server and finds the advertisement.
It asks me to press F12, I press it but it doesn't react and the following line is: "PXE-MOF: Exiting Intel Boot Agent". So I find this weird, it's like the key F12 doesn't work. Is there a way to see if this key works?
Does anybody know why it's not going furthur? The correct driver seems to be injected into the boot image. I am using the driver from the lenovo website in the Windows OS after Winpe stage.

After much frustration trying to get the drivers to install for a winpe boot image I found that the issue was it couldn't find the files to copy. The inf file does not tell the install where to find the driver files. Instead it was trying to find them
in x:\windows\inf\ not where they are installed in the pe image simple fix was to copy the files into the windows inf folder and now the drivers install correctly.
I found this by hitting shift-F10 and the running notepad and opened the x:\windows\inf\setupapi.dev.log file, the source path for the driver points to x:\windows\inf (see below)
\machine.inf_amd64_neutral_9e6bb86c3b39a3e9\machine.inf' ([strings])
! sto: Skipping missing driver package file 'e1d62x64.sys'.
! sto: Skipping missing driver package file 'e1d62x64.din'.
! sto: Skipping missing driver package file 'NicCo36.dll'.
! sto: Skipping missing driver package file 'NicInstD.dll'.
! sto: Skipping missing driver package file 'e1dmsg.dll'.
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'x:\windows\inf'
Good luck
L

Cannot boot with graphics card installed

Specs:
MSI R9 280 TWIN FROZR
ASRock H97M
Core i5 4750
Corsair 750W
8GB g.skills
First time builder. Build was turning on (CPU/case/GPU fans running) but going to a black screen with no bios or POST. No mobo beep codes because somehow it doesn't have speaker bumpers. With the R9 unplugged, it gets to bios fine. I triple checked the power cables and seating of the card. Made sure in the BIOS it was set to PCI-E as the default graphics source. Looked on ASRock's site but couldn't find compatibility info.
Is the card a dud, or is there anything else I should try?
Thanks so much

CPU socket was fine. I switched the bios to internal graphics and kept the GPU installed, BIOS could see the card in the slot fine.. which at first I thought meant the gpu was definitely busted. But then, I switched the PCI-E Speed from "auto" to "Gen2" and default GPU back to the PCI-E slot and lo, it worked and booted. Tried "gen3", didn't work. Switched the switch at the top and tried Gen3, and it worked!
Weirdly, messing around again I un-switched the switch and put it back to "Auto", and it still boots fine now..
EDIT: Never mind, still need gen3/switched to the left

Hard drive configuration with Promise Raid controller

I plan on running two 30 gig 75GXP drives on the Promise controller in Raid-0 mode. I also have a 60 gig WD drive that I use for backups and for initial installation. During installation, I put the Win98SE setup files and all the drivers, apps, backup data, etc. on the WD drive and do a clean install from there.
My current (old) board is an Abit KT7-R with the Highpoint raid controller. Using the Highpoint controller, I am able to put the WD drive as a slave device and the controller treats it as a normal IDE drive. I'm moving to the 845 Ultra ARU. From what I've read, if you put a single drive on the Promise controller, it tries to set it up as a Raid drive? I don't want to risk losing my backup data on the WD drive to some attempt by the Promise controller to "raid" my single drive. So, where is the best place to put my WD drive so that I can install my system from it? I'm thinking about putting it as Master on IDE2. I normally run my CD as Master on IDE1. Once the installation is complete, I will remove the installation files from the WD drive and use it exclusively for backups. I have the WD drive in a Vantec EZ-Swap rack, and I normally keep it powered off unless doing a backup.
So, the plan is to create the Raid-0 array, Fdisk and format the array, and then load Windows from the WD drive, followed by all my applications. Is Master on IDE-2 the best solution for the WD drive?

hi
not very clued up on raid but it sounds right
if the wd drive is on its own on that ide do not jumper
as master you have to have no jumpers if all alone

Storage 3320 single raid controller connecting with 02 Host Connection

Dear ALL,
I have 3320 with single raid controller, 5x HDD. I started to install it in a single-bus configuration to meet up with Host & External tape due to the following diagram:
1) using a correct SCSI jumper cable to connect between the SCSI port "CH0" and the SNGL BUS CONF together
2) Connecting the SCSI port labeled "CH1" with SCSI LVD Sun Server running Solaris 9 by SCSI cable
3) Connecting the SCSI port labeled "CH3" with the external tape device by the SCSI cable.
As a result, the Host Server can see the only Logical Drives and i could make the approciate partitions.
But the problem is that the Server could not see the SCSI Tape device on this case (Tape device & cable are fine, tested ok before). I am wondering that if all connection above with connecting to Server & Tape device are ok here, then why is the tape device not being recongised under the Solaris ?? and even it's not being known under the OK prompt when i tried to run probe-scsi...
regards
Scott

Please bypass all questions above, i would like to brief what i need to get helps as the below.
Pls advice me how to get the external SCSI LVD tape device connected with SE 3320 raid Controller WHILE the Array 3320 was connected with Sun Server through the SCSI Port labeled "CH 1", the SCSI jumper cable connected between "CH 0" and the SNGL BUS CONF port in a single-bus configuration (By the way, Se 3320 raid is working well with Server).
Thanks for any comments
Scott

Tiered Storage Spaces with LSI RAID Controller 9260-8i (no JBOD) - Performance Drop

Hello
I have a Lab-Server with a LSI-Raid-Controller 9260-8i and 2x 256GB SSDs / 6x 600GB HDDs. First I configured the LSI-Raid-Controller with a RAID 1 (2x 600GB HDD) and installed
Windows Server 2012 R2 with Hyper-V Role on this RAID 1. This works just fine. Then I configured the LSI-Raid-Controller with additional 6x "Raid 0 Drive Groups" where each Drive Group has one single physical drive
in it. And then I created 6 virtual drives out of these 6 Drive Groups. So far so good: my Windows Server 2012 R2 now sees 6 new Harddrives (4x 600GB HDD and 2x 256GB SSD). I then created a Storage Pool out of these 6 drives (with PowerShell /
assign MediaType SSD/HDD) and on top of the Storage Pool a "Tiered Storage Space" with Mirror Layout (2x 256GB SSDs mirrored and 2x2x 600GBs HDD mirrored). This gives me a Tiered Storage Space of about 1.3TB. On this Storage
Space I created a Virtual Drive of 1.3TB capacity. Success!! It seems to work fine.... Even I do not have a Storage-Controller supporting JBOD directly, I was able to create a Tiered Storage Space!!
Now where's the problem? Fine-Tuning the LSI-Raid-Controller Settings and the resulting
Disk Performance....
1) LSI-Raid-Controller: Virtual Drive Properties: What should I choose? Read Policy (Ahead or no) / Write Policy (Write Back with BBU or Write Through) / IO Policy (Direct IO or cached IO) / Disk Cache Policy (enable or disabled or unchanged)
/ Stripe Size (256 KB or ??). Do these settings conflict with the Windows Server Storage Space Layout?
2) Windows Server Disk Management (under "Disk XY"): Write Cache Policy? (activate Write Cache on this Device)
3) Windows Server Device Manager (under "Drives" - Microsoft Storage Space Device): Write Cache Policy? (activate Write Cache on this Device)
4) Performance - Results with Crystal Disk Mark: the inital Results after setting up the Storage were quite good (Seq R: 550 MB/s and W: 590 MB/s // 512K R: 490MB/s and W: 618 MB/s // 4K R: 18MB/s and W: 37 MB/s // 4KQD32
R:270 MB/s and W:37 MB/S) But 2 months later the values dropped to: Seq R: 290 MB/s and W: 170 MB/s // 512K R: 120MB/s and W: 239 MB/s // 4K R: 1.5MB/s and W: 31 MB/s // 4KQD32 R: 9 MB/s and W: 71 MB/S). Huge loss of performance
- SSD full?
5) Since this is a Hyper-V Server I put some VMs on it. The Performance within the VMs has also dropped accordingly. Are there any
best practices when placing VHDX-Files on a Tired Storage Space? I could of course assign one or two VHDX-Files directly to the SSD Tier, but actually I don't want that because that would use too much SSD-Space.
Any Experts on this Subject?
Mark

Hi Mark,
For the settings of the Raid Controller, it is better to confirm with manufacturer for detailed information. As you said these settings will affect with storage space settings.
From the description you set the 6 disks as 6 RAID0 groups. Is it supported to leave these disks as JBOD and directly add them into a storage space? If Raid settings will affect storage space performance, this could help us avoiding the RAID settings.
As data is already written onto the virtual disk, we may not available to recreate it. You could have a try with following PowerShell cmdlet to see if it will work better after optimize.
Optimize-Volume -DriveLetter X -TierOptimize
If you have any feedback on our support, please send to [email protected]

Brand New RD240 ThinkServer can not see the LSI 8708EM2 RAID Controller During Bootup

I have a brand new out the box RD240 ThinkServer that can not see the LSI 8708EM2 RAD Controller it came with. This RAID controller simply does not want to function. This RAID Cntroller does not show up during the boot up and I even tried putting in a different slot in the riser card, thinkn maybe it was a bad PCI-e slot, but made no difference. Also the Lenovo Easy Setup software does not find this controller either. So I'm wondering if there is an issue with the RAID Controller or is it a bad Riser card? Does anyone have any idea's on what can be done or what I may be missing?

For a list of Warranty Support contact numbers, please visit:
http://support.lenovo.com/en_US/feedback/detail.page?LegacyDocID=MIGR-76613
In the U.S. you can call: 1-800-426-7378

Second IDE Raid controller

I have MSI K7T 266 Pro 2 RU board, onboard raid, i want to install second raid controller card. I cant get into a bios of second card. Second card is CMD PCI - 0649 Ultra 100 Raid controller.
If the a problems when running two raid controllers in one system?
And how can i get into the bios of second raid card.
P.S. card is installed in Windows XP fine. i can see two hard drives connected to it. Right after raid bios on onboard raid it looks windows.
Please help
Thanks

Quote
Originally posted by pcman12345
My pc boots of onboard raid. (2) 40gig drives. What do new drivers have to do with getting into bios of pci raid card. I have all the latest drivers anyway.
Any other ideas?
Thanks for your help.
It sounds like you are booting from the promise RAID controller. If so, you are well familiar with the way in which it dominates the bootup process for the first 30 seconds or so.........(dots look familiar?...)
I wonder if the second RAID card is also initiating its bios sequence at the same time underneath the Promise boot screen (underneath, so to speak) so that when the Promise routine is finished, so is the CMD routine, and you proceed from that point with both RAID controllers initialized (but can only see one of them at a time from the bios screen.)
Do you you have "boot from other device" enabled in the bios? If so you might try disabling that to see if it will sequence the RAID controllers initialization so that the CMD bios appears after the Promise bios is done (I assume you have the onboard Promise array selected as the boot device.)
A bit more trouble would be to reboot to main bios, disable the onboard RAID controller in the bios, save and reboot. At this point the Promise bios will not display and you should see a CMD bios display which you could manipulate--then reenable the Promise controller to boot, etc. If you disable the Promise controller and you still don't see a bios for the CMD RAID device you need to look elsewhere. Also, it might be that the CMD bios access requires a certain key sequence pressed during post to display?....Just some random thoughts...

K8N Neo2 + NVRAID + Promise Raid Controller = not working right

I'm trying to get my Promise Raid card working with nvraid enabled and I've finally given up. It works fine with NVRAID disabled though. I have 2xSata on Raid 0 and 2xIDE on raid 0+1. i also have two other IDE's on non-raid and two atapi cdrom drives. In order for me to use all of my storage devices, i need the promise controller to boot. The Prommise RAID controller's BIOS will not boot with nvraid enabled. WindowsXP detects the drives, but if i try to mount them via PAM (Promise Arry Management), it says one of the drives is corrupt/not working. but if i have both the ide raid hd's on the nvraid w/ sata raid, then it works fine. I just won't be able to use my cdrom drives. if anyone has a fix for this, please let me know. and sorry for the long descriptions. thanks.

Why don't you go into BIOS and alter the IRQ manually for that PCI card, because probably that card is using the same IRQ as the nVidia one.
Be well....

Cannot boot with Perc /2 raid controller

Similar Messages

Maybe you are looking for