Boot fail after system clock changed

Hi!
I've changed the system clock in BIOS, after that I've got an error message.
Grub was loading until reached the /dev/sda3 check and suddenly stopped and asked the root pass.
Unfortunately I wasn't able to type in my pass because of hu_HU charset.
After that I restored the original date and now everything is fine except the date (At the moment the date is: 2009 Monday 17:35:13)
How Can I set up the correct date and what was that error?
I appreciate every help.
Thx.

MadTux wrote:Did you see an error message? Could have been a problem with the file system. I guess if the date in the file system is before the current date, this could cause problems. Why not use ntp? Then you always have the correct time.
That was the problem I guess. I don't know ntp. I was wondering if you'd tell me more about ntp.

Similar Messages

Boot fails after security update

Greetings,
In installed the most recent security update this morning, and after restarting, my machine won't boot up.
I've followed the existing threads (in case you've also had this problem, the most informative was here:
http://discussions.apple.com/thread.jspa?threadID=1545171 )
Here's my machine's current state; I'd appreciate any input!
I booted to single user mode, and checked the disks using /sbin/fsck -fy . there were no errors reported.
I booted from my Install Disk 1, repaired the disk (again, no errors), and verified the disk.
Now, it still does not boot independently; it stalls at the apple logo. Safe boot does not work. It doesn't appear to be a PRAM or SMC issue.
What should my next move be? Thanks again!

There are no guarantees, but following this procedure when installing updates and upgrades on your Mac, or even re-installing them, will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO or security update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.10 to 10.4.11. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta. If Safari 3.1.1 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 3.0.4 (or worse still, version 2) when running 10.4.11 or 10.5 can have repercussions, as Safari 3.1.1 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely, and may entail you having to reinstall an earlier operating system.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• /Library/InputManagers
• ~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).

CRM 5.0 not booting up after IP Address change to Static

Hi Experts:
I really hope that you can help me out with this.
We had/have a CRM 5.0 system, we changed its IP from Dynamic to Static (that went fine). We rebooted the system up (that also went fine)
The next morning we noticed that some of the processes were showing red (in SAP MMC). We waited on that hoping that it would resolve it self.
HOwever, till early evening, the system was still showing red processes. So, we decided to reboot the system up. HOwever, the dispatcher is not starting up. Essentially none of the java applications (SDM, Dispatcher, and Server) are starting up.
I have opened up a ticket with SAP, and they beleive that the issue is with Oracle Listener as that is refusing to recognize the SID from our SAP system.
Since then I have turned off the static IP and tried restarting the CI, but still it continues to give the same error.
During the Disp+Work.exe start up protocol...it continues to show "J2EE status info unavailable".
Have any of you encountered something like this in regards to NetWeaver 2004s or anyother SAP application.
Any help would be appreciated.....
Imran

HI Shaun:
Thanks for your reply, however it is still giving the same error. As requested I am attaching the trace file:
Again..I really appreciate this.
trc file: "dev_disp", trc level: 1, release: "700"
sysno      02
sid        CRM
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    48
intno      20050900
make:      multithreaded, Unicode, optimized
pid        2584
Tue May 23 14:32:51 2006
kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
length of sys_adm_ext is 572 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (02 2584) [dpxxdisp.c   1231]
     shared lib "dw_xml.dll" version 48 successfully loaded
     shared lib "dw_xtc.dll" version 48 successfully loaded
     shared lib "dw_stl.dll" version 48 successfully loaded
     shared lib "dw_gui.dll" version 48 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3902
Tue May 23 14:32:56 2006
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5233]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is active
DpIPCInit2: start server >TWATSCRM1001_CRM_02                     <
DpShMCreate: sizeof(wp_adm)          14080     (1408)
DpShMCreate: sizeof(tm_adm)          3954072     (19672)
DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm)          528064     (1048)
DpFileTableSize: max/headSize/ftSize/tableSize=2000/8/160056/160064
DpShMCreate: sizeof(file_adm)          160064     (72)
DpShMCreate: sizeof(vmc_adm)          14520     (1452)
DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 05EF0040, size: 4783504)
DpShMCreate: allocated sys_adm at 05EF0040
DpShMCreate: allocated wp_adm at 05EF1E28
DpShMCreate: allocated tm_adm_list at 05EF5528
DpShMCreate: allocated tm_adm at 05EF5558
DpShMCreate: allocated wp_ca_adm at 062BAAF0
DpShMCreate: allocated appc_ca_adm at 062C08B0
DpShMCreate: allocated comm_adm at 062C27F0
DpShMCreate: allocated file_adm at 063436B0
DpShMCreate: allocated vmc_adm_list at 0636A7F0
DpShMCreate: allocated gw_adm at 0636A830
DpShMCreate: allocated vmc_adm at 0636A860
DpShMCreate: allocated ca_info at 0636E118
DpShMCreate: allocated wall_adm at 0636E120
MBUF state OFF
DpSesCreateTable: created session table at 063F0040 (len=138424)
EmInit: MmSetImplementation( 2 ).
MM diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
J2EE server info
start = TRUE
state = STARTED
pid = 3192
argv[0] = D:\usr\sap\CRM\DVEBMGS02\exe\jcontrol.EXE
argv[1] = D:\usr\sap\CRM\DVEBMGS02\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\CRM\SYS\profile\CRM_DVEBMGS02_TWATSCRM1001
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=3927
argv[5] = -DSAPSYSTEM=02
argv[6] = -DSAPSYSTEMNAME=CRM
argv[7] = -DSAPMYNAME=TWATSCRM1001_CRM_02
argv[8] = -DSAPPROFILE=D:\usr\sap\CRM\SYS\profile\CRM_DVEBMGS02_TWATSCRM1001
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1617]
***LOG Q0K=> DpMsAttach, mscon ( TWATSCRM1001) [dpxxdisp.c   11349]
DpStartStopMsg: send start message (myname is >TWATSCRM1001_CRM_02                     <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 48
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Tue May 23 14:33:00 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1412
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3929) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3192)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue May 23 14:33:36 2006
ERROR => W0 (pid 1088) died [dpxxdisp.c   13947]
ERROR => W1 (pid 3392) died [dpxxdisp.c   13947]
ERROR => W2 (pid 3560) died [dpxxdisp.c   13947]
ERROR => W3 (pid 3460) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W4 (pid 3972) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W5 (pid 1052) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W6 (pid 2608) died [dpxxdisp.c   13947]
ERROR => W7 (pid 3636) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W8 (pid 424) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W9 (pid 3356) died [dpxxdisp.c   13947]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:46 2006
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long)               Tue May 23 18:33:46 2006
========================
No Ty. Pid      Status Cause Start Err Sem CPU    Time Program Cl User         Action                    Table
0 DIA     1088 Ended         no      1   0             0
1 DIA     3392 Ended         no      1   0             0
2 DIA     3560 Ended         no      1   0             0
3 DIA     3460 Ended         no      1   0             0
4 UPD     3972 Ended         no      1   0             0
5 ENQ     1052 Ended         no      1   0             0
6 BTC     2608 Ended         no      1   0             0
7 BTC     3636 Ended         no      1   0             0
8 SPO      424 Ended         no      1   0             0
9 UP2     3356 Ended         no      1   0             0
Dispatcher Queue Statistics               Tue May 23 18:33:46 2006
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
2
2000
6
6
--------++++--
+
DIA
6
6
2000
6
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id          13
wake_evt_udp_now     0
wake events           total     9, udp     7 ( 77%), shm     2 ( 22%)
since last update     total     9, udp     7 ( 77%), shm     2 ( 22%)
Dump of tm_adm structure:               Tue May 23 18:33:46 2006
=========================
Term    uid man user    term   lastop mod wp ta   a/i (modes)
Workprocess Comm. Area Blocks               Tue May 23 18:33:46 2006
=============================
Slots: 300, Used: 1, Max: 0
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:51 2006
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >TWATSCRM1001_CRM_02                     < (normal)
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes
Stop gateway
killing process (2340) (SOFT_KILL)
Stop icman
killing process (3380) (SOFT_KILL)
Terminate gui connections
wait for end of work processes
wait for end of gateway
[DpProcDied] Process lives (PID:2340 HANDLE:1496)
waiting for termination of gateway ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:52 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:2340 HANDLE:1496)
wait for end of icman
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:53 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:54 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:55 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:56 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:57 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:58 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:33:59 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:34:00 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:34:01 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:34:02 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:3380 HANDLE:1504)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1525
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue May 23 14:34:03 2006
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:3380 HANDLE:1504)
[DpProcDied] Process died (PID:3192 HANDLE:1480)
DpStartStopMsg: send stop message (myname is >TWATSCRM1001_CRM_02                     <)
NiIMyHostName: hostname = 'TWATSCRM1001'
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=562,pac=1,MESG_IO)
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name                    -, type 4, key -
DpStartStopMsg: stop msg sent
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   11633]
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiBufISelUpdate: new MODE -- (r-) for hdl 3 in set0
SiSelNSet: set events of sock 1436 to: ---
NiBufISelRemove: remove hdl 3 from set0
SiSelNRemove: removed sock 1436 (pos=3)
SiSelNRemove: removed sock 1436
NiSelIRemove: removed hdl 3
MBUF state OFF
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/10
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 16)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 3 / sock 1436
NiBufIClose: clear extension for hdl 3
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Em2Cleanup: Cleanup EM2
Eg2Cleanup: Cleanup EG2
Es2Cleanup: Cleanup ES2
Es2ResLocSlotClear: clear slot 0
Es2ResLocSlotClear: clear slot 0
Es2ResLocSlotClear: clear slot 0
Es2ResLocSlotClear: clear slot 0
***LOG Q05=> DpHalt, DPStop ( 2584) [dpxxdisp.c   10022]
Good Bye .....

Yosemite booting fails after erasing and merging bootcamp

I have a MBP 15' retina. I had dual system: mac and windows, but windows failed after upgrading to to Yosemite for obvious reasons so I left it there. Yesterday, I decided to erase my bootcamp and merge it to my mac partition. Everything worked out smoothly as long as I did not reboot. After reboot, Yosemite failed. Here are the symptoms:
Please assist. Thanks

Click on Utilities -> Terminal and post the output of the following Terminal commands. In Recovery console you have to switch between Terminal and Safari.
diskutil list
diskutil cs list
gpt -vv -r show /dev/disk0
fdisk /dev/disk0

First operation confimed - after system allowed changed order qty

Hi,
Production order first operation confimed - after user go change the produciton order qty, how to control this one, we need to config once first operation confirmed can't change the order qty. pls advise
ex : when create production order 10001234 qty 100 pcs, has oper 10,20,30,40
shop floor confirmed operation 10th 100pcs, after user change the qty 200 pcs, how to control this issue? pls
Thanks,
Sankaran

Hi Muthu
No need of exits , this can be done using status profile.
1>Create status profile using BS02.
2>give status no 10 as initial & 20 as the next .
3> in lowest & highest for 10 give as lowest 10 & highest 20 . For status 20 give lowest & hightst both as 20.
4> double click on status 10 & click on create & set what all business transactions u want to allow when the status is 10.
5> double click on 20 & tick on the radio button set against the partial confirmation button so that when the order is partially confirmed the status is automatically set to 20. in this status do not allow change prod order business transaction.
This should solve ur problem . Explore more about status profile in spro>production>SFC> order>create status profile documentation.
Thanks & regards
Prasad
Reward if useful.

Boot Fail after latest BIOS Update on Flex 2-15D

Hi everyone,
I have a severe problem (I guess) after the latest BIOS Update. Windows 7 freezes during startup.
I own a 64-bit Lenovo FLex 2 15D with AMD A6-6310 and R4, 4GB RAM and a SSHD (8GBSSH). I purchased it without OS and installed Windows 7 - which worked fine so far.
I yesterday updated the BIOS with version 9FCN23WW (for Win7 and Win8), the latest BIOS update. A mistake, it seems.
After Reboot, I first had to disable Secure Boot in the BIOS, because it would not let me boot at all. I figured out how to get into the BIOS-Setup to disable this (press Enter 2x, press Tab when in the Boot Menu to access the "Apps Menu", then "SETUP" - just in case this helps someone).
Now Win7 begins to start up, but freezes during the startup process (the splash screen with the win flag freezes and looks a bit strange. I used the "protected mode" Windows Startup and saw that the process always hangs when loading "amdkmpfd.sys".
That is basically it.I guess I have to find a way to re-install the previous version of the BIOS, but I have no idea how!
Any idea?!
Now about what I did to fix this (poor, but I tried):
If I try to start from a Win7 installation CD-ROM (actually it is one for Dell PCs, but I guess that is not the problem) and press a key to boot from CD, Windows loads files, shows "Starting Windows" and at a certain point again just freezes. When I -do not- press a key, WIndows Boot Manager shows up and mentions that "Windows failed to start (etc.)" "File: \EFI\Microsoft\Boot\BCD" "An Error occurred while attempting to read the boot configuration data."
I can't even boot into Linux on a USB stick, because the Windows "Error Recovery" (translated from German, sorry - my guess) won't let me when I try (just offers to boot to Win7 in protected mode - it could be that it fails immediately and jumps back to Win Startup).
Thank you for every bit of help!
Tristam
Solved!
Go to Solution.

I found our the solution to my problem with the help of SebastianLenovo ...
In the BIOS / Boot Mode, I switched back from "UEFI" to "Legacy". That's it. That simple. The BIOS Upgrade routine just did not transfer that setting from the old BIOS to the new.
Given the fact that 1. I did not change that setting, so it is default and 2. it would have been easy to avoid, if the BIOS update routine would be well programmed to transfer the current BIOS settings to the new, upgraded BIOS ...
Anyway a strange situation that a 64-bit system has a 32-bit BIOS. Actually no Linux distribution (except FatDog and rescue systems) are able to deal with it - Linux only running as a Virtual Machine under Windows. I think this is inappropriate and really taking away a part of the fun if you can not run this laptop as a dual boot system.
Thanks to Sebastian and I hope this solution helps someone in the future...
Regards, Tristam.

Boot fails after pacman -Syu

Hi, I did pacman -Syu and after this the system did not boot anymore.
I noticed 2.6.18 kernel files
First I got problem with master boot block
then I got: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
- As proposed in another topics I tried already:
in /etc/fstab
/dev/discs/disc1/part3 / ext3 defaults 0 1
/dev/discs/disc1/part1 /boot ext2 defaults 0 1
/dev/discs/disc1/part2 swap swap defaults 0 0
changed to
/dev/hdd3 / ext3 defaults 0 1
/dev/hdd1 /boot ext2 defaults 0 1
/dev/hdd2 swap swap defaults 0 0
in /boot/grub/menu.lst
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/discs/disc1/part3 ro
changed to
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdd3 ro
initrd /boot/kernel26.img
and now I got:
Booting 'Arch Linux [/boot/vmlinuz26]'
root (hd1,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/hdd3 ro
[Linux-bzImage, setup=0x1400, size=0x2917b71]
initrd /boot/kernel26.img
Error 15: File not found
=============================
- I tried first to change disks/disk1/part3 to change to hdb3 but this failed. then I noticed that a Live boot disk mounted hdd1 hdd2 and hdd3
My bios configuration:
primary IDE controller CD-1
CD-2
secondary IDE controller hd-0 Win
hd-1 Arch
and now I get lost....thanks
fdiks -l tells:
Disk /dev/hdd: 10.2 GB, 10262568960 bytes
16 heads, 63 sectors/track, 19885 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 * 1 66 33263+ 83 Linux
/dev/hdd2 67 587 262584 82 Linux swap
/dev/hdd3 588 19885 9726192 83 Linux

# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdb3 ro
initrd /boot/kernel26.img
changed to
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdd3 ro
initrd /boot/kernel26.img
and now I got:
::Initramfs completed - control passing to kinit
md: Autodetecting RAID arrays
md: autorun ...
md: .. autorun DONE.
this error is gone
Kernel panic - not syncing: Attempted to kill init !
and continues with:
EXT3-fs: mounted filesystem with ordered data mode.
> Archlinux v0.7.2 (Gimmick)
:: Starting UDev Daemon
:: Loading Modules
FATAL: Could not load /lib/modules/2.6.10-ARCH/modules.dep: No such file or directory
shouldn't it be 2.6.18 ?
So it seems that CD on the primary IDE and disks on the Secondary IDE
seems to be a problem for upgrading from v0.7.0 to v0.7.2
Shouldn't I swap the IDE flatcables ?
If I should do this is the kernel26.img right for this new hw configuration ?

NFS mount on boot failing after systemd upgrade

Hello,
after upgrading systemd (208-2 --> 208-3), nfs mount on boot will fail. Tested multiple times. After downgrading back to 208-2, all worked fine.
Output of journalctl --reverse:
Dependency failed for Remote File Systems.
Dependency failed for /mnt/demeter.
Dependency failed for File System Check on /192.168.20.70:/data.
Timed out waiting for device 192.168.20.70:-data.device.
/etc/fstab, the nfs line:
192.168.20.70:/data/ /mnt/demeter nfs4 defaults 0 5
uname -a:
Linux eros 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64 GNU/Linux
I'm using the latest packages (expect grub, it's the version before the current, because of huge ugrade problems, too).
Greetings,
Sebastian

Ah, big thanks. I thought the last column is the mount order, because it's called "pass". I changed it to zero, and now it works.
Greetings,
Sebastian

[SOLVED] Boot failure after system update

Been running nicely for a few months, but after a -Syu update yesterday morning, the boot process fails immediately after the bit about "Processing Udev events", which memory tells me is the point in the boot process where the screen resolution changes up, so it's my video driver I'm suspecting. I'm running a middle-aged PC with a middle-aged nVidia card, which the nouveau drivers have managed very nicely up to this point, but something in the latest kernel seems to be causing mischief. This machine dual-boots Arch with Windows 98; the latter is working just fine, as do other linux distros booted from a live CD, so I'm sure the hardware itself is OK.
After I see the line about processing Udev events, all I get is a completely black screen, but no report of "no signal" from the monitor. No key presses or Ctrl-Alt-Del combinations have any effect.
If I was to post the relevant log file, would some kind soul take a look? I'm no expert AT ALL, so please tell me which one(s) to post!
TIA,
Piers.
Last edited by pierssnell (2012-04-22 13:13:10)

Many thanks -- but I seem to have the same problem in single-user mode. Followed instructions in your second link, appending "single" or "Single" at the end of the "kernel..." line, and then pressing b. Same result as before, it gets as far as the line "Waiting for Udev to process uevents...... [BUSY]" and then screen goes to black.
My other difficulty is, and this is where I start sounding a bit feeble; I can look at errors.log, or everything.log, but it's all rather Greek to me, and even if I see something that makes it quite clear that it is the nouveau driver that needs re-installing, I really don't see how I can re-install the driver if I can't even get as far as a command prompt?
FWIW, I'm seeing in errors.log
"[drm] nouveau 0000:01:00.0: mem timing table length unknown: 14"
... but I've seen that before, and it's never been fatal.

Boot fails after pacman -Suy

Today I tried to refresh my system using pacman -Suy
After reboot I get the following message:
:: Checking Filesystems [BUSY]
/dev/hda4:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <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.
give root password for maintencance
(or type Control-D to continue):
Running e2fsck -b 8193 /dev/hda4
gives the same error message (except the part within asterixes)
Curiously, "fdisk -l" does not give any output at all!
cat /proc/partitions
major minor #blocks name
3 0 58605120 hda
3 1 15727603 hda1
3 2 1 hda2
3 3 104391 hda3
3 4 5245222 hda4
3 5 618471 hda5
3 6 16418398 hda6
3 7 20490876 hda7
cfdisk gives the following error: "FATAL ERROR: Cannot open disk drive"
cat /etc/mtab:
/dev/hda4 / ext3 rw 0 0
/udev /dev tmpfs rw,nosuid 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
cat /etc/fstab
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
sys /sys sysfs defaults 0 0
/dev/hda5 swap swap defaults 0 0
/dev/hda4 / ext3 defaults 0 1
/dev/hda3 /boot ext defaults 0 1
/dev/hda6 /home ext3 defaults 0 1
blkid doesnt give any output either, so I cannot find UUIDs to use in my fstab
the /boot folder is empty, probably hasn't mounted,
but through windows I could locate /boot/grub/menu.lst:
timeout 0
default 0
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,2)
kernel /vmlinuz26beyond root=/dev/hda4 ro
initrd /kernel26beyond.img
Are there perhaps any irregularities in my setup files, I havent been able to spot any
I have tried anything I know!
Can anyone please help me get my system up and running again?
~Quinten

Did you
mount -n -o remount,rw /
When was your last update? What has been updated?
Can you mount your devices with an arch install cd?
Last edited by ZaQ (2010-03-13 16:42:03)

DisplayLink Fails After System Restore

I recently posted that my WIFI failed and after much frustration did a system recovery via the hidden partion. WIFI is all good now, yeah!
But, my Kensington Displaylink (K33926US) fails to function, although it did previously. Kensington support had me try different drivers and none were successful. They finally said that the problem was the computer and I needed to update my graphics display driver.!?
I know this is a software issue since the dock worked a few days ago prior to the recovery. After my last experience I'm very reluctant to do the wrong thing. Plus Kensington did not fill me with confidence.
I'm running NVIDIA 8.17.12.5912 dated 7/26/2010 on a Qosmio X-505-Q894 with Win 7, X64 and SP1.
Any help or ideas are greatly appreciated!

I have no idea what Kensington Displaylink is or how important it is to you. However, I did find a display driver for you to try. It has the same version number but with a later release date, 8/11/10, which normally indicates some kind of change was made after 7/26/10. You can download it from HERE. Good Luck!! I hope it solves your problem.
C.B.
C.B.
Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit

StopWeblogic.sh and startWeblogic.sh fail after weblogic password changed

Hello,
We had to change the password for the weblogic user and after the change the stop start script are failing. I was reading that if boot.properties file is present, the start/stop scripts do not ask for the weblogic credentials. I could see the boot.properties file under the domain directory but the contents are encrypted. How can we resolve this? Any help is appreciated.
Regards.

the simplest solution is
- either delete the boot.properties; weblogic will ask you the credentials at the next start
- or edit manually the boot.properties, inserting non-encrypted values; weblogic will encrypt the password at the next start

[solved] boot fails after recent update

After updating a load of packages today my system fails to boot with the following message:
Checking Filesystems [Fail]
********************Reboot Required*********************
* The System will be rebooted automatically in 15 seconds *
Then it just reboots. I can't get past this message.
I did not upgrade the kernel26-firmware package since I run kernel26-ice 2.6.29.
I can't find any logfiles for hints. What could be wrong?
[Edit 2009-07-06]
I checked the filesystems from a rescue system to no avail.
Last edited by mykey (2009-07-07 09:54:15)

Oh well - took me a while to figure things out this time maybe the solution helps somebody else.
Since I use reiser4 as a filesystem I had to recompile reiser4progs against the new libreadline in order to allow a proper fsck during boot

IDSM-2 not booting up after System Image ugrade

Hi friends,
I had attempted to upgrade the WS-SVC-IDSM2 blade on Cisco 6509 (Sup 720) switch to SW ver 6.0(3) from Maintenence partition 2.1(2) but was unsuccessful. The IDSM-2 was initially running ver 5.1(3).
The file that i tried was WS-SVC-IDSM2-K9-SYS-1.1-a-6.0-3-E1.bin.gz.
I followed the instructions as per the Configuration Guide for Installing System images but still failed on this.
Now, the module fails to boot.
I am only able to log into the maintainence partition after using the command hw-module module 3 reset cf:1.
But I am not able to log into the application partition after using the command hw-module module 3 reset hdd:1.
When i execute show images command in Maintainence partition, i still see the version listed as 5.x.
Running show module on the switch when booting the IDSM-2 in application partition yields the following output:
Mod Ports Card Type Model Serial No.
1 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAD100204GU
2 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL1006CMLY
3 8 Intrusion Detection System WS-SVC-IDSM-2 SAD09440284
4 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1030WDL9
5 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1003ASLQ
<Output truncated>
Mod MAC addresses Hw Fw Sw Status
1 0015.62e1.9eb4 to 0015.62e1.9eb7 2.2 12.2(14r)S5 12.2(18)SXF3 Ok
2 0016.c7a1.0644 to 0016.c7a1.065b 2.3 12.2(14r)S5 12.2(18)SXF3 Ok
3 0012.80f1.7f28 to 0012.80f1.7f2f 6.0 7.2(1) 8.5(0.46)RFW PwrDown
4 0018.7354.b1b0 to 0018.7354.b1df 2.4 12.2(14r)S5 12.2(18)SXF3 Ok
5 0013.c346.c3e8 to 0013.c346.c3eb 4.5 8.1(3) 12.2(18)SXF3 Ok
<Output truncated>
Mod Sub-Module Model Serial Hw Status
1 Centralized Forwarding Card WS-F6700-CFC SAL10019FCU 2.0 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1007DDH2 2.0 Ok
3 IDS 2 accelerator board WS-SVC-IDSUPG ADEI5313870 2.3 PwrDown
4 Centralized Forwarding Card WS-F6700-CFC SAL1028UK0W 2.0 Ok
5 Policy Feature Card 3 WS-F6K-PFC3B SAL1003AVFH 2.2 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL1003AN8W 2.4 Ok
7 Centralized Forwarding Card WS-F6700-CFC SAL1008E7D7 2.0 Ok
Mod Online Diag Status
1 Pass
2 Pass
3 Not Applicable
4 Pass
5 Pass
6 Pass
7 Pass
8 Pass
9 Pass
After I unplug the module from slot and replug it, the module comes online but only boots still into maintenence partition.
I dont have a service account also. Have any of you come across this issue?
Any directions on this will be really appreciated.
Thanks a lot
Gautam

Remove blades from chassis, allowing drive to cool down, this is a known defect that is addressed in software starting with 4.1(4)4

[SOLVED] Boot fails after setting bios time to future

I set my pc clock to wrong year(future) in bios, it worked first time but after a reboot I am getting this error message:
Starting File System Check on /dev/disk/by-uuid/xxxxxxxxxxxxxxxxxxx...
systemd-fsck[299]: storage: Superblock last mount time (Sat Oct 30 17:11:14 2038,
systemd-fsck[299]: now = Wed Oct 30 18:12:01 2013) is in the future.
systemd-fsck[299]: storage: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[299]: (i.e., without -a or -p options)
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): _
In emergency shell, running "systemctl default" and same error shows up again. Running "fsck /dev/sda1" says "/dev/sda1 is mounted\ne2fsck: Cannot continue, aborting.". Umount'ing /dev/sda1 and fsck still says it's mounted. Google doesn't help much with this error.
Last edited by axper (2013-10-30 17:06:56)

That's what I tried:
(emergency shell)
# fsck /dev/sda1
fsck from util-linux 2.24
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
# umount /dev/sda1
# fsck /dev/sda1
fsck from util-linux 2.24
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
Also ran "fsck /dev/sda1" from live cd, rebooted - still the same.

Boot fail after system clock changed

Similar Messages

Maybe you are looking for