Wallstreet suddenly sleeps during boot

I was recently given a 266mhz Wallstreet with a cracked screen and broken solder joint on the power socket. I successfully re-soldered the power socket, and was able to install an early version of OSX, upgrade the hard drive, go back to OS9.22 (so I could try installing 10.3 using XPostFacto). The problem started after installing my new screen. Booting into OS9.22, everything looks great until the desktop is displayed. I see the menu bar along the top, and suddenly it goes to sleep with a flashing green light. I tried booting to my OS9 and my OSX CDs to try reinstalling, and it does the same thing. As soon as it displays the desktop on the boot disk, my Wallstreet enters sleep mode. Most of the time it won't wake up regardless of what I try. A couple times I noticed that it tried to wake up (showed desktop for a second before sleeping again) - possibly on the bootdisk attempts.
I tried re-seating everything inside, including pressing hard on the processor board. Removed the keyboard, CD & floppy drives (I have no working batteries). Removed the top memory module. Still no improvement.
What could cause this?

Mana,
I would try this test: Remove the HD, then boot to a CD. If the Wallstreet finally stays awake, your HD is probably affecting the magnetic sleep switch. Read this reply I made to a user with a similar problem:
http://discussions.apple.com/thread.jspa?messageID=1323012&#1323012

Similar Messages

Suddenly "Fatal error during GPU init" during boot - radeon

Hi,
after a rather abrupt shutdown my system doesn't boot correctly anymore.
I have an Asus laptop with an ATI radeon HD 2400 (so the sticker on the laptop says - I'm not really a hardware guy)
Before:
While booting, the kernel/console output had bigger, somewhat non-high-resolution letters. Halfway in, the letters changed into a smaller, higher-defined font which was more "beautiful".
Sorry, I don't know what mechanism that is, so I had to describe it that way.
After:
This doesn't happen anymore. Rather, I get this message during boot (this is a copy out of /var/log/errors.log):
Jun 21 17:59:55 localhost kernel: [ 4.081919] radeon 0000:01:00.0: Fatal error during GPU init
Jun 21 17:59:55 localhost kernel: [ 4.082998] radeon 0000:01:00.0: no bo for sa manager
Jun 21 17:59:55 localhost kernel: [ 4.083059] [TTM] Trying to take down uninitialized memory manager type 1
I already tried the following:
- reinstall xorg and xf86-video-ati
- sections "Enable KMS" and "Troubleshoot KMS" from that wiki entry:
https://wiki.archlinux.org/index.php/ATI
- scream and slightly hit the side of the laptop
Nothing worked. Could anyone tell me where to continue searching? I'd hate to reinstall a 1-week old system.
Thanks in advance,
Alex

If you remove the ati drivers, the mesa-drivers are used I think.
Since the open source drivers don't work, you should try the closed source drivers (ATI Catalyst) from the AUR. Installing this is a bit of a hassle. The catalyst driver does not support Xorg 1.12, so you have to add a repository for Xorg1.11 and downgrade (see the wiki page). Then, you should install either catalyst-utils and catalyst-hook from AUR (as described in the wiki) or catalyst-total (which combines both and is also mentioned in the wiki).
See the Catalyst Wiki for all information.
Catalyst Utils in AUR
Catalyst Hook
Catalyst Total
edit: I just read the wiki. It seems like there is an easier way to install things now: https://wiki.archlinux.org/index.php/AT … repository
Last edited by Terminator (2012-06-25 23:32:39)

MBP 2010 goes to sleep during login

I cannot boot up by MBP. It starts with the gray screen and the apple. The baton spins around a while, then the display goes to black, not suddenly, but a quick fade. Sometimes it then comes up again with the gray screen and the cursor in the corner. But then it goes back to black.
The computer is unresponsive - caps lock does not respond. Looks like it is asleep - white light is pulsing, battery meter shows full, charger is charging.
I have hard shut the computer many times. Occasionally, it will show a flash of a screen before shutting, and the screen is the waking from hibernation, like when you wake the computer after the battery is low and the computer shuts down by itself. But it is fleeting and the battery meter shows fully charged.
I have a feeling therefore that it is going to sleep during the login process.
I have tried PRAM and SRC reset - no change.
I have tried to boot in safe mode, and it also goes to the black screen.

Hey Frederic
The next step is to boot to your install disk or Recovery Disk and use Disk Utility to verify the Disk. After that the next step would be to reinstall the operating system.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/TS2570
OS X: About OS X Recovery
http://support.apple.com/kb/HT4718
OS X Mountain Lion: Reinstall OS X
http://support.apple.com/kb/PH10763
Thanks for using Apple Support Communities.
Regards,
-Norm G.

Sudden Sleep.SUDDENLY SLEEPING HELP..

Paris France. Feb 2006.
SUDDENLY SLEEPING. Like, I'd be typing along, with the powercord plugged in and a full battery charge, and the display goes blank and the whole machine sounds like it's going into hibernation. I can always get it back just by pressing a key and waiting a few seconds, but it's very strange and disturbing, and besides, it's totally aggravating! Have anyone found a solution to this bloody problem. please HELP... I am now on 10.4.5
Help..sudden sleep.
Victor

Mac OS X: Why your Mac might not sleep or stay in sleep mode
Learn why your Mac might not go to sleep when you expect it to, or why it might not stay in sleep mode. What's sleep mode? It's a low power, energy-saving feature of that offers both environmental and economic benefits, as well as helping to extend the life of batteries and displays.
On the other hand, you probably don't want the computer to sleep at certain times even if you're not using the keyboard or mouse, such as when you are:
While watching a DVD movie
Listening to your iTunes music library
Running an automated backup
Away from your computer while downloading large files
Tip: For troubleshooting tips, go to the "How can I determine what is causing a sleep issue and resolve it?" section at the bottom of this article.
Why doesn't the computer go to sleep at the expected time based on Energy Saver settings?
You can configure Energy Saver preferences to set your computer to automatically sleep after a specified period of time; an internal counter called a "sleep timer" monitors the amount of time your computer has been inactive. When the counter's time matches the amount of time you specified, the computer enters sleep mode and displays a pulsing power light.
Some things reset the sleep timers, preventing the computer from sleeping:
Hard drive access (even if you're not using the computer, a running application might be accessing your drive, such as when downloading a large file or listening to music in iTunes)
Moving the mouse or using a portable Mac's trackpad, pressing a mouse button, or pressing a key on the keyboard
Some System Preferences settings (see below)
Open applications (see below)
Input devices (see below)
Expansion cards (see below)
Additional drives, such as USB, FireWire, DVD, or CD drives (see below)
Some System Preferences settings affect sleep
Energy Saver
Energy Saver is a System Preference that can help you optimize energy settings as well as sleep times and processor usage. Note that processor controls are not used for Intel-based Macs because they have a built-in power-saving feature. Only PowerPC-based Macs display processor controls.
Bluetooth
You can allow Bluetooth devices to wake a sleeping computer by enabling "Allow Bluetooth devices to wake this computer" in Bluetooth preferences. Simply having a bluetooth device paired does not prevent a system from sleeping.
Spotlight
Your computer will not sleep if Spotlight is indexing content, because that requires hard disk access. For example, if you just installed or reinstalled Mac OS X, Spotlight may need a while to index content.
Sharing
Network activity can reset the sleep timer, too. For example, leaving a self-refreshing Web page open in a Web browser.
In these situations, the display will sleep (unless Energy Saver preferences is configured to never let the display sleep) but the processor will continue to be awake and the power light will remain on.
Keyboard, mouse, other input devices can affect sleep
Keyboard presses and mouse button clicks can wake a sleeping computer. Mouse movement alone will only wake a sleeping display. Even though your Mac may be in sleep mode, it remains aware of keyboard presses and mouse clicks. If you move a mouse, press a key, or use a different input device, the sleep timer counter will reset.
Open applications can affect sleep
Software that accesses the hard drive will delay sleep mode until it is either quit or done accessing the drive, for example:
A self-refreshing Web page open in Safari.
Songs playing in iTunes.
A movie disc playing in DVD Player.
However, this can also occur in subtle ways you might not expect:
An application window might display text that periodically changes (such as a clock).
If an application uses a custom font to display text but the font resource is marked purgeable, then at some point the memory manager will purge the font from memory. When the application tries to draw text using that font again, it will be loaded from the hard drive, resetting the sleep timer.
Applications can be designed to keep the system awake and prevent idle sleep indefinitely. In developer lingo, an application may explicitly prevent system sleep by calling IORegisterForSystemPower(), and calling IOCancelPowerChange() when it receives a power management kIOMessageCanSystemSleep notification.
Expansion cards can affect sleep
Some PCI expansion cards can prevent sleep. If a card's Mac OS X device driver is not properly power managed, the computer will be unable to safely remove power from it, preventing the system from entering full sleep. Instead, the system enters a state named "Doze".
Some kinds of PCI cards prevent any kind of sleep mode--your system will not go into low-power mode during long periods of inactivity. The computer fans may run excessively when this is the case.
Other hard drives (USB, FireWire, ATA), optical media drives (DVD, CD) can affect sleep
If there is disk accesses activity at least once a minute on disks such as ATA drives, FireWire drives, and USB drives, the computer will not idle sleep.
How can I determine what is causing a sleep issue and resolve it?
As mentioned above, these are the most likely causes and solutions for sleep issues:
Sharing preferences: Enabling sharing for any connections can potentially disable sleep. Turn off file sharing if it's not being used.
Bluetooth settings: Bluetooth can wake your computer if you set the "Allow Bluetooth devices to wake this computer" checkbox in Bluetooth System Preferences.
Is a keyboard and mouse connected and working correctly?
Do you have any other external USB or FireWire devices connected? Try removing them one by one or disconnect when not in use.
Is Spotlight indexing? This can take anywhere from several minutes to several hours after a new installation. Indexing prevents idle sleep.
Additional Software: Try a Safe Boot to help isolate a software issue.
Sound check: Put your ear near your computer. Do you hear the sounds of hard disk access (a clicking or "clacking")?
Energy Saver settings: If the computer and display sleep timers are set to Never, the computer will not sleep.
Search Advanced Search | Help
Email This Article
Log in to send email
Did this article help you?
It solved my issue...
Tell us what works for you.
It's good, but...
Report typos, inaccuracies, etc.
It wasn't helpful...
Tell us what would have helped.
Languages
This article is available in the following languages:
English
Keywords: ktech kmosx4 kmosx3 kmosx2 kmosx

Ultra 5 Hangs During Boot

My Ultra 5 hangs during boot at the following point....
setting default ipv4 interface......
I have tried resetting my router, unplugging the network cable, and nothing seems to work.
John

jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

N200 shuts down during boot

Dear Lenovo,
I have a problem with my N200 laptop. Notebook shuts down during boot. Sometimes it is immediately after "Lenovo screen", sometimes it is when Vista logo appears. I found out that this is always when notebook is "cold". It does't matter if I want to switch on my notebook or if I want to restore it from hibernation or sleep mode. Next thing is that it always crashes when fan starts work at full tilt (I checked the fan but it is clear). When notebook starts correctly then it works without problems. Usually I have to switch it on about three times then it is OK. This problem takes about 2 weeks. I have my laptop about 7 month. Do you have any ideas how to solve this problem?
And another thing - I forget to send registration card to Lenovo and now I am afraid that I will be without warranty. Can I send it still now?
Thank you for answer and sorry for my English.
Gabi

Yes, problem with the video card sounds plausible! Any not so successful updates recently? It is sometimes to make a good uninstall, which is required to make a good install.
4in1 drivers should - esp. with W98 and ME - be installed while in SafeMode and with all autostarting programs disabled, for example Antivirus and utilities.
Else, since you have a damaged regedit, I would reinstall Windows. You might have done something for example an upgrade or new install the registry, not healthy, has made a note of. Some utilities also overwrite and change system files without good results.

Dhcpcd-based network fails during boot

Hi,
My fully updated Arch_X86-64/KDE is connected to the Internet router via (on-board wired) eth1, and is configured to get an auto IP address.
This has worked flawlessly for years till two days ago.
Ever since, eth1 service fails during boot, and requires several manual dhcpcd command to finally kick in. The same applies after waking from sleep mode. (see terminal output below)
As can be seen the system is configured to load the (correct) r8169 mode.
Please advise.
Thanks
Miki Badt
---------copy of respective commands---------------
# journalctl -b | grep eth
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: RTL8168d/8111d at 0xffffc900119d2000, 6c:f0:49:ed:b3:e9, XID 083000c0 IRQ 49
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: RTL8168d/8111d at 0xffffc900119e6000, 6c:f0:49:ed:b3:eb, XID 083000c0 IRQ 50
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:23 Miki_Arch dhcpcd[339]: eth1: waiting for carrier
Sep 15 15:50:23 Miki_Arch dhcpcd[336]: eth0: waiting for carrier
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:05:00.0 eth0: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth0.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth1.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
#manual commands
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1039]: version 6.0.5 starting
dhcpcd[1039]: eth1: waiting for carrier
dhcpcd[1039]: timed out
dhcpcd[1039]: exited
[root@Miki_Arch miki]# ping www.ynet.co.il
ping: unknown host www.ynet.co.il
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1046]: version 6.0.5 starting
dhcpcd[1046]: eth1: soliciting an IPv6 router
dhcpcd[1046]: eth1: rebinding lease of 192.168.1.13
dhcpcd[1046]: eth1: leased 192.168.1.13 for 3600 seconds
dhcpcd[1046]: eth1: adding host route to 192.168.1.13 via 127.0.0.1
dhcpcd[1046]: eth1: adding route to 192.168.1.0/24
dhcpcd[1046]: eth1: adding default route via 192.168.1.1
lspci -v | grep Ethernet
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
lspci -k
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
cat /etc/modules-load.d/realtek.conf
r8169
Last edited by mibadt (2013-09-15 13:29:25)

Hi,
I've some errors with the new dhcpcd, you should downgrade.
https://wiki.archlinux.org/index.php/Do … g_Packages

Laptops in docking station with lid closed go to sleep during in-place migration from XP to Windows 7

We have an issue where existing XP laptops are targeted with SCCM 2012 OSD TS for upgrade to Windows 7. The laptops are in a docking station, with the lid closed. The laptops are going to sleep when the OSD is booted in WinPE, just before the
Setup Windows and Configmgr step. I have copied powercfg.exe from a Windows 8.1 machine (both AMD64 and x86 versions) to the MDT Tool package...." and then a step to run:
%DeployRoot%\Scripts\%PROCESSOR_ARCHITECTURE%\PowerCfg.exe -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0
However, the laptops are still sleeping during the Setup Windows and Configmgr step. Any insight to correcting this will be extremely helpful.

Hi
We came across this issue, seems odd that SCCM doesn't suspend the power management in the OS during the TS - (But then again it also seems odd that Windows 7 will go to sleep if you close the lid of a laptop half way through a shutdown, so that when you
lift the lid it wakes only to complete the shutdown, did MS not spot that, or choose to ignore it!?).
These commands should be run soon after the Setup Windows and ConfigMgr step and will disable the device and screen from sleep/hibernating:
Prevent sleep during OSD (Battery power)
cmd.exe /c powercfg -x -standby-timeout-dc 0
Prevent sleep during OSD (AC power)
cmd.exe /c powercfg -x -standby-timeout-ac 0
Prevent monitor off during OSD (Battery power)
cmd.exe /c powercfg -x -monitor-timeout-dc 0
Prevent monitor off during OSD (AC power)
cmd.exe /c powercfg -x -monitor-timeout-ac 0
Prevent hibernate during OSD (Battery power)
cmd.exe /c powercfg -x -hibernate-timeout-dc 0
Prevent hibernate during OSD (AC power)
cmd.exe /c powercfg -x -hibernate-timeout-ac 0
At the end of the TS, you can revert these changes by running the following command to reset the power scheme:
powercfg -restoredefaultschemes
Hope this helps
Thank you. However, we did put similar steps in our Task Sequence right after the "Setup Windows and..." step, but the issue we are having is that the "Sleep" occurs during the "Setup Windows and...." so it never reaches
anything after that step until the lid is opened.

Internal keyboard ignored during booting

My MBP suddenly ignores any keyboard command during booting like the option-key or cmd-opt-p-r. It only responds to an external usb Apple keyboard. It operates normal under OS X though.
This happened after I tried several times to install Win Vista and Win 7 RC through Boot Camp on the original hdd (320GB Seagate) to no effect.
If I insert the original Vista dvd and press the option-key I can choose between OS X, Windows and EFI. Pressing Windows results in just a black screen, but pressing EFI results in an error screen stating something like BSD (double kernel panic) and then a sort of powerpoint presentation starts: the screen starts in grey and redraws about 10 times from the top to the bottom, every time a little darker until a full black screen. A few months ago this dvd installed just fine on this MBP using a different hdd.
PRAM reset and SMC reset using the external keyboard brought no redemption. Is there some sort of system reset that goes a level or two deeper than these two resets? It seems that EFI is damaged somehow.

Actually, if you cut out all the specs I included, it is simple; regardless of whether I use a wireless combo or simple PS-2 keyboard and mouse directly coupled with no networking between the computers, the keyboard will deactivate on bootup about half the time on either computer. I have also noticed that BIOS checked Soundblaster fails to activate at about the same rate, but not necessarily at the same boot up. This is evident because I have a case bottom speaker that was used for detecting problems at bootup, although MSI does not have a similar program to Soyo Voice Doctor. The speaker still records Soundblaster kick in.

I am getting frequent lock-ups and blue screens during boot up. The lock ups occur during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button. Ideas?

I am getting frequent lock-ups and blue screens during boot up on my Mac Pro. The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
I had the Mac Defender malware and I have used apple jack but still having issues.

I am getting frequent lock-ups and blue screens during boot up on my Mac Pro. The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
I had the Mac Defender malware and I have used apple jack but still having issues.

RV180 (wired only) problems with firmware 1.0.4.14, fails to boot correctly + LAN ports power off during boot (downgrading to 1.0.3.10 = fine again).

Hi All,
A few months ago when 1.0.4.14 was released I was quick to update to this version from 1.0.3.10 but very quickly ran into issues.
Bit of background info... I am not doing anything complex with this box, basic IP4 network over all LAN ports, no VLANs, firewall enabled and allowing 2 port access rules to a static IP address. Any static IPs are assigned manual at host level but all other devices receive DHCP IP addresses. I don’t host VPN on this RV180 but I do with another. Routing VPN has no issues. WAN is connected to another switch provided by my ISP who provides DHCP IP Address with their DNS etc. Only LAN ports 1 and 2 are connected, port 1 to my Wireless AP (AP mode passing all requests to the RV180, DHCP etc.), port 2 connects to a 8 port Smart Switch (but all 'Smart' features are currently not in use, so basic switching only). All other settings on the RV180 are on recommended defaults.
Everything is working fine on 1.0.3.10 but I have all kinds of issues after updating to 1.0.4.14. Here are the actions and experiences I had...
1) Backup my RV180 config to txt file.
2) Navigate to the firmware upgrade page and follow steps to complete the upgrade process from 1.0.3.10 to 1.0.4.14. *router does the normal process of upgrading*
3) RV180 reboots to complete but doesn’t come back up even after waiting 5-10 mins. LAN ports enable during boot up (link lights on) but after about 2mins turn off (no link lights). WAN light is on alongside the Power Light.
4) Power cycle even with rest... Same results.
5) Reset the RV180 to default settings. I can sometimes get the unit to boot up and the LAN remains active and powered up. The web UI is VERY slow compared with 1.0.3.10. Internet sometimes works and sometimes doesn't (I would expect it all work without issue on default settings).
6) I repeat this a few times, various resets, powered off waiting periods, etc. but I always have issues. I did manage to get some log file information and the Kernel appears in the Alert, Error and also the Warning logs (please see attached files).
7) I gave up at this point. No major issues like this reported on the internet from a few google searches etc. So I then reset to defaults (1.0.4.14), downgrade to 1.0.3.10 and finally reset to defaults again + restore backup config settings (with some manual changes).
The router has remained like this and seem to be working fine, but I would like any security improvements from 1.0.4.14 firmware on my device.
Anyone able to help, have the same issue or can advise me in any other ways?
I see 1.0.3.10 isn’t displayed as a firmware download on the standard support page for the RV180 now. Only 1.0.2.6 and 1.0.4.14. Do I need to downgrade again to 1.0.2.6 before upgrading to the latest version?
Regards,
~FAZ~

Hi,
I recently bought a RV180 router and immediately I encountered the same problem; practically I am not able to access the web GUI.
The PC is directly connected to the router, nothing else is connected; the TCP/IP configuration is as follows:
PC: 192.168.1.100
RV180: 192.168.1.1
GATEWAY: 192.168.1.1
SUBNET MASK: 255.255.255.0
Once the router is turned on, the power LED flashes fastly, the Ethernet LED is on but after few minutes it disappears and the PC detects a disconnection of the Ethernet cable.
The router is not pingable and, as I said, the web interface is not reachable.
I have tried to power cycle the router, to reset it (pressing the reset button for more than 3 second and for more than one minute), to access the rescue mode and download a new firmware through TFTP, but nothing worked.
Few times, after many boot and reset trials,I was able to access the web interface and in one of these occasions I updated the firmware to 1.0.4.14 but once the router is powered off the problem arises again at the next power on.
I have not tried yet to downgrade to an older firmware version.
Can you suggest any solution? thank you.

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.

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

Read-Only Problem during Boot

Hi,
I tried to update my system today, like every week, with the standard command pacman -Syu. After installing all updates, my window manager (gnome3) crashed and i tried to restart my System. After the grub window appeared and I choosed my kernel the normal startup commands are shown until the Arch prompt appeared. The one where Arch Linux tried to start all relevant processes. After that there are only mistakes. All startup processes are busy or failing. The only message i get is, that the filesystem, i think thats the root partition (ext4), is read-only or another error: some files for startup cannot be created because they already exist.
Getting to console is also impossible, because the system tries to start virtualbox additions, with an funny message, that it is busy and tries it again in 5 min (infinity loop). But shidt happens. I have read in another post that I can try another Linux System, mount my root partition and do an
fsck /dev/sda3 -p or -f
. But it says that all is clean (sda3 is root and sda1 is /boot). The filesystem is ext4, so i tried also fsck.ext4, but it also say all is clean.
After another boot i stoped at the position, where the fist error occur.
Mounting Local Filesystems
/etc/rc.sysinit: line 285: /etc/mtab: Read-only file System
next one:
Activating Swap
/bin/rm: cannot remove '/etc/localtime': Read-only file system
removing leftover Files
/usr/bin/find: cannot delete 'var/run/cups.pid': Read-only file system
After that message there are also al lot of analog errors.
I have no other idea than an dirty filesystem. Is there another possibility to rescue my system without an fresh install. Im sorry but i cannot log any messages at that state of boot. So it is not easy to get better informations about special error codes.
I have forget to give you some informations about my stats:
- actual stable arch kernel 2.6.38
- gnome 3
- thinkpad t400
Last edited by Psikon (2011-05-13 20:18:12)

With udev 168-1 I obtain this message during boot:
:: checking filesystems
fsck.ext4: no such file or directory while trying to open /dev/sda6 (my root device)
Possibly non-existent device?
***************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
but fsck run manually says it's all clean.
I have to remount rw / partition and manually mount all the other partition, then I can switch to runlevel 3.
With udev 167-2 (and prior) I can boot without any problems.
I'm not sure it's a problem from udev, but downgrading it works for me.

"F11 System Recovery" during boot does not work after Cloning hard drive.

Problem: “F11 System Recovery” during boot does not work after Cloning hard drive.
HP Envy m6-1125dx UEFI Notebook Computer with GPT hard drive.
Original Seagate Hard Disk GPT 700GB with Window 8.0_64 upgraded to Windows 8.1_64
Startup Menu (F11 System Menu works properly) only on original hard drive.
Following obtained from Disk Management & diskpart in Command Prompt.
GPT Disk <700GB>
Partition 1 WINRE NTFS Primary 235MB/400MB [Recovery]
Partition 2 EFI System FAT32 (LBA) Primary 108MB/260MB [System]
Partition 3 (NONE) Unformatted Primary 128MB/128MB [Reserve]
Partition 4 Main NTFS Primary 90GB/195GB [Primary “C”]
Partition 5 (NONE) NTFS Primary 372MB/450MB [Recovery]
Partition 6 Data NTFS Primary 7GB/475GB [Primary “E”]
Partition 7 NTFS Primary 26MB/350MB [Recovery]
Partition 8 Recovery NTFS Primary 24GB/26GB [Recovery “D”]
I have Cloned the original hard drive to a new HGST 1TB Hard Drive using four different methods (sector by sector):
Acronis True Image 2015
Acronis Backup for PC
AOMEI Backupper Professional
Macrium Reflect
Each time the cloning process completes successfully and has the same original partition arrangement. The computer works properly except when trying to use the “F11 System Menu” key during boot. It gives the following error message:
“Recovery
Your PC needs to be repaired
A required device isn’t connected or can’t be accessed.
Error code: 0xc0000225
You need to use the recovery tools on your installation media. If you don’t have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. “
Any suggestions why the F11 System Recovery does not work during boot and how to fix the problem would be appreciated. I have does various disk checking and file checking on both the original and new hard drive with no errors.
Thank you in advanced.

Hi,
How did you clone the HDD ? One-for-one or different method ?
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Wallstreet suddenly sleeps during boot

Similar Messages

Maybe you are looking for