No raid option during boot up

there is no option for me to access my raid options, during the boot up there should be a option but there is not one, system specs.
2.4c
865 neo2 fis2r
hyperx 3500
fx 5900
2x wd raptors

There are two responses to your previous post. See your previous thread.
One response is as follows:
No options for RAID in the BIOS. RAID is managed via external BIOS; in my case, you access this by hitting CONTROL-F on startup. This works for the promise BIOS, but you also have the option of using the ICHR5 and it will have a different BIOS. See the supplementary manuals which came with the computer.
Also, in the integrated peripherals section of the BIOS, enable the SATA. I suspect you have to enable the SATA drives for both the Promise Controller and the ICHR5. Note also if you ever plan to boot off the RAID drive, you'll have to set this up in the "Advanced BIOS Features" section of the BIOS.
Good luck.
Scott
Also, please ensure the RAID drivers are installed! These come on one of your system disks with the motherboard. These install separate BIOS' configuration utilities which manage the RAID options.

Similar Messages

P7N Diamond, unable to access RAID Config during Boot

I've got a P7N Diamond motherboard, with 6 disks attached, one SSD (boot) and I recently installed 5 1.5TB disks as well. These I would like to run in RAID 5 mode. I've enabled RAID for those channels in the BIOS, but I am unable to access the RAID config that's supposed to be available during bootup. The system also has an ADAPTEC RAID 1430SA ROHS SINGLE PCI-E LP 4-PORT controller with two disks attached, could this be messing things up? (I DO get an option to access this RAID config, but it fails claiming too little free memory (!) (It's a system with 4GB installed)) In Windows 7, the 5 disks shows up in the NV Raid as "Free disks", but I'm not able to do anything with them except setting SMART info. In the Windows Disk management they don't show up at all.
So, anyone got any ideas on how to access the raid config (F10) during boot?
All suggestions appreciated
Thanks,
Zem

The error regarding "too little free memory" isn't related to system RAM but to bios ROM address space. As already stated, the Adaptec card is causing the conflict with the NV RAID controller bios. This is actually a very common issue when trying to run multiple disk controllers in a single system and isn't any fault of the mobo. There's only so much addressable space for BIOS to reside in.
You may be able to free up some address space by disabling the LAN Option (boot) ROM in CMOS and setting the JMicron controller to IDE instead of RAID. Even better would be to disable the JMicron controller entirely.
If, after doing so, the Adaptec controller is still not able to work with the NV controller in RAID mode, then I'm afraid you're out of luck.

Macbook Pro 17" restarting during boot screen

This seems to be an on going problem for people. From the threads I've read I could not get a solution.
My Macbook is turing on and plating the chime, but the screen has been covered in loads of square patches of purple dots. The Apple logo appears on the grey screen and the wheel starts to turn. What happens is it will do this for a minute or so and then freeze or more often restart and do the same thing again until i force it to turn off.
I have tried all of the below already
     - Safe Mode (fails and restarts)
     - Single user mode (disk repair command as I could not do it through the graphical interface)
     - Reset using cmd+option+r+p
     - Recovery by holding Option during boot (again freezes or restarts)
I would use a disc to a reinstall but my optical drive is broken and I do not have access to an external one. I realise I can use a Bootable USB but I only have access to a Windows for the time being. Its probably worth mentioning that was watching a video on Youtube when the whole laptop froze and starting repeating and jerking and then shut down. It has not worked since!
Can anyone suggest any other posible solutions please?
Thank you

My Macbook is turing on and plating the chime, but the screen has been
covered in loads of square patches of purple dots. The Apple logo
appears on the grey screen and the wheel starts to turn. What happens is
it will do this for a minute or so and then freeze or more often
restart and do the same thing again until i force it to turn off.
This seems like a hardware issue.
All we can suggest is run a #3 Hardware Test, write down what it says and take it into Apple for a free eval.
..Step by Step to fix your Mac
5 year old machine? I'd say it's the video card going because the cooling fins behind the fans haven't been cleaned, heat damage is irreversible.
Not worth fixing, buy a new machine.
You can extract the drive and use a SATA to USB adatpter and Migration Assistant to a new Mac.
My computer is not working, is my personal data lost?

F11 R&R option at boot time

Evening,
I have just purchased an IdeaPad S10 4333-36U. I saw that it came with Windows XP Home. So i did a clean format on the windows parition and installed Windows XP Professional.
Please note that i left the recovery parition intact. When doing the above process. So now i have my windows XP professional parition and my recovery parition "SERVICEV002" on the netbook.
Before i installed WXP Professional i noticed that whenever the machine booted that after the quick luanch, at the top i would see a message saying "To boot to the Rescue and Recovery Environment, Press F11".
Since installing WXP Professional I no longer get this option during boot up. Instead it goes straight in to Windows. As said prevoiusly my recovery partition is still un touched on the system.
Could anyone tell me how i can make this message F11 boot to recovery message come back during boot time?
Any assistance with this would be most appreciative.
Regards,
Andrea

CCC is used to make a bootable clone. It will also make an image file that can be installed using ASR or that can be used with NetBoot. It does not make a bootable image because you cannot boot from a disk image file. The image file can also be burned onto a CD or DVD, but you will not be able to boot from it because a CD/DVD is not a writeable device, and OS X must be able to write to a startup device.
Another utility, BootCD (not yet usable with Tiger), worked around the problem by rewriting some of the startup code in OS X to force the making of a RAM disk, then moving some of the startup files to the RAM disk and designating the RAM disk as the startup device. Although BootCD will make a bootable and customizable CD using Panther, it does not work with Tiger.
Any questions?

VIA Raid 0: Red screen of Death - fatal error during boot sequence

I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB. I have occasionally had messages saying "Hard disk error. Can't find drive 0". I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up). However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising. The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued. Naturally I switched off at this point, but on rebooting got exactly the same message. Eventually, as I have backups, I continued past this point and sure enough the RAID had gone. So I rebuilt the raid array and everything seems to be OK.
However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups. BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
Has anyone else had this RAID erro. Is it a driver error or is it a dsik failing (even though they were new at Christmas).
I am using a Superflower power supply which has 22A on the 12V rail
1GB PC3200 ram by A-Data (CAS 2.5)
Elderly HP 9100 CDRW
MSI DR-8 DVD RW
Ethernet card
Radeon 9600 128MB
AMD64 3000 processor
Freeflow

Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

Heres the problem...
My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
No phsysical signs of bad caps on the system board.
I ran ran Memtest86 for 18 hours striaght with no errors.
Ran CPU stress test with no problems.
No IRQ,DMA,etc conflicts found.
Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
I have tried min install to no avail.
Bois is retaining its settings (so bios battery is good)
I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
I am down to a possible cold solder joint on the system board?
This problem started to occur about a month ago.
If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge
I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
Specs..
Athlon 64 3500+
2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB) Ran in Dual config
Geforce 6800 (BFG 6800 GT oc)
Creative X-Fi XtremeMusic
Antec NeoPower 480
2 WD 36gig SATA Raptors in raid 0 (system partition)
2 WD 120gig IDE in raid 0 (data partition)
Windows XP Pro
all drivers and bios are manufacture ref and up-to-date.
Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
So what have we learned class?
1. check the obvious
2. do a complete physical inspection of your system
3. KISS -- keep it simple stupid

Is this your ram:
Quote
Part Number: PQI3200-1024SB
Quality Control: Comprehensively and rigorously tested
Package: 1024MB single pack
Organization: 128M x 64-bit
CAS Latency: 3-4-4-8
Test Voltage: 2.6 V
PCB Board: 8 Layers PCB
Heat Spreader: Mirrored Black Copper
Speed: DDR 400 MHz (PC3200)
Type: 184-pin DDR SDRAM
Error Checking: Non-ECC
Registered/Unbuffered: Unbuffered
Warranty: Lifetime
This is a quote from MSI web site:
Quote
Main Memory
• Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
• Supports the memory size up to 4GB
• Supports 2.5v DDR SDRAM DIMM
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
Post back results as there are more things one can try but lets start with the simple stuff and work up.

Eth0 is being up and down for several time during boot

My wicd doesn't connect to eth0 on the first attempt after boot up. It is configured to eth0 always have a higher priority to connect.
My dmesg shows that eth0 being up and down for several time during boot. I have e1000e in my MODULES list.
Here is my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK=""
TIMEZONE="Asia/Hong_Kong"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MOD_AUTOLOAD="yes"
MODULES=(acpi-cpufreq fuse tp_smapi vboxdrv e1000e)
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="antony-tp"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="yes"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(!hwclock syslog-ng dbus !network !dhcpcd rpcbind acpid @wicd nfs-common netfs @crond cups @laptop-mode @alsa @sensors ntpd @slim bluetooth)
Here is a segment of my dmesg
[ 2.759302] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
[ 2.759304] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 2.759338] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 2.759348] e1000e 0000:00:19.0: setting latency timer to 64
[ 2.759467] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 2.766107] tpm_tis 00:0a: 1.2 TPM (device-id 0x0, rev-id 78)
[ 2.766808] ACPI: AC Adapter [AC] (on-line)
[ 2.776492] wmi: Mapper loaded
[ 2.777212] mei: module is from the staging directory, the quality is unknown, you have been warned.
[ 2.777781] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.777783] ACPI: Thermal Zone [THM0] (66 C)
[ 2.778291] iTCO_vendor_support: vendor-support=0
[ 2.780137] ACPI: Battery Slot [BAT0] (battery present)
[ 2.780958] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 2.781462] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[ 2.781547] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
[ 2.781919] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.783139] cfg80211: Calling CRDA to update world regulatory domain
[ 2.789182] [drm] Initialized drm 1.1.0 20060810
[ 2.789538] hub 4-1:1.0: USB hub found
[ 2.789616] hub 4-1:1.0: 8 ports detected
[ 2.792925] Non-volatile memory driver v1.3
[ 2.795877] thinkpad_acpi: ThinkPad ACPI Extras v0.24
[ 2.795879] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 2.795881] thinkpad_acpi: ThinkPad BIOS 8DET54WW (1.24 ), EC unknown
[ 2.795882] thinkpad_acpi: Lenovo ThinkPad X220, model 4290NL5
[ 2.797236] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[ 2.797352] thinkpad_acpi: radio switch found; radios are enabled
[ 2.797466] thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
[ 2.799752] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 2.800067] Registered led device: tpacpi::thinklight
[ 2.800091] Registered led device: tpacpi::power
[ 2.800106] Registered led device: tpacpi::standby
[ 2.800120] Registered led device: tpacpi::thinkvantage
[ 2.800192] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 2.800254] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[ 2.801077] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
[ 2.801162] sdhci: Secure Digital Host Controller Interface driver
[ 2.801164] sdhci: Copyright(c) Pierre Ossman
[ 2.801707] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 2.801709] Copyright(c) 2003-2011 Intel Corporation
[ 2.801744] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2.801753] iwlwifi 0000:03:00.0: setting latency timer to 64
[ 2.801789] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[ 2.801791] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90005abc000
[ 2.801793] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
[ 2.801877] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
[ 2.801913] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
[ 2.801962] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 2.802045] sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e822] (rev 7)
[ 2.802067] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.802107] sdhci-pci 0000:0d:00.0: setting latency timer to 64
[ 2.802118] _regulator_get: 0000:0d:00.0 supply vmmc not found, using dummy regulator
[ 2.802188] Registered led device: mmc0::
[ 2.803329] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA
[ 2.815226] iwlwifi 0000:03:00.0: device EEPROM VER=0x715, CALIB=0x6
[ 2.815229] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
[ 2.815231] iwlwifi 0000:03:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
[ 2.815247] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 2.845674] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
[ 2.845820] Registered led device: phy0-led
[ 2.850630] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 2.862431] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
[ 2.943648] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:92:77:26
[ 2.943651] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 2.943712] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
[ 2.943734] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.943739] mei 0000:00:16.0: setting latency timer to 64
[ 2.943817] mei 0000:00:16.0: irq 50 for MSI/MSI-X
[ 2.944502] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
[ 2.945021] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[ 2.946341] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
[ 2.946452] watchdog: error registering /dev/watchdog (err=-16).
[ 2.946523] mei: unable to register watchdog device.
[ 2.946598] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
[ 2.946692] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
[ 2.946734] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 2.948359] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 2.948422] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
[ 2.948444] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[ 3.022245] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
[ 3.172080] usb 1-1.4: new full-speed USB device number 5 using ehci_hcd
[ 3.274597] Bluetooth: Core ver 2.16
[ 3.274611] NET: Registered protocol family 31
[ 3.274612] Bluetooth: HCI device and connection manager initialized
[ 3.274614] Bluetooth: HCI socket layer initialized
[ 3.274614] Bluetooth: L2CAP socket layer initialized
[ 3.274618] Bluetooth: SCO socket layer initialized
[ 3.275535] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 3.276006] usbcore: registered new interface driver btusb
[ 3.338454] usb 1-1.6: new high-speed USB device number 6 using ehci_hcd
[ 3.444567] Linux media interface: v0.10
[ 3.447387] Linux video capture interface: v2.00
[ 3.448573] input: Logitech Trackball as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
[ 3.448671] generic-usb 0003:046D:C404.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1a.0-1.2/input0
[ 3.448690] usbcore: registered new interface driver usbhid
[ 3.448691] usbhid: USB HID core driver
[ 3.449136] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217)
[ 3.450945] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7
[ 3.450987] usbcore: registered new interface driver uvcvideo
[ 3.450988] USB Video Class driver (1.1.1)
[ 3.484049] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
[ 3.491137] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[ 3.491298] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[ 3.491486] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0
[ 3.491637] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 3.491709] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 3.491765] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 3.492050] i915 0000:00:02.0: power state changed by ACPI to D0
[ 3.492053] i915 0000:00:02.0: power state changed by ACPI to D0
[ 3.492059] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.492062] i915 0000:00:02.0: setting latency timer to 64
[ 3.538056] mtrr: no more MTRRs available
[ 3.538058] [drm] MTRR allocation failed. Graphics performance may suffer.
[ 3.538266] i915 0000:00:02.0: irq 52 for MSI/MSI-X
[ 3.538270] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 3.538271] [drm] Driver supports precise vblank timestamp query.
[ 3.538292] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 3.664501] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
[ 3.664518] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 3.716317] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12
[ 4.407165] fbcon: inteldrmfb (fb0) is primary device
[ 4.575259] Console: switching to colour frame buffer device 170x48
[ 4.577042] fb0: inteldrmfb frame buffer device
[ 4.577043] drm: registered panic notifier
[ 4.607860] acpi device:01: registered as cooling_device4
[ 4.607985] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13
[ 4.608039] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 4.608122] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 4.757243] EXT4-fs (sda3): re-mounted. Opts: discard
[ 4.765917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard
[ 4.776777] Adding 262140k swap on /dev/sda2. Priority:-1 extents:1 across:262140k SS
[ 5.099467] NET: Registered protocol family 10
[ 6.048650] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.098038] Bluetooth: RFCOMM TTY layer initialized
[ 6.098055] Bluetooth: RFCOMM socket layer initialized
[ 6.098057] Bluetooth: RFCOMM ver 1.11
[ 6.278766] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 6.278893] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 6.568639] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 6.568775] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 6.684082] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7.176563] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 7.226662] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 7.227110] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.229345] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 10.490618] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
[ 10.817814] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 10.819315] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 11.186166] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 11.186292] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 11.313367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 11.665342] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 11.717591] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 11.718042] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.964795] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 12.017213] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 12.017720] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.811264] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
[ 13.826031] EXT4-fs (sda4): re-mounted. Opts: discard,commit=0
[ 15.178905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 15.180472] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 25.663056] eth0: no IPv6 routers present
Any hint for tracing the root of this problem? Thank you very much!

Hi ...
If you have moved the Safari application from the Applications folder, move it back.
As far as the cache goes, there's a work around for that when you can't empty the Safari cache from the menu bar.
Go to ~/Library/Caches/com.aple.Safari.Cache.db. Move the Cache.db file to the Trash.
Try Safari.
Mac OS X (10.7.2) < from your profile
If that is corrrect, you need to update your system software. Click your Apple menu icon top left in your screen. From the drop down menu click Software
Update ...
~ (Tilde) character represents the Home folder.
For Lion v10.7x: To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

Macbook Pro Lion shuts off during boot up

I have a 13" MacBook Pro purchased in 2011. I had the internet lock up on me and hard shut down the computer. Now when I press the power button, the machine begins to boot up and the apple pops up then the progress bar pops up and the wheels starts to spin, but the machine shuts down about 5 seconds into it.
I have seen this problem on older posts (pre-Lion) and one solution was to hold option during start-up and then boot off th esystem restore disc, but Lion is all internet based, so no disc here. When I do that, it pops the option to select an internet source, which I do, then the HD symbol pops up with an arrow below it. When I clikc the arrow (which is the only apparent option) it does the same thing and shhuts off at the same point.
HELP!

Try booting with command-R. This will boot into the repair parttion. From here you can run disk utility and other programs. You can also do a repair installation of Lion which will almost certainly solve the problem. Doing so shouldn't wipe out your user data, but installing OS updates will be required.

Why no RAID options for new disks?

Hi support group,
"My name is Shaun, and I am a mac-aholic"
I inserted 4 new 3TB disks into the bays of my Mac Pro (2012), and there is no RAID option for them.
How I got here:
Inserted the WD Red drives, and they were not initiated.
I "erased" the drives, gave them names, and they appear in Disk Utility in grey drives.
Went to set up the RAID, and move the drives into the RAID, but got an error that they could not be used.
It appears to me that disk utility is not allowing me to fully use those drives. I Have created RAID drives before with no issue in RAID1 with 3TB drives before on this machine. Am perplexed, I thought this to be the easy and simple part of my upgrade odyssey! Did I screw up the initialization? On all FOUR drives?
Now, if I click on the drives, the RAID option does not present itself.
FWIW, I am using OS X 10.9.5, on Mac Pro 5,1. I boot from PCIe card. My end goal is to create a 4-disk RAID 10 using the four SATA connections on the MP.

It was really pretty simple based on your feedback, I powered down, removed the drives from the SATA backplane, moved each drive separately to the USB enclosure, then re-"erased" in OSX-Etended. I ejected each drive when finished, and moved to the next one until all four were re-"erased". Then I restarted the Mac with all four in the SATA connections, and all four were visible and had the RAID option tab. I created the three RAID schemes (two stripe and one mirror), and dragged the drives into the RAID option. Then I hit "create" or some other command to finish the RAID.
Note that I did get an error on the RAID creation. From memory, this was "cannot create RAID without an unmounted disk" or something like that. I cleared the error, and then opened back up Disk Utility. All the RAIDs were listed, and were operational with the green "On" signal. I could read/write/transfer from the RAID. Once I transfer the data to this RAID, I will work on a way to test it, but if any risk to the data, I might just leave well enough alone.
For now, it seems I have a fully functional RAID 1+0 using the four HDD on the SATA connections in my Mac Pro 5,1.

I have a Mac Pro with four hard drives. I currently have Lion installed on one hard drive. I want to have the option to boot from either Lion or Snow Leopard. How can I do this?

I have a Mac Pro with four hard drives. I currently have Lion installed on one hard drive. I want to have the option to boot from either Lion or Snow Leopard. How can I do this?

It's best to install Snow Leopard on one of the three remain drives without an Operating System.
You can then install the applications you need from the original media. Create a User Account using Setup Assistant.
Do you want to migrate User Accounts from the OSX LIon boot drive, or are you keeping the User Accounts separate?
Dual-booting just requires holding the option key during startup and selecting either Lion or Snow Leopard.

I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2011 MBP upgraded to Mavericks.

hello,
And thank you in advance.
I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 20011 MBP upgraded to OS X 10.9 Mavericks. Any ideas?
I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive. I tried to create an iso image from my Windows XP machine but recieved messages that Windows 8.1 could not run on XP. I've ordered the Windows 8.1 backup media.
Any way to proceed?
Thanks Tim

download the win 8 iso from here;
http://getintopc.com/softwares/operating-systems/download-windows-8-pro/
then start over. install on to your usb along with the support software.

Installer disk not found message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks?

I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks. Any ideas?
I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive.
Thanks Tim

You might have better luck in the Boot Camp community. I'll ask the hosts to relocate your post.
Boot Camp Community

[915 Series] Why is there no RAID option?

Hi
mainboard is MS 7058 V1.0
type of mobo is 915p/g combo
it has full options, it has three IDE and four SATA connectors on board.
Bios was 1.4, and some time ago I updated to 1.7
it ran off a SATA 160 Gigabyte drive in enhanced IDE configuration
today, I pulled the drive, and fixed four identical 300 giga Sata drives because I want to run a striped mirrored RAID.
but... when I look at the available options, the BIOS setup screens do not ever show a RAID option at ALL.
I could connect an IDE drive, and see wether that will then allow me to install a RAID, but I really want to boot from RAID.
I also have an azalia question, but this can wait... the burning question right now is this..
kind regards, Jaak

Hi
hey, Thanks... Sorry if I be late to reply.
looks like default forum option is no not have email notification ON...
gonna look for this, if available.
F6 and driver on floppy, when I go for it and launch the setup on blanco SATA drives for a stipe/mirror without any PATA drives present at all, will that work?
I could still try this, even after I moved the mobo to a smaller case so as to get rid of it.
what I saw is that in BIOS, it does not show any of the raid options.
Is that floppy gonna install something in preboot, or in MBR of first active (if no option can be taken in BIOS, how so?)
r, or in EMBR of first active?
long time ago I did do some raid in real SCSI, and them things had an active bootrom in scsi raid setup, what is what I do not see...
now, maybe, MAYBE, one can set this up as a disttributed volume in windows, but will it do stripe/MIRROR?
I am skeptical.
yet... what have I got to lose, eh?
If ya really think a striped mirrored SATA RAID can be done n my mobo, I am willing to get me another (BIG/GER) case with an azalia front connector... and try it out.

Change Seconds Waiting for Device during boot

During boot at the section: "Waiting 10 Seconds for Device", I am often dropped to a shell. I think it may be because I need to increase the wait time. How can I do this? I've looked in several places but I'm not sure what to look for.

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

[solved]How to unlock LUKS using keyfile on usbdrive during boot?

Hi all,
I would like some advise for booting encrypted partitions using kefiles on a flashdrive. I'm setting up a Intel Atom based homeserver, and and want my data to be encrypted in case the server gets stolen. To save some encryption overhead I prefer to leave root unencrypted and only encrypt /home, and if this works, later on /var, /tmp and swap as well. My plan is to have a keyfile on a flash thumbdrive, and only have the thumbdrive plugged in while booting.
I have read the dm-crypt wiki page, but it assumes an encrypted root, and this approach won't work in my situation, where only non-root mountpoints are encrypted. If i put 'ASK' in /etc/crypttab I get prompted for the passphrase and the LUKS container unlocks and mounts fine. I can also unlock the LUKS container manually using the keyfile that I created. However when I put the path to the keyfile in /etc/crypttab instead of 'ASK', and let the usbdrive automount using an udev rule the unlock at boot fails. It seems that my udev rule is only executed when I plug in a drive after booting, not when it is already plugged in during boot. How would I accomplish this? Mount it with fstab and automatically unmount it after booting, or some entirely different way?
my /etc/fstab:
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sda1 / ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/mapper/home /home ext4 defaults 0 1
/etc/crypttab:
home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_home.key
/etc/udev/rules.d/01.usbdrive_automount.rules (sdb is a second, currently unused harddisk):
KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
<edit>
Okay I have found a solution. The trick was to make sure the usbstick gets mounted first, so the keyfile is available for the unlocking/mounting during boot. To do so I have added 'usb' to the hooks line in /etc/mkinitcpio.conf and recompiled the initramfs as described in the wiki link above.
Next I changed my /etc/udev/rules.d/01.usbdrive_automount.rules a little so that the mountpoint of the usbdrive stays after unplugging it:
KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k", OPTIONS="last_rule"
#ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
#ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
/etc/fstab:
The usbdrive is put above the encrypted partition to make it get mounted first:
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sdc1 /media/usbhd-sdc1 ext2 defaults 0 0
/dev/sda1 / ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/mapper/home /home ext4 defaults 0 1
/etc/crypttab:
home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_luks.key
So now I plug in the flashdrive, turn on the server, unplug the flashdrive and udev automatically unmounts the flashdrive while leaving the mountpoint /media/usbhd-sdc1 for the next boot.
</edit>
Last edited by rwd (2009-12-04 19:36:14)

graysky wrote:@ratcheer - You can try now if it's a major pain in the balls by enabling [testing] and using the updated linux package.
If you do enable testing make sure you aren't like myself: I'm not competent enough to enable testing..
Edit:
To elaborate a bit. If you enable testing and then just do a "pacman -Syu" then you are going to pull in all sorts of packages you may not want and it may be complicated to get rid of later. To avoid this I would enable testing, do this:
sudo pacman -Syy
sudo pacman -S testing/linux
So it would pull in the absolute minimum that I wanted from testing. Then I would disable the testing repository and pacman -Syy again. That would convert the new linux package and packages it requires to manual packages. E.g. they would be shown under "pacman -Qm"
Because once you start pulling packages in from testing it is almost a one-way street. As I instructed above, that is my gross understanding. I don't use testing at all, it is supposed to be used if you are actively testing Arch and providing feedback while doing so.
Last edited by headkase (2012-10-03 01:51:51)

No raid option during boot up

Similar Messages

Maybe you are looking for