Error during booting Arch

Hi all!
I just installed Arch Linux by using the HOWTO installation on this forum.
When I try the command "migrate_udev" nothing happens.
Then I tried to use "udev", which doesn't gives any output unless "no such command". Well, I went further on. Then I rebooted and I got this error!
atkdb.c: Spurious ACK on isa0060/serio0. Some program might be trying tp acess hardware directly
What did I do wrong, and how can I actually get Arch to work?
I'm using a Dell XPS400 Pentium 2 400Mhz.
Sincerly yours,
Kasper

Have you tried one of the new 0.8 install cd's?
http://bbs.archlinux.org/viewtopic.php?t=27994
ftp://ftp.archlinux.org/other/0.8/i686
In fact, if your a using an older install cd, try the ftp install, which would should get you further along.
If you did do the ftp install, or updated with pacman, then you probably need to refer to you harddrives ad "sda1" instead of "hda1" etc...
Don't know if any of this helps...

Similar Messages

3 unable to open '/etc/udev/rules.d/':m error during booting

After a recent upgrade to the kernel26-2.6.28.5-1-i686, I got the above error during booting in one of the laptop.
My search did not give any positive solution for this till now. I read that now udev gets its rules from /lib/udev/rules.d.
But still rules files in /etc/udev/rules.d and /lib/udev/rules.d are different. I know that any symllink work around will not work in this case, I tried but as expected the error message appears again.
So, I roll back to kernel26-2.6.28.4-1-i686 and everything back to normal.
Any Idea to resolve this? (package is not broken as I use the same mirror for another PC and in that I am not getting any error)
Last edited by kgas (2009-02-19 16:10:23)

This issue got resolved on its own with the latest kernel (kernel26-2.6.28.6-1-i686) update. I will leave this topic for some more time to see others response...

G580 Upgrade to Windows 10 failed in the SAFE_OS phase with an error during BOOT operation

0xC1900101-0x20017 I could not successfully upgrade from windows update, nor from the straight download site. The installation failed in the SAFE_OS phase with an error during BOOT operation. I see w10 bios updates for other models. Has anyone been successful in upgrading to W10 from W8?

2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:36:21, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >:uspend(1066): Result = 0xC18001042015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteInstallMode(656): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteDownlevelMode(376): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupManager::Execute(222): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupHost::Execute(370): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216
2015-07-31 21:36:36, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
2015-07-31 21:36:40, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
2015-07-31 21:37:02, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:37:03, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2015-07-31 21:37:11, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:39:15, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:39:18, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]

[SOLVED] nouveau error while booting arch

Hi!!! I'm newbie to arch, here is an error I can't solve myself. I search in google for solutions but they didn't solved. Please help me to solve this. I dual booted arch linux with window 8.1. After installation, while booting for the first time, this error occurred.
Here is the error I found.
[0.063411] Ignoring BGRT: Invalid status 0 (expected 1)
starting version 218
Arch_Linux: clean, 70622/18677760 files, 1643393/74703025 blocks
[ 15.759913] nouveau E[ PIBUST][0000:01:00.0] HUBO: 0xffffffff (0x1a
[ 15.759952] nouveau E[ PIBUST][0000:01:00.0] GPCO: 0x00000001 (0x1a
[ 15.823494] nouveau E[ PBUS][0000:01:00.0] MMIO: 0x00000000 FAULT a
[ 15.824050] nouveau E[ DRM]Pointer to TMDS table invalid
[ 15.824072] nouveau E[ DRM]Pointer to flat panel table invalid}
Last edited by aaa234 (2015-02-04 04:18:42)

aaa234 wrote:
runical wrote:
That is a different problem to be honest. I assume that you can login using your normal user? If you set up sudo you might be able to get into root by using
sudo su
and change the password like that.
I'm sorry if this is a noob question. Where do I type sudo su because as soon as the OS is booted, the system asks localhost login and password. I haven't installed any desktop environment yet. I only set up a password under arch-chroot but I can't login with and without that password.
I was assuming a normal installed environment with a normal user. Using "sudo su", you can abuse privileges granted by sudo to circumvent the password required by su. A well configured sudo should not allow this, but in this case it seemed likely that the system was not completely set up yet.
problem has been solved with this https://bbs.archlinux.org/viewtopic.php?id=168879
Then, if there are no more problems, please mark the thread as solved.

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.

Memory Allocation Error during Boot

Hi,
I am posting this on a different computer than the one on which I istalled Java because I can no longer get it to boot.
Here's the history:
I am working in Windows 98
I added a line to the autoexec.bat so that the PATH lines looked like this:
SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=%PATH%;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
I then rebooted and tried the javac and java commands in different folders and everything worked fine. I shut down the computer and tried to reboot a day later. The following are pieces of the message I received (I don't usually go near the autoexec.bat or system settings so I have no idea how to get past these errors, nor fix them):
SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
General Protection Fault in C:WINDOWS\SCANDISK.ALT at 0090:1921
Memory Allocation Error
Cannot load COMMAND, system halted
Please help!
Thanks,
Julie

SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SY
ATEC\PCANYW~1;"C:Program
Files\Mts";"C:j2sdk1.4.0_02\bin
General Protection Fault in C:WINDOWS\SCANDISK.ALT at
0090:1921This shouldn't have been caused by the Java installation. As I understand the situation, at load time scandisk has been called. This is usually due to the computer not having been shut down properly, or a sign of real problems. However, scandisk is unable to run.
You should try a forum/newsgroup for Windows for more help. My own suggestion would be to load to the command prompt (or try safe mode). (Press F8 during boot to get a menu.) And then run scandisk manually. If it works, try renaming the C:\WINDOWS\SCANDISK.ALT file and rebooting.
Regards,
Bhaveet

Errors during boot OEL 5.5 starting a 11.2 instance

Hello,
I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).
Many thanks,
Aurel

Hi;
I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).For can see your db up or not u can run :
ps -ef|grep lg
oracle 6750316 1 0 Feb 28 - 0:03 asm_lgwr_+ASM
oracle 9437238 14418146 0 16:06:56 pts/3 0:00 grep lg
oracle 14745644 1 0 15:50:41 - 0:00 ora_lgwr_orcl
So my asm instance and db instance is up
For alert or error message you need to create one sh which is cheking alert.log,if you hit ORA error than it can send u email
Regard
Helios

Error during boot

When doing tmboot, I have obtained the following error:
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
That it means? So that one takes place? The documentation on the error indicates
that any action is not necessary. And that the servants can have published or
no. I have verified with tmadmin that the servants estan DEAD. He can be a problem
of allocation of resources, can be that ipc does not have sufficient resources
associate? Somebody podria to give an idea me on like acting? Thank you very much

This error message is normaly printed if the server is directly going down again
during boot. Don't know what your servers are, but you will see this error message
e.g. if the server is not able to allocate its resources like database access,
open config/logfiles, etc.. As the server is not booting you have a problem you
should investigate. Taking a look to your ULOG and stdout/stderr files may give
more details.
"lucia vilar" <[email protected]> wrote:
>
>
When doing tmboot, I have obtained the following error:
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
That it means? So that one takes place? The documentation on the error
indicates
that any action is not necessary. And that the servants can have published
or
no. I have verified with tmadmin that the servants estan DEAD. He can
be a problem
of allocation of resources, can be that ipc does not have sufficient
resources
associate? Somebody podria to give an idea me on like acting? Thank you
very much

[SOLVED] Error during boot, need help to identify

I've noticed recently that I'm getting an error during (taken from dmesg)
[ 7.982440] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
[ 7.982865] DRM: Fill_in_dev failed.
can anyone tell me where this is coming from and how to fix it maybe? I have a Intel i7-2600K (Ivy Bridge generation) with a Nvidia GTX 580 card using the propriatary driver.
Last edited by fettouhi (2014-11-20 21:28:04)

BTW, if your processor really is an i7-2600k, that would make it a Sandy Bridge (2nd gen) processor, not an Ivy Bridge (3rd gen and starts with a '3'). Unless this is just a typo, knowing this might help you debug things in the future, as there are unfortunately bugs that affect some 2nd but not 3rd gen procssors, and vice-versa.

Error During Boot Up

After I selected Arch in Grub, the system starts to load up and I noticed during the loading of Arch Linux, there was an error of some kind pertaining to 'alsa'. The text was scrolling too fast and I was wondering how I can see what error that was. I checked /var/log/everything.log and couldn't see anything but it's clear as day when Arch is booting...
Anyone know how I can see this error once I am in the OS?

Press the Pause / Break button on your keyboard, the one next to Scroll Lock, to pause/resume the booting process!

[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
As for suspects... I had systemd working fine.
-- I updated some packages (not more than a few days worth and I'd have to check the list)
-- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
I've been booting in by appending
systemd.unit=emergency.target
to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
-- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
-- systemctl list-units
-- systemctl list-unit-files
-- journalctl and looking around for instances of fail or failed or dbus
If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
Thanks!
Last edited by jwhendy (2012-11-08 16:07:33)

As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

Win 8 boot error; Dual booting Arch/pre-installed Win8.1

Hello everyone! My name is kuhi and I have this problem that's driving me insane. I've tried all sorts of things... googling here and there, up and down.
The setup worked splendidly until one morning I turned my computer on, booting into the Windows Boot Manager from grub. Suddenly, out of the blue, I get this error:
Required device isn't connected... Error: 0xc0000225
Now none of the options in the recovery mode work... Refresh, reset, particular command prompt commands, you name it.
Another thing is, this error seems to have locked the windows partition itself, thus hinding it from itself, I guess. Now I can't even mount the drive on linux. It just tells me that I'm not authorized to do that. All I want right now is to access the filesystem and retrieve some of the personal files left in there, then It can all go to hell.
I don't know what to do. I've tried different BIOS and Boot options thinking it might work, but with no avail. I'm lost, is there anyone out there, who has ever met this kinda error? Or at least someone, who can point me in the right direction? I'll be happy to provide any information I can get.
Thanks in advance,
kuhi.

TheSaint wrote:Supposed that is NTFS, you should have/install ntfs-3g package
and try ntfsck over that partition (/dev/sda4)
One more tool is testdisk to see if the partition table is sane.
YOU ARE AMAZING! Thanks a lot... it seems that after getting the packages you listed I am now able to mount and access the Windows8 partition. Doesnt neccessarily fix my issue, but at least I can retrieve lost filed. You are truly the saint
Edit: now i dont know how to open Docs & Settings as it seems to be an unsupported file, but ill try to figure that out
Edit2: hell its probably like password locked
Edit3: turns out its a broken symbolic link to /mnt/.NTFS-3G/C:/Users.. any way to fix this broken link
Last edited by kuhi (2014-11-20 00:18:12)

Windows 8.1 error during boot on macbook

installed windows 8.1 on the bootcamp partition but everytime I try to boot.I get the error code 0xc000000e.since my computer woulnt boot from the cd. I linked the boot camp hard drive to VirtualBox where there I installed it and booted it sucessfully. But
everytime I try to boot it nativly. It does not work

Hi,
For this issue,please check the event viewer to see if some error log appeared when the issue occurred.
It seems that it was caused by corrupted user profile.
I suggest you use other account to test it.
If the issue still persists, please photograph the error message and collect crash dump file, then upload here via skydrive or similar network device and share the link here for further research.
To collect the crash dump, follow these steps:
First enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\explorer.exe]
"DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\
00,6d,00,70,00,73,00,00,00
"DumpCount"=dword:00000010
"DumpType"=dword:00000001
"CustomDumpFlags"=dword:00000000
Then, open a program which may cause the issue. If error appeared, please find the crashdump file under c:\.
Regards,
Kelvin hsu
TechNet Community Support

HDD errors during boot

Hello,
it's been a few weeks since the following errors appeared for the first time. I get them every time I boot the computer.
Sometimes all goes well, while other times I have to run fsck on one or more lvm logical volumes to continue booting (i.e. home, boot etc which are mounted on separate logical volumes) (I don't know whether this is relevant but only one of the three drives belongs to an lvm volume group).
Any suggestions?
Thanks,
Theodor
[ 11.379855] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 11.379912] ata4: irq_stat 0x00400040, connection status changed
[ 11.379934] ata4: SError: { PHYRdyChg DevExch }
[ 11.379954] ata4: hard resetting link
[ 11.386347] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 11.386403] ata2: irq_stat 0x00400040, connection status changed
[ 11.386447] ata2: SError: { PHYRdyChg DevExch }
[ 11.386483] ata2: hard resetting link
[ 11.386553] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 11.386609] ata1: irq_stat 0x00400040, connection status changed
[ 11.386653] ata1: SError: { PHYRdyChg DevExch }
[ 11.386688] ata1: hard resetting link
[ 18.508080] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 18.508121] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 18.529130] ata2.00: configured for UDMA/133
[ 18.529136] ata2: EH complete
[ 18.535800] ata1.00: configured for UDMA/133
[ 18.535804] ata1: EH complete
[ 18.577859] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 18.577928] ata2: irq_stat 0x00400040, connection status changed
[ 18.577971] ata2: SError: { PHYRdyChg DevExch }
[ 18.577991] ata2: hard resetting link
[ 18.604794] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
[ 18.604849] ata1.00: irq_stat 0x00400040, connection status changed
[ 18.604872] ata1: SError: { PHYRdyChg DevExch }
[ 18.604890] ata1.00: failed command: WRITE FPDMA QUEUED
[ 18.604911] ata1.00: cmd 61/10:00:80:57:24/00:00:07:00:00/40 tag 0 ncq 8192 out
res 40/00:04:80:57:24/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 18.604960] ata1.00: status: { DRDY }
[ 18.604976] ata1: hard resetting link
[ 21.373511] ata4: softreset failed (1st FIS failed)
[ 21.373551] ata4: hard resetting link
[ 24.178843] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 24.363030] ata4.00: configured for UDMA/133
[ 24.363036] ata4: EH complete
[ 25.701517] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 25.728161] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 25.728741] ata2.00: configured for UDMA/133
[ 25.728745] ata2: EH complete
[ 25.750370] ata1.00: configured for UDMA/133
[ 25.750386] ata1: EH complete
[ 25.792429] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 25.792485] ata4: irq_stat 0x00400040, connection status changed
[ 25.792528] ata4: SError: { PHYRdyChg DevExch }
[ 25.792548] ata4: hard resetting link
[ 25.813052] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 25.813088] ata2: irq_stat 0x00400040, connection status changed
[ 25.813111] ata2: SError: { PHYRdyChg DevExch }
[ 25.813129] ata2: hard resetting link
[ 25.813407] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
[ 25.813463] ata1.00: irq_stat 0x00400040, connection status changed
[ 25.813486] ata1: SError: { PHYRdyChg DevExch }
[ 25.813503] ata1.00: failed command: WRITE FPDMA QUEUED
[ 25.813524] ata1.00: cmd 61/10:00:c0:15:27/00:00:07:00:00/40 tag 0 ncq 8192 out
res 40/00:04:c0:15:27/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 25.813573] ata1.00: status: { DRDY }
[ 25.813588] ata1: hard resetting link
[ 32.881735] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 32.904750] ata2.00: configured for UDMA/133
[ 32.904752] ata2: EH complete
[ 32.934970] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 32.960871] ata1.00: configured for UDMA/133
[ 32.960886] ata1: EH complete
[ 33.011746] ata2: limiting SATA link speed to 1.5 Gbps
[ 33.011751] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 33.011792] ata2: irq_stat 0x00400040, connection status changed
[ 33.011815] ata2: SError: { PHYRdyChg DevExch }
[ 33.011833] ata2: hard resetting link
[ 33.016467] ata1: limiting SATA link speed to 1.5 Gbps
[ 33.016472] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
[ 33.016511] ata1.00: irq_stat 0x00400040, connection status changed
[ 33.016534] ata1: SError: { PHYRdyChg DevExch }
[ 33.016551] ata1.00: failed command: WRITE FPDMA QUEUED
[ 33.016572] ata1.00: cmd 61/10:00:e0:06:27/00:00:07:00:00/40 tag 0 ncq 8192 out
res 40/00:04:e0:06:27/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 33.016620] ata1.00: status: { DRDY }
[ 33.016635] ata1: hard resetting link
[ 35.787058] ata4: softreset failed (1st FIS failed)
[ 35.787098] ata4: hard resetting link
[ 38.912211] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 39.098022] ata4.00: configured for UDMA/133
[ 39.098028] ata4: EH complete
[ 40.081811] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 40.110026] ata2.00: configured for UDMA/133
[ 40.110032] ata2: EH complete
[ 40.138453] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 40.165709] ata1.00: configured for UDMA/133
[ 40.165725] ata1: EH complete
[ 40.224806] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 40.224862] ata4: irq_stat 0x00400040, connection status changed
[ 40.224896] ata4: SError: { PHYRdyChg DevExch }
[ 40.224919] ata4: hard resetting link
[ 40.253699] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen
[ 40.253755] ata1.00: irq_stat 0x00400040, connection status changed
[ 40.253783] ata1: SError: { PHYRdyChg DevExch }
[ 40.253801] ata1.00: failed command: WRITE FPDMA QUEUED
[ 40.253826] ata1.00: cmd 61/10:00:20:0c:27/00:00:07:00:00/40 tag 0 ncq 8192 out
res 40/00:04:20:0c:27/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 40.253875] ata1.00: status: { DRDY }
[ 40.253891] ata1: hard resetting link
[ 40.253971] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 40.254027] ata2: irq_stat 0x00400040, connection status changed
[ 40.254071] ata2: SError: { PHYRdyChg DevExch }
[ 40.254107] ata2: hard resetting link
[ 46.122319] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 46.302501] ata4.00: configured for UDMA/133
[ 46.302506] ata4: EH complete
[ 47.321777] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 47.348350] ata2.00: configured for UDMA/133
[ 47.348355] ata2: EH complete
[ 47.375081] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 47.402082] ata1.00: configured for UDMA/133
[ 47.402099] ata1: EH complete
[ 113.650271] ata4: limiting SATA link speed to 1.5 Gbps
[ 113.650276] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 113.650280] ata4: irq_stat 0x00400040, connection status changed
[ 113.650282] ata4: SError: { PHYRdyChg DevExch }
[ 113.650288] ata4: hard resetting link
[ 119.497457] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 119.674349] ata4.00: configured for UDMA/133
[ 119.674356] ata4: EH complete

user1234 wrote:Hello,
can you describe Mainboard, SATA thanks,
Peter
MoBo: Gigabyte X58A-UD3R
Sata Drives: PCI/PCIe: None Spider.007 wrote:
Hello,
Is it a samsung Also, whenever ID# ATTRIBUTE_NAME 1 Raw_Read_Error_Rate 3 Spin_Up_Time 4 Start_Stop_Count 5 Reallocated_Sector_Ct 7 Seek_Error_Rate 9 Power_On_Hours 10 Spin_Retry_Count 11 Calibration_Retry_Count 12 Power_Cycle_Count 192 Power-Off_Retract_Count 193 Load_Cycle_Count 194 Temperature_Celsius 196 Reallocated_Event_Count 197 Current_Pending_Sector 198 Offline_Uncorrectable 199 UDMA_CRC_Error_Count 200 Multi_Zone_Error_Rate SMART Error Log Version: 1
No Errors Logged
SMART Self-test Num Test_Description # 1 Extended offline # 2 Extended offline # 3 Short offline # 4 Short offline # 5 Short offline # 6 Short offline # 7 Short offline # 8 Short offline ID# ATTRIBUTE_NAME 1 Raw_Read_Error_Rate 3 Spin_Up_Time 4 Start_Stop_Count 5 Reallocated_Sector_Ct 7 Seek_Error_Rate 9 Power_On_Hours 10 Spin_Retry_Count 11 Calibration_Retry_Count 12 Power_Cycle_Count 192 Power-Off_Retract_Count 193 Load_Cycle_Count 194 Temperature_Celsius 196 Reallocated_Event_Count 197 Current_Pending_Sector 198 Offline_Uncorrectable 199 UDMA_CRC_Error_Count 200 Multi_Zone_Error_Rate SMART Error Log Version: 1
No Errors Logged
SMART Self-test Num Test_Description # 1 Extended offline # 2 Extended offline # 3 Short offline # 4 Short offline # 5 Short offline # 6 Short offline ID# ATTRIBUTE_NAME 1 Raw_Read_Error_Rate 3 Spin_Up_Time 4 Start_Stop_Count 5 Reallocated_Sector_Ct 7 Seek_Error_Rate 9 Power_On_Hours 10 Spin_Retry_Count 12 Power_Cycle_Count 184 End-to-End_Error 187 Reported_Uncorrect 188 Command_Timeout 189 High_Fly_Writes 190 Airflow_Temperature_Cel 194 Temperature_Celsius 195 Hardware_ECC_Recovered 197 Current_Pending_Sector 198 Offline_Uncorrectable 199 UDMA_CRC_Error_Count SMART Error Log Version: 1
No Errors Logged
SMART Self-test Num Test_Description # 1 Extended offline # 2 Extended offline # 3 Short offline Last edited your HW configuration
drives, installed PCI / PCIe cards, ...
2X WDC Black 640GB (WD6401AALS ), 1X Seagate ST3500320AS
except for the GPU: 5870
drive and do you have an nvidia card? You might want to read http://ubuntuforums.org/archive/index.p … 38608.html
these sort of errors pop up it might be smart to run a full scan on the drives using smartctl, to make sure the hardware is okay
FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
0x002f 200 200 051 Pre-fail Always - 6
0x0027 201 160 021 Pre-fail Always - 2950
0x0032 095 095 000 Old_age Always - 5644
0x0033 200 200 140 Pre-fail Always - 0
0x002e 200 200 000 Old_age Always - 0
0x0032 078 078 000 Old_age Always - 16415
0x0032 100 100 000 Old_age Always - 0
0x0032 100 100 000 Old_age Always - 0
0x0032 095 095 000 Old_age Always - 5068
0x0032 199 199 000 Old_age Always - 1028
0x0032 199 199 000 Old_age Always - 5642
0x0022 105 094 000 Old_age Always - 42
0x0032 200 200 000 Old_age Always - 0
0x0032 200 200 000 Old_age Always - 1
0x0030 200 200 000 Old_age Offline - 9
0x0032 200 200 000 Old_age Always - 4
0x0008 200 200 000 Old_age Offline - 2
log structure revision number 1
Status Remaining LifeTime(hours) LBA_of_first_error
Completed: read failure 90% 16413 141458831
Completed: read failure 90% 16125 123811039
Completed: read failure 90% 16080 123811039
Completed: read failure 90% 16080 123811039
Completed without error 00% 10771 -
Completed without error 00% 10769 -
Completed without error 00% 10766 -
Completed without error 00% 10765 -
FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
0x002f 200 200 051 Pre-fail Always - 3
0x0027 202 152 021 Pre-fail Always - 2891
0x0032 095 095 000 Old_age Always - 5641
0x0033 200 200 140 Pre-fail Always - 0
0x002e 100 253 000 Old_age Always - 0
0x0032 077 077 000 Old_age Always - 16812
0x0032 100 100 000 Old_age Always - 0
0x0032 100 100 000 Old_age Always - 0
0x0032 095 095 000 Old_age Always - 5413
0x0032 199 199 000 Old_age Always - 1356
0x0032 199 199 000 Old_age Always - 5641
0x0022 106 095 000 Old_age Always - 41
0x0032 200 200 000 Old_age Always - 0
0x0032 200 200 000 Old_age Always - 2
0x0030 200 200 000 Old_age Offline - 3
0x0032 200 200 000 Old_age Always - 0
0x0008 200 200 000 Old_age Offline - 2
log structure revision number 1
Status Remaining LifeTime(hours) LBA_of_first_error
Completed: read failure 90% 16809 120018891
Completed without error 00% 16525 -
Completed without error 00% 16479 -
Completed without error 00% 16479 -
Completed without error 00% 10771 -
Completed without error 00% 10765 -
FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
0x000f 117 099 006 Pre-fail Always - 152860992
0x0003 097 093 000 Pre-fail Always - 0
0x0032 095 095 020 Old_age Always - 5833
0x0033 100 100 036 Pre-fail Always - 0
0x000f 075 060 030 Pre-fail Always - 38796352
0x0032 089 089 000 Old_age Always - 10184
0x0013 100 098 097 Pre-fail Always - 667
0x0032 097 037 020 Old_age Always - 3550
0x0032 100 100 099 Old_age Always - 0
0x0032 100 100 000 Old_age Always - 0
0x0032 100 097 000 Old_age Always - 412323151969
0x003a 100 100 000 Old_age Always - 0
0x0022 067 057 045 Old_age Always - 33 (Min/Max 23/34)
0x0022 033 043 000 Old_age Always - 33 (0 13 0 0 0)
0x001a 021 015 000 Old_age Always - 152860992
0x0012 100 100 000 Old_age Always - 0
0x0010 100 100 000 Old_age Offline - 0
0x003e 200 200 000 Old_age Always - 0
log structure revision number 1
Status Remaining LifeTime(hours) LBA_of_first_error
Completed without error 00% 10183 -
Completed without error 00% 9901 -
Completed without error 00% 4189 -
by ttheodor (2014-01-06 14:17:07)

PXE error during boot

K8T Neo board. (MS6702e)
Just set the BIOS to give me a 'normal' instead of quick boot, and noticed that when it gets to
Intel UNDI PXE 2.0)
Realtek RTL81105 / 81698 gigabyte Ethernet controller v.1.01
Is displays the MAC address, then pauses for some time (about 30 seconds) displaying DCHP... with a slash "/" rotating
then pops up with:
PXE.E53 no boot file name recieved
PXE.MOF exiting PXE ROM
I'm not entirely sure what this means, or if anything is incorrectly loaded / installed. Everything 'appears' to work OK - my only complaint is the length of time is takes to boot - mainly due to the pause at this point

Check your boot sequence... you might have network boot before your hd....
I know sometimes the boot sequence doesn't save correctly. For example, when I save (change) my setting the first time to have my VIA SATA HD boot first, it'll alway changed to network boot. I have to save it the second time to have the setting keep....
Maybe that's the problem for you too...

Error during booting Arch

Similar Messages

Maybe you are looking for