[SOLVED] UEFI Virtualbox installation boot problems

Before I install Arch on my computer, I wanted to test the installation in Virtualbox. Because my motherboard has UEFI, I selected the EFI option in Virtualbox for a 64 bit Arch install.
I ran through the Beginners' Guide on the wiki and all seemed to go well. I rebooted the VM after the installation (forgetting to remove the ISO from the drive) and got the refind menu showing correctly and managed to boot in to my new Arch system from there. I also did a reboot (with the ISO still in the drive) and all was well. However, I then shutdown the system (shutdown -h now) and then powered it back on again and instead of going in to the refind menu, it goes to the archiso uefi boot menu and continues to boot from the ISO. So I powered down the VM again, removed the ISO from the drive and powered the VM back on again. This time, nothing booted and I was left in the UEFI shell.
Does anyone have any ideas why this has happened?
Last edited by ryan117 (2013-02-13 20:15:44)

This is probably because VirtualBox tends to forget its "NVRAM" settings when you reboot. There are a number of solutions to this problem. IMHO, the easiest is:
Boot using an emergency system.
Mount the ESP (probably /dev/sda1 -- the FAT partition that holds the boot loader).
Rename EFI/refind on the ESP to EFI/BOOT
Rename EFI/BOOT/refind_x64.efi to EFI/BOOT/bootx64.efi
Thereafter, rEFInd should appear when you reboot. If you subsequently upgrade rEFInd, you'll need to install it to its new location rather than to EFI/refind.
Alternatively, you can use the bcfg command in an EFI version 2 shell to register refind_x64.efi as the default boot program. This tends to get remembered, even when entries created by efibootmgr don't. This will require installing an EFI 2 shell, running it, and running the suitable bcfg command. (I think it's documented in the Arch wiki somewhere.)

Similar Messages

[SOLVED] CD Drive causing boot problems

I'm trying to install Arch, but booting the install disk causes these errors to come up:
Loading /arch/x86_64/vmlinuz.....
Loading /arch/x86_64/archiso.img.............ready.
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
: : Starting udevd...
done.
: : Running Hook [udev]
: : Triggering uevents...[ 19.934456] usb 5-1.6: device descriptor read/64, error -110
[ 35.098044] usb 5-1.6: device descriptor read/64, error -110
[ 36.869505] ata8.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[ 36.869549] ata8: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 36.869598] ata8.0: failed command: IDENTIFY PACKET DEVICE
[ 36.869639] ata8.0: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 36.869640] res 40/00:00:00:00:00/00:00:00:00:00 Emask 0x56 (ATA bus error)
[ 36.869721] ata 8.0: status: { DRDY }
It just stops there and won't continue to boot. Disconnecting the SATA cable from my CD drive and using a flash drive to boot fixes these issues, but I didn't continue with the install because I wasn't sure if I would be unable to boot with the drive plugged in later. This is my CD drive. It's connected to a SATA 6GB/s port on my motherboard. The drive works perfectly in Windows.
Also, if anyone knows anything about the USB error, help would be appreciated. That was the only error that did not go away after disconnecting my CD drive. I only have a keyboard, mouse, and WiFi dongle plugged in.
Last edited by nigh (2012-05-29 09:28:01)

Your issue with the SATA disc drive is a problem with Udev. Namely that some SATA disc drives do not support 16-byte pass-through commands coming from Udev. See this post for a longer explanation and the correct workaround:
https://bbs.archlinux.org/viewtopic.php?pid=895404
Other guides online will say to comment out parts of Udev's 60-persistent-storage.rules file, but I have found that to not only not work, but mess up detection of the SATA hard drives.
So, after, or during, Arch installation using your USB stick:
Add
options libata atapi_passthru16=0
to /etc/modprobe.d/modprobe.conf
Add
FILES="/etc/modprobe.d/modprobe.conf"
to /etc/mkinitcpio.conf
Rebuild kernel image with:
mkinitcpio -p linux
reboot
To narrow down your USB issue, maybe you could try booting with only one plugged in at a time to identify which one has the issue. Do they all three work even though one gives this message?

[SOLVED]Kernel 3.0 boot problems.

I recently built the 3.0 kernel (downloaded from kernel.org) and am trying to make it bootable.
After creating an image and editing grub, I get an error talking about how modules.dep was not found, that /dev/sda7 does not exist and can't be mounted to new_root, that I'm on my own and Good Luck, and then I get dropped to ram fs.
I listed the contents of the kernel26.img and kernel30.img and there is quite a difference even though they were both built using the same mkinitcpio.conf. kernel26.img was built with -p kernel26. I haven't found a preset for kernel30.
kernel26.img boots fine.
I think the .imgs need to be similar but I don't know how to make them similar. Or I could be completley wrong and on the wrong track. Any ideas?
kernel26.img listed:
/proc
/sys
/dev
/bin
/sbin
/lib
/usr
/usr/bin
/usr/lib
/usr/sbin
/run
/dev/null
/dev/zero
/dev/console
/dev/mem
/bin/busybox
/lib/libc.so.6
/lib/libc-2.13.so
/lib/ld-linux-x86-64.so.2
/lib/ld-2.13.so
/sbin/modprobe
/sbin/blkid
/lib/libblkid.so.1
/lib/libblkid.so.1.1.0
/lib/libuuid.so.1
/lib/libuuid.so.1.3.0
/init_functions
/init
/config
/etc
/etc/modprobe.d
/etc/modprobe.d/usb-load-ehci-first.conf
/sbin/udevd
/lib/librt.so.1
/lib/librt-2.13.so
/lib/libpthread.so.0
/lib/libpthread-2.13.so
/sbin/udevadm
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/50-firmware.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-storage.rules
/lib/udev/rules.d/80-drivers.rules
/lib/udev/firmware
/lib/udev/ata_id
/lib/udev/path_id
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/load-modules.sh
/etc/udev
/etc/udev/udev.conf
/hooks
/hooks/udev
/sbin/v86d
/etc/modprobe.d/uvesafb.conf
/lib/modules
/lib/modules/2.6.38-ARCH
/lib/modules/2.6.38-ARCH/kernel
/lib/modules/2.6.38-ARCH/kernel/drivers
/lib/modules/2.6.38-ARCH/kernel/drivers/connector
/lib/modules/2.6.38-ARCH/kernel/drivers/connector/cn.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/video
/lib/modules/2.6.38-ARCH/kernel/drivers/video/uvesafb.ko.gz
/hooks/v86d
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/cdrom
/lib/modules/2.6.38-ARCH/kernel/drivers/cdrom/cdrom.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sr_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/libata.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/libahci.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/ahci.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs
/lib/modules/2.6.38-ARCH/kernel/fs/mbcache.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs/jbd2
/lib/modules/2.6.38-ARCH/kernel/fs/jbd2/jbd2.ko.gz
/lib/modules/2.6.38-ARCH/kernel/lib
/lib/modules/2.6.38-ARCH/kernel/lib/crc16.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs/ext4
/lib/modules/2.6.38-ARCH/kernel/fs/ext4/ext4.ko.gz
/lib/modules/2.6.38-ARCH/modules.dep
/lib/modules/2.6.38-ARCH/modules.alias
/lib/modules/2.6.38-ARCH/modules.symbols
kernel30.img :
/proc
/sys
/dev
/bin
/sbin
/lib
/usr
/usr/bin
/usr/lib
/usr/sbin
/run
/dev/null
/dev/zero
/dev/console
/dev/mem
/bin/busybox
/lib/libc.so.6
/lib/libc-2.13.so
/lib/ld-linux-x86-64.so.2
/lib/ld-2.13.so
/sbin/modprobe
/sbin/blkid
/lib/libblkid.so.1
/lib/libblkid.so.1.1.0
/lib/libuuid.so.1
/lib/libuuid.so.1.3.0
/init_functions
/init
/config
/etc
/etc/modprobe.d
/etc/modprobe.d/usb-load-ehci-first.conf
/sbin/udevd
/lib/librt.so.1
/lib/librt-2.13.so
/lib/libpthread.so.0
/lib/libpthread-2.13.so
/sbin/udevadm
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/50-firmware.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-storage.rules
/lib/udev/rules.d/80-drivers.rules
/lib/udev/firmware
/lib/udev/ata_id
/lib/udev/path_id
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/load-modules.sh
/etc/udev
/etc/udev/udev.conf
/hooks
/hooks/udev
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, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy 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 anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/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 an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev v86d autodetect pata scsi sata filesystems"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Last edited by bsilvereagle (2011-07-27 23:29:25)

bsilvereagle wrote:
karol wrote:
bsilvereagle wrote:Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.
linux 3.0 is just the next version of the kernel26, and we don't have versioned kernel yet https://bugs.archlinux.org/task/16702
It's just the same as you uninstall foo-1.2.3 and install e.g. foo-1.2.4 or bar-1.0.0 if package foo gets replaced by package bar.
I know, I'd just like to be able to boot .38-ARCH and 3.0. I have problems w/ thermal and I'm trying to find the coolest kernel.
You could rebuild the original .38 arch kernel but name it differently, look at e.g. the kernel26-lts package or the lots of custom AUR kernels for references.

Lenovo laptop u430 Touch - strange UEFI boot problem

Hello!! I'm Javier from Argentina. I'm having a strange boot problem with my Lenovo u430 Touch and Windows 8.1 x64 configured in UEFI.
When I power on o restart the laptop It gets stuck at lenovo logo screen and i have to press a key from the keyboard to continue booting on Windows 8.1 x64. This is really annoying.
No hdd activity.Trying to solve the problem I reset bios to default settings, I updated to last bios available and restored Windows 8.1 with OKR but i have no luck.
To solve this problem I configured the laptop to use legacy support, but I would that someone can help me to use again my laptop with UEFI bios settings.
Thanks, I will appreciate your help.Javier

Hi Sendhil,
Welcome to Lenovo Community Forums!
I'm sorry to hear about your situation. I have private messaged you the details. Please let me know after checking your PM inbox.
Do post us back for further queries.
Best Regards
Shiva Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

How do i solve the silverlight installation problems

How do I solve the Sliverlight installation issues on my new Macbook pro?

What exactly is the installation issue?
Uninstall Silverlight: https://www.microsoft.com/getsilverlight/get-started/install/removing-silverligh t-mac.aspx
Reinstall Silverlight: https://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx
Sometimes you may need to repair permissions and users permissions on the machine.
See #6 and #11 here
..Step by Step to fix your Mac
If your having trouble with the installation process, it's sort of the same procedure to install Flash
How to install/uninstall Flash, fix problems
Installing software from the web is a bit more difficult than from AppStore.
Microsoft Silverlight should be approved through Gatekeeper, so having to control or right click on the installer to select "Open" to bypass Gatekeeper shouldn't be required.
If this is occuring, like it's saying this app can't be installed as it's not from MacAppStore or a Apple Identified Developer, then it's likely not the real Silverlight but a trojan malware.
Please use the links I've provided to install Silverlight as they are direct to Microsoft.

[SOLVED]GRUB Dual-boot problem

Hey guys, I need some help since I haven't had any issues with GRUB until now. I've read the GRUB page on the wiki and several other sites, but I'm still not sure which method I should use.
Anyway, everything was fine yesterday, I could boot into both my Windows and Arch. Then for some reason today, I tried booting into Windows, but stated BOOTMGR is missing, press CTRL+ALT+DEL to restart. So I tried booting into Arch, which was fine. So I used the Windows CD and then used Startup Repair to fix Windows, but unfortunately it didn't work. I then typed bootrec /fixmbr (which was typed impulsively, since I use that whenever I uninstall Linux). Anyway, that makes Windows overwrite to the MBR, so after booting my laptop it goes straight to Windows.
So I was wondering whether to use the method where you have to use chroot, the method you can just use grub> find /grub/stage1 and install to MBR, or just run through the Arch install CD and skip everything except installing the bootloader and rebooting.
Replies are appreciated, thanks in advance.
EDIT: Solved it. I booted in the Arch Linux install CD and followed the instructions on the wiki. I switched to the grub shell and used
grub> find /grub/stage1
for use in root. It displayed (hd0,6), so I then used
grub> root (hd0,6)
. Lastly I used
grub> setup (hd0)
to install GRUB to the MBR. It works perfectly again.
Last edited by Reki (2011-11-27 14:31:23)

I know exactly what the problem is.
If you're using rEFIt, sync your partition tables (should be the menu item called 'Partitioning Tool'). The problem is that GRUB has been installed, but doesn't know where to find the Arch partition.
After syncing, you may find that the boot process hangs at the Linux logo on a gray background. No worries — just reboot and the problem should fix itself.
N.B. You will need to do a partition table sync every time you change your hard drive's layout.

Boot problems with K8N NEO Platinum(no video). SOLVED

I have this board for a few months now, but this week, when powering the system, it gave me no video.
It reads the HD and after a little while all the lights in the D-Bracket go green. But still no video.
There are other simptoms that can help the diagnosis: sometimes i do get video, the system powers up perfectly. This happens when I repeatedly press the reset button, or try powering on and off, on and off...
I don't think it is cold boot problem, since when I successfully turn on the system and then turn it off, the same boot problem occurs I I try turning it on again.
Another thing is that when I turn it off through Windows, it doesnt actually turn off: the screen ges black, but the HD leds still blink for a looong time. I have to turn it off manually, then. Sometimes it actually turns off, but turn itself on again after 1 second.
So if the D-Bracket sais its all good, then what is bad?
My System specs are
Athlon 64 Venice 3000
1 Gb Corsair DDR
Leadtek Geforce 6600GT

Quote from: cyberoll on 19-April-06, 19:18:18
Its solved now. There was a short circuit. The rouded isolators were placed in the upside of the board, and they should have been under the board. I changed it and all the problems are gone.
Such a little thing... :D
What is a "rouded isolator" and where is it located. I would like to see if this will fix my problem. The same thing is happening to me.
Thanks

1st series iMac G5: Booting problems, kernel panics, waking from sleep...

Specifications of the iMac described: 1.8 Ghz, 1GB, 80GB, 64 Mb Nvidia VRAM, Airport, 10.5.5
Back in August 2004 my dad bought us kids an iMac G5 for ‘family use’. It had a fresh install of 10.3.5 on it and compared to the (1999) iMac G3 it replaced it was amazingly fast.
The iMac never showed any signs of probable issues, until we decided to upgrade to Leopard in January 2008. Initially, this upgrade was only meant to be able to sync with the latest iPod nano (who demanded a newer version of iTunes).
After the installation the first thing I noticed was a high CPU usage, the machine seemed slower than ever and that with 1 Gb of RAM (the minimum sys. req. for Leopard are 512 Mb of RAM). Anyway, then the real thing started, it wouldn’t turn on anymore. We brought it to an Authorized Apple Reseller, the Tech department said the Logic board had failed. The costs of the fix weren’t the worth the computer anymore, so...end of story. The iMac was indeed one of the bad series, although it hadn’t any swollen capacitors.
My dad already made up his mind and bought himself a Macbook. He then told me that if I was able to get the broken iMac fixed, I could keep it. And so, I bought an ‘as-is’ logic board on Ebay. Last weekend I installed it, and it actually seemed to work! Yet, the problems are during the startup: the first thing I see is a screen full with horizontal lines flickering all the time, like an old TV with bad signal. Mostly it won’t boot and I get the message to restart the computer (kernel panic, I got dozens of logs already!). Sometimes it got stuck during booting (grey apple screen with gear in the middle) making the fans go crazy (after a while) and sounding what others describe as a ‘jetliner taking off’ sound. Sometimes the screen remains black. Generally it takes me 5 to 10 minutes to start up properly. Maybe it’s just me but it seems like when the computer has warmed up a little (by turning on and off on and on) starting up gets smoother. I mean the startup screen suffers from less horizontal flickering lines.
During the use of Leopard, I again get high CPU usage, especially when I use multiple programs at the same time, or when starting multiple programs. My iStat Pro said once that the fans were running at 4700 rpm and the heat of the CPU was about 70 Celsius. If I really want to **** my iMac off I should play a racing game. That just totally freaks him out! These problems could probably be solved by adding more RAM. Right?
The iMac also has a sleep problem. Sometimes after lets say an hour or so, you can’t get it out of sleep mode (by manipulating keyboard and/or mouse, the sleep light stops, but the screen stays off --> only solution is to restart). What happened to me once was that it slept so long that it just got into a deep sleep by turning itself off completely!
Here’s a list of what I tried so far:
- Disk Utility: Resetting the permissions, no problems were found.
- Resetting the SMU, both on the logic board itself as by pressing the power button 5 - 8 seconds, no improvements.
- Resetting the PRAM, no improvements.
- Did the Hardware test of the original install CD, nothing was found, all good.
- Did Archive and Instal, this actually messed my system entirely, cause it wouldn't boot at all and when starting up from the Leopard installation DVD it wouldn't recognize the Macintosh HD.
- Did Archive and Instal with the original disks, this disk did recognize Macintosh HD and so I installed the original system, 10.3. Booting problems and those flickering lines are still there though.
Next phase will be erase and install, but first I want to know what you guys think about all this.
Oh eh, One more thing; The guys at Applecare (phone support) told me that the replaced logic board was also out of warranty and so they couldn’t help me. But as the man on the phone was kind, he told me to go look for a special ‘driver’ on the net. He said that the driver should be able to resolve some of the issues described. He said that I had to give in the name of the LB on google and look for results. Is this bogus? Because I haven’t found anything useful on google so far. What’s the name (rather than a number) of the LB in the first place?
I hope you guys can give me some answers. I'm kinda desperate. But I still feel there's hope...

The symptoms of a flakey power supply are sleep problems and you have done all the right things as far as resetting the SMU and PRAM. Your CPU usage can be tracked by going to Utilities>Activity Monitor - look and see what is hogging the memory. The flickering lines could also be an optical system going south.
The other thing you can do is run DiskWarrior or TechToolPro to see if you have corrupted directories. Preferential Treatment will let you check for corrupted preferences.

Z77A-GD65 boot problem

Hello,
the display on motherboard keep showing changing codes until i force shut down but nothing on the screen, i cleared the CMOS many times but no use.
also removed the RAM and the mobo showed error 55 correctly.
this is for 1st bios
after that i switched to 2nd Bios and it worked and boot into windows CD but when i choose to repair my windows installation it said there's no valid windows installed, then it fails to boot again to CD and the motherboard only detect one hard drive... it gives AE error like nothing attached to it...
note: linux live USB work fine and i can browse my HDDs with no problem.
is my motherboard broken or there's solvable problem?
my rig:
Intel i7-3770K
GPU: GTX 680 lightning
RAM: dual kingston hyperX 4Gb DDR3 1833MHz
PSU: seasonic platinum 1000W

it started after i installed linux, there was a double windows boot problem so the GRUP boot loader didn't detect windows...
to solve it i deleted one boot file from windows HDD, and wanted to refix the boot using windows CD...then all of this started
and no i didn't try to flash bios at all, i was consider this as solution to what happened.
thanks~

[SOLVED]system fails to boot since adding udev rules for automounting

Hello
I have recently been trying to use udev rules to automount, and putting together stuff from the wiki, forums and general googling around have produced the following set of rules:
# automounts usb hdd and pendrives as usbhd-sdx; no messing around with
# volume labels or other confusing stuff
# matches all sdx devices except the internal hdd, sda
KERNEL=="sd[b-z]", NAME="%k", SYMLINK+="usbhd-%k", GROUP="users", OPTIONS="last_rule"
# imports filesystem information
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
# creates mount points and sets up symlinks
ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP="users", NAME="%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_r$
# automount all other file systems
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
This seemed to be working very well unitl I tried to boot this morning and the boot process stopped at "processing UDev events" with the following message:
iTCO_wdt: Unexpected close, not stopping watchdog!
It pauses at this point for 10-15 seconds and then reboots.
Having searched a bit, I found the following similar post on the forums: http://bbs.archlinux.org/viewtopic.php?pid=459375
Which suggests that the problem might lie with this line:
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
I have renamed the file so that it no longer has the udev .rules extension and now the system boots fine. Does anyone have any suggestions as to why the above rules might be causing this behaviour and how I might go about fixing it?
Thanks
Last edited by useradded (2010-07-02 22:58:14)

Hey falconindy
That was the final kick up the logical a$$ that I needed to get some kind of grip on udev rules. I now have a fully functional rule that applies only to /dev/sdxy and not to everything else as well, so no more boot trauma, THANK YOU.
I will mark this thread as solved and post my new rule for the benefit of anyone who might read this.
New rule (no boot problems):
# automounts usb hdd and pendrives as label or as usbhd-sdxy if no label present
# ensures the following is _only_ run for sdxy devices excluding internal hdd, sda
KERNEL!="sd[b-z][0-9]", GOTO="personal_usb_automount_settings_end"
# imports filesystem information
# provides access to following variables:
# ID_FS_UUID; ID_FS_UUID_ENC; ID_FS_VERSION; ID_FS_TYPE; ID_FS_VERSION; ID_FS_LABEL
# accessible via ENV{variable}; $env{variable}|%E{variable}
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise name usbhd-%k
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# creates mount points and sets up symlinks
ACTION=="add", SYMLINK+="%E{dir_name}", GROUP="users", NAME="%k"
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}"
ACTION=="add", RUN+="/bin/ln -s /media/%E{dir_name} /mnt/%E{dir_name}"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# automount all other file systems
ACTION=="add",ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", RUN+="/bin/rm -f /mnt/%E{dir_name}"
ACTION=="remove", RUN+="/bin/umount -l /media/%E{dir_name}"
ACTION=="remove", RUN+="/bin/rmdir /media/%E{dir_name}", OPTIONS="last_rule"
# exit
LABEL=="personal_usb_automount_settings_end"
Last edited by useradded (2010-07-02 22:59:20)

I have an early 2008 Mac Pro, which has re-booting problems. Also what does the spinning beach-ball indicate?

Hi, I have an early 2008 Mac Pro which has re-booting problems.
Processor speed is: 2.8
Memory: 2GB 800 MHz DDR2 FB-DIMM
2 x 28GHz Quad Core Intel Xeon
I am running OSX Yosemite Version 10.10
My Mac Pro keeps re-booting. Last year I had to replace my graphics card. My original card was the ATI Radeon HD 2600 XT 255MB, and that is what I have now. At this precise moment my Mac Pro is running perfectly, except that it is slow and the spinning beach-ball keeps appearing. I have managed to do some work with the disk utilities, verifying, cleaning and partitioning. Some errors were found and when it was cleaned this seemed to help my Mac Pro to function properly. Although I am able to use my Mac Pro now, from day to day I still experience re-boot problems. Also quite unexpectedly my mac dictionary has an error, it closed itself down and will not open at all, I had the message to say that a report will be sent to Apple.
I have tried starting my computer with an external hard drive fitted via a USB cable, I use for back-ups. This worked and I was able to wipe my hard drive clear and replace all info from the back up I had done only a few days ago.
This worked for a few days and then the same problem started again.
I am beginning to wonder if I need to buy a new hard drive.
If there is anyone who has some answers to help me solve my problem, I would be most grateful.
Robert

When you have the beachball activity, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Windows 8.1 pro boot problems

I upgraded my OS on a hp pavilion g6-1d73us from windows 7 home premium to windows 8.1 pro and ever since I have had boot problems. I took all the software off since I thought that might be the problem but the boot problems persist. The computer's self diagnosis helps but I still have problems. Is my laptop incompatible with windows 8.1? Windows 8.1 was a download and I still have recovery disks for windows 7. I originally thought the problem was incompatible software but now I am not sure.

Hi @hifive11 ,
Thank you for visiting the HP Support Forums and Welcome. I am glad you have recovery disks for windows 7, smart thinking. I have looked into your issue about your HP Pavilion g6-1d73us Notebook and having issues with the Windows upgrade to 8.1. Here is a link to the drivers page for your product. I do notice there are drivers for Windows 8.The Updates you need for the system are the Chipset. These are located on the driver page link above.
One of the things that can cause an issue is things connected USB. The computer can not load the drivers so it causes an issue. Once the machine is up to date then return the USB devices.
Then I recommended to restore the BIOS to factory defaults.Here is a link to restore the BIOS.
You can do a system restore. System restore will help if something automatically updated and did not go well on the Notebook.
Please note remove any and all USB devices. Disconnect all non-essential devices.
Hope this helps.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Edge e520 i5 UEFI/GPT Dual boot Windows/Ubuntu

Hi!
I have an Edge e520 1143GVG. It has an UEFI-Board with Win7/64 on MBR-Harddisk.
What I want:
GPT-Partition scheme and dual boot Windows 7/64 and ubuntu 14.04/64.
I managed to backup the partitions on an external HDD, install GPT on Harddisk, recopy saved Partitions and have now a fully running Win7/64 on GPT-System (it wasn't that easy as it seems here).
Next Step is to install Ubuntu on a separate Partition. I took a standard Ubuntu boot-CD, startet the pc with that boot disk (Board-Settings: UEFI/BIOS "Both", UEFI First) and installed Ubuntu without any trouble. Unfortunately no boot entry has been generated, so I tried to add one with EasyBCD. That doesn't work, an error is shown like "Windows cannot be startet, no valid file /NST/grub.mbr" or something like that.
I think the reason is that the cd booted in BIOS Mode, not UEFI. If I set board setting to "UEFI only", the boot CD will not start. So I built a bootable Ubuntu USB-Flashdrive with GPT-Scheme, but it didn't start as well.
After that I updated BIOS hoping UEFI-Boot from external devices will be possible then. It isn't.
The e520-board seems to be outdated or faulty, it is not possible to boot from USB or CD in UEFI-Mode.
Does anyone knows a solution? Will Lenovo update the BIOS?
kr,
Bernd Hollermann, Germany

I have to update my problem:
booting in gpt/uefi-mode is impossible from usb-key, but is ok from DVD. I managed to install Ubuntu now, everything runs well, after I took a 64-bit version on a dvd.

Mac Pro Boot Problems After 10.6.2 Update

After installing the latest version of snow leopard I am now having boot problems on my mac pro.
Symptoms;
-Screen resolution is incorrect at apple splash screen.
-Takes a lot longer than usual to boot.
-Once booted the blue tooth magic mouse isn't imediately reckonised, takes a while to find that.
-Once the mouse is finally reckonised it can move around but can't click on anything or bring up the dock. Tried a wired mouse, had the same problem.
-The keyboard is also not appearing to do anything, none of the shortcuts or quick keys work..
Had exactly the same problem after 3 restarts but on the 4th after leaving it for a good 20-30minutes it setled down and everything was working okay. However this is a recurring problem as I had the same thing yesterday...
I have a my 10.5.8 system backed up on an external so I am running from that at the moment. Don't want to go back to snowy til these problems are solved.
Any help will be greatly appreciated!
Martin

Try Safe Mode (It will take more time to startup in Safe Mode because it runs a directory check.)
Let us know.
-mj

How to solve Oracle SQL Developer connection problem ?

Folks,
Hello. I am using Oracle Database 11gR1. The Database Control Console https://localhost.localdomain:1158/em works correctly. I can create a Database and a table successfully.
My OS is Linux and connects to internet successfully.
In order to run SQL statements. we need to use Oracle SQL Developer. I connect Oracle SQL Developer in the following way:
Connection Name: DB1 (this is my database name as well)
Username: SYS (this is the user name I used to login to the Console)
Password: SYS (this the password used to login to the Console)
Connection Type: Basic
Host Name: localhost
Port: 1158
SID: DB1 (this is created during installing the Database)
But the error message comes up: "Status: Failure - IO exception Connection Reset."
Can any folk tell me how to solve Oracle SQL Developer connection problem ?

user8860348 wrote:
Folks,
Hello. I am using Oracle Database 11gR1. The Database Control Console https://localhost.localdomain:1158/em works correctly. I can create a Database and a table successfully.
My OS is Linux and connects to internet successfully.
In order to run SQL statements. we need to use Oracle SQL Developer. I connect Oracle SQL Developer in the following way:
Connection Name: DB1 (this is my database name as well)
Username: SYS (this is the user name I used to login to the Console)
Password: SYS (this the password used to login to the Console)
Connection Type: Basic
Host Name: localhost
Port: 1158
SID: DB1 (this is created during installing the Database)
But the error message comes up: "Status: Failure - IO exception Connection Reset."
Can any folk tell me how to solve Oracle SQL Developer connection problem ?username: sys
password: enter_your_correct_password given at the time of oracle installation
role: select sysdba if you would connect as sysdba else select normal for users other than sys
hostname: enter your oracle server hostname or ip address eg:- 192.168.11.12
to find the hostname open terminal/command prompt in oracle installed machine
type ---> hostname
type ---->ping hostname
you can find the ipaddress of the server
port number: 1521 (default) ----> i guess , else check the port number in the tnsnames.ora file under your ORACLE_HOME/network/admin folder
SID: DB1
try it
Good Luck

[SOLVED] UEFI Virtualbox installation boot problems

Similar Messages

Maybe you are looking for