Root Node not found in Data Object

Hello Everybody,
When I create Data Objects in MI Server, I am not able to see the root node.
I could find Backend Adapter and Flow Definition, but not the Root node.
Can someone tell me what I am doing wrong. Please help me.
Thanks,
Sneha Singh.

Hi,
The problem is because of your BAPI signature only.
The tables parameter of getList and importing parameter of getDetail should be of same structure.
i.e.)
FUNCTION ZBAPI_CUST_GETLIST.
""Local Interface:
*" EXPORTING
*"     VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*"      ZCUST_DET STRUCTURE ZCUST_DET
FUNCTION ZBAPI_CUST_GETDETAIL.
""Local Interface:
*" IMPORTING
     *VALUE(BAPIKUNNR) LIKE ZCUST_DET-CUSTOMER*
*" EXPORTING
*"     VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*"      ZBAPI_ORDERS STRUCTURE ZBAPI_ORDERS
Change this and try. If its not working then include your header structure as exporting parameter in getDetail
i.e)
FUNCTION ZBAPI_CUST_GETDETAIL.
""Local Interface:
*" IMPORTING
*"     VALUE(BAPIKUNNR) LIKE ZCUST_DET-CUSTOMER
*" EXPORTING
*"    VALUE(ORDER) LIKE ZCUST_DET STRUCTURE ZCUST_DET
*"     VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*"      ZBAPI_ORDERS STRUCTURE ZBAPI_ORDERS
Regards,
Dhana
Edited by: Dhanasekhar Karuppanan on Aug 21, 2009 9:54 AM
Edited by: Dhanasekhar Karuppanan on Aug 21, 2009 9:55 AM
Edited by: Dhanasekhar Karuppanan on Aug 21, 2009 9:55 AM

Similar Messages

Requested node not found in configuration file

The following warning appears when I instantiate the ReportClientDocument object:
[main] WARN com.businessobjects.reports.sdk.JRCCommunicationAdapter - Requested node not found in configuration file
This looks to me like a configuration issue. How can I get rid of it?

Please read the rules of engagement and add all of the missing info. I'm assuming you are developing in Java so moved your post to the Java forum.

REP-1070 Object not found in the object store ...

When trying to open an report file (.rdf) in Reports 6 it won't open. I get the error REP-1070 Error while saving or opening ... Object not found in the object store.
I know that in the report there is an OLE object, is that the problem? How can I save the source code when I can't open the file?
Please help!
/Linda

Hi vdha,
Try this..
Get the user account under which the host instance for the send port is configured.
Log-off from your server. Log back in using the service account. The account which is been used in the host instance.
Go to MMC..Select “My User Account” as opposed to “Computer account” as you did.
The import the certificate under “Personal “ folder and “Trusted Root Certification Authorities ”
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

W25 The Characteristic %NV% is not found in data provider ...

Hi Gurus,
we are currently starting to use the BI Portal. I want to publish a Query, which really works fine in BEx Analyzer, in the Portal using a Web Template.
So I used the BEx Web Application Designer to create a Template where I just inserted the Analysis Item with my data provider.
In BEx Web Application Designer I get the warning "W25 The Characteristic %NV% is not found in data provider XXX" - and when I open my Query in the Portal I get the dump message
"ERROR RS_EXCEPTION (000): SQL0104N An unexpected token """" was found following "'1' AND "I"."SVER" =". Expected tokens may include: "<space>". SQLSTATE=42601
MSGV1: SQL0104N An unexpected token """" was found
MSGV2: following "'1' AND "I"."SVER" =". Expected tokens
MSGV3: may include: "<space>". SQLSTATE=42601
ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION".
Does anybody have an idea what's the problem? Please?
Thank in advance!

Sandra,
If you are not on SPS-14 try applying this note
1122372.
Please assign points if helpful.
Thanks,
Bobby

RMAN receives: OSB error: UUID not found OB cached object manager

I am receiving an error when backing up :
Starting backup at 17-MAR-2009 10:00:00
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=137 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Oracle Secure Backup
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DGROUP1/seattle/datafile/system.826.679693097
channel ORA_SBT_TAPE_1: starting piece 1 at 17-MAR-2009 10:00:02
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 03/17/2009 10:02:57
ORA-27191: sbtinfo2 returned error
Additional information: 2
ORA-19511: Error received from media manager layer, error text:
sbt__rpc_cat_query: Query for piece 07ka4pt2_1_1 failed.
*(Oracle Secure Backup error: 'UUID not found (OB cached object manager)').*
Prior to this (when everything was working) I merely tried to re-label a tape. Why this has caused the problem I do not know but I can't seem to fix it.
Does anybody know what has happened and what the fix is?
On the HTTP administration page, when I try to configure the device I get the following error message:
Error: cannot read location object associated with device - UUID not found
It looks as though the device definition has been corrupted some how.

The fix has been found (from Oracle Support). The cause is not yet understood.
I document it here for others who may run into the same problem.
It seems that the device "went missing". The fix was to add it.
ob> mkloc dat72
It is still being investigated and I will update the notes when I am in possession of more information.

SourceSet in function (Jscript) not found any Data View

HI,
I have the code:
var = oDB xfa.sourceSet.DataConnection.clone (1);
oDB.nodes.item (1). query.setAttribute ("text", "CommandType");
oDB.nodes.item (1). query.select.nodes.item (0). value = "SELECT * FROM vw_products";
oDB.open ();
oDB.close ();
This code works perfectly if I call in initialize the form.
(form1.Inicial::initialize - (JavaScript, both))
But the same code does not work if I call a function in Jscript, (Function test {} for example). Not found "sourceSet.DataConnection".
Any idea what could be? I've tried everything but it only works if i put in initialize the page.

And a further example from my library of examples, just to help you out...
SQL> CREATE OR REPLACE TYPE num_descript AS OBJECT(num number, descript varchar2(30))
2 /
Type created.
SQL> CREATE OR REPLACE TYPE tbl_num_descript AS TABLE OF num_descript
2 /
Type created.
SQL> CREATE OR REPLACE PACKAGE reftest AS
2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED;
3 END;
4 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY reftest AS
2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED IS
3      v_obj num_descript := num_descript(NULL,NULL);
4      v_rc sys_refcursor;
5    BEGIN
6      IF p_choice = 1 THEN
7        OPEN v_rc FOR SELECT empno as num, ename as descript FROM emp;
8      ELSIF p_choice = 2 THEN
9        OPEN v_rc FOR SELECT deptno as num, dname as descript FROM dept;
10      END IF;
11      LOOP
12        FETCH v_rc INTO v_obj.num, v_obj.descript;
13        EXIT WHEN v_rc%NOTFOUND;
14        PIPE ROW(v_obj);
15      END LOOP;
16      CLOSE v_rc;
17      RETURN;
18    END;
19 END;
20 /
Package body created.
SQL> select * from table(reftest.pipedata(1));
       NUM DESCRIPT
      7369 SMITH
      7499 ALLEN
      7521 WARD
      7566 JONES
      7654 MARTIN
      7698 BLAKE
      7782 CLARK
      7788 SCOTT
      7839 KING
      7844 TURNER
      7876 ADAMS
      7900 JAMES
      7902 FORD
      7934 MILLER
14 rows selected.
SQL> select * from table(reftest.pipedata(2));
       NUM DESCRIPT
        10 ACCOUNTING
        20 RESEARCH
        30 SALES
        40 OPERATIONS

ADK Installation root registry not found?

Hi,
I am trying to image some machines in one location and for some reason we aren't able to. Basically it just PXE boots, finds it in the collection and then it is stopped with a command prompt open "x:\sms\bin\x64>" and doesn't do anything after
that.I checked the SMS log and all I see is the following:
ADK installation root registry value not found.
Loaded C:\Windows\system32\wimgapi.dll
Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Any ideas or anything else I can check? TIA

Yes, see below TIA
<![LOG[Found new image LIA00004]LOG]!><time="13:43:59.968+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.046+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim
PackageID: LIA00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00005]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim
PackageID: LIA00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00095]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim
PackageID: LIA00095
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0016A]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim
PackageID: LIA0016A
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA001F4]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim
PackageID: LIA001F4
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00231]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim
PackageID: LIA00231
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00269]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim
PackageID: LIA00269
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00276]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim
PackageID: LIA00276
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00288]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim
PackageID: LIA00288
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0029B]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Begin validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context=""
type="1" thread="6000" file="ccmcert.cpp:1662">
< ![LOG[Completed validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE"
context="" type="1" thread="6000" file="ccmcert.cpp:1803">
< ![LOG[PXE Provider finished loading.]LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="smspxe.cpp:184">

[SOLVED] Kernel panic at boot due to root FS not found

When I try to boot using a new kernel version (eg. 3.0.1 or 2.6.39), I get a kernel panic with an "init not found" error message. I haven't been able to get any more detailed error messages, but I assume that there's a problem with finding or mounting my root filesystem.
For now, I'm stuck with 2.6.38.7-1, which boots without any problems. (I keep trying the new kernel, then rolling it back using a Live CD.)
I have a shared EXT4 root and boot partition, and I'm using Grub 0.97. Other than that, I'm not sure what information would be helpful in tracking down this problem, and any help would be appreciated.
Last edited by dcecile (2011-08-10 00:41:46)

No problem.
Here's my full Grub. It has a lot of trial-and-error entries, and I made *-old copies of my 2.6.38 kernel files:
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
# general configuration:
timeout 2
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
title Arch Linux
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux.img
title Arch Linux Fallback
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux-fallback.img
title Arch Linux Ext4
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux-ext4.img
title Arch Linux Log
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/initramfs-linux.img
title Arch Linux Break
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro rootwait break=y panic=30 vga=0x318
initrd /boot/initramfs-linux.img
title Arch Linux Nonboot Log
root (hd0,2)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /initramfs-linux.img
title Arch Linux Baduuid Log
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/1ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/initramfs-linux.img
title Arch Linux LTS
root (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-lts.img
title Arch Linux LTS Fallback
root (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-lts-fallback.img
title Arch Linux LTS Log
root (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/kernel26-lts.img
title Arch Linux Old
root (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old.img
title Arch Linux Old Fallback
root (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old-fallback.img
title Arch Linux Old Log
root (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/kernel26-old.img
title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1
This is the 3.0 entry that doesn't work:
title Arch Linux
root (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux.img
And this is the 2.6.38 entry that does work:
title Arch Linux Old
root (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old.img
Here's "lsinitcpio /boot/initramfs-linux.img":
./etc
./etc/udev
./etc/udev/udev.conf
./etc/modprobe.d
./etc/modprobe.d/usb-load-ehci-first.conf
./init
./init_functions
./bin
./bin/busybox
./sys
./proc
./dev
./hooks
./hooks/udev
./run
./config
./usr
./usr/bin
./usr/sbin
./lib
./lib/udev
./lib/udev/usb_id
./lib/udev/firmware
./lib/udev/scsi_id
./lib/udev/path_id
./lib/udev/ata_id
./lib/udev/rules.d
./lib/udev/rules.d/50-udev-default.rules
./lib/udev/rules.d/80-drivers.rules
./lib/udev/rules.d/50-firmware.rules
./lib/udev/rules.d/60-persistent-storage.rules
./lib/modules
./lib/modules/3.0-ARCH
./lib/modules/3.0-ARCH/modules.alias.bin
./lib/modules/3.0-ARCH/modules.symbols.bin
./lib/modules/3.0-ARCH/kernel
./lib/modules/3.0-ARCH/kernel/fs
./lib/modules/3.0-ARCH/kernel/fs/ext4
./lib/modules/3.0-ARCH/kernel/fs/ext4/ext4.ko.gz
./lib/modules/3.0-ARCH/kernel/fs/mbcache.ko.gz
./lib/modules/3.0-ARCH/kernel/fs/jbd2
./lib/modules/3.0-ARCH/kernel/fs/jbd2/jbd2.ko.gz
./lib/modules/3.0-ARCH/kernel/sound
./lib/modules/3.0-ARCH/kernel/sound/core
./lib/modules/3.0-ARCH/kernel/sound/core/seq
./lib/modules/3.0-ARCH/kernel/sound/core/seq/snd-seq-device.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/core/snd.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/core/snd-rawmidi.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/soundcore.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers
./lib/modules/3.0-ARCH/kernel/drivers/ata
./lib/modules/3.0-ARCH/kernel/drivers/ata/libata.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/ata/ahci.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/ata/libahci.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb
./lib/modules/3.0-ARCH/kernel/drivers/usb/core
./lib/modules/3.0-ARCH/kernel/drivers/usb/core/usbcore.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb/host
./lib/modules/3.0-ARCH/kernel/drivers/usb/host/uhci-hcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb/host/ehci-hcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video
./lib/modules/3.0-ARCH/kernel/drivers/video/backlight
./lib/modules/3.0-ARCH/kernel/drivers/video/backlight/lcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/fb_sys_fops.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/sysimgblt.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/syscopyarea.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/sysfillrect.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/input
./lib/modules/3.0-ARCH/kernel/drivers/input/ff-memless.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/scsi
./lib/modules/3.0-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ezkey.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sjoy.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gyration.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-samsung.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-lcpower.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kye.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-dr.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-wacom.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-keytouch.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-uclogic.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cherry.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kovaplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zpff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-elecom.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-common.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-arvo.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-waltop.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-pyra.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-picolcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-twinhan.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-emsff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sunplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-apple.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-topseed.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-chicony.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-magicmouse.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cypress.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kensington.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kone.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-axff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-multitouch.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-logitech.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-petalynx.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-prodikeys.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid
./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid/usbhid.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sony.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zydacron.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-koneplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gaff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-microsoft.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-monterey.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ntrig.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-belkin.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-pl.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-a4tech.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ortek.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-quanta.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-tmff.ko.gz
./lib/modules/3.0-ARCH/kernel/lib
./lib/modules/3.0-ARCH/kernel/lib/crc16.ko.gz
./lib/modules/3.0-ARCH/modules.dep.bin
./sbin
./sbin/blkid
./sbin/udevadm
./sbin/modprobe
./sbin/udevd

Node not found in SPRO IMG

Hi All,
In SPRO transaction Time Management-->Web Applications->leave request(new)-> node text not found
I am not able to find all the three subnodes under the node leave request (new)
It is displayed as node text not found .whenever we execute these nodes it gives out an error as "there are no executable transactions assigned to this node".
These nodes are available in the development server but not available on test server.we have already activated the BC sets through SCPR20 and found the activation log successful for all EA-IMG, EA-AKH,EA-MENU.
Also activated the switch EA-HR.and ours is not an upgraded system(.4.7)
Please Help to the earliest possible as it is very urgent for us.
Regards,
Jyothi.R

Hi, If the client where you have the problem has been copied from a different one, it may be a problem with the translation of texts:
Check this note :
Texts of hierarchy enhancements not transported
SAP Note Number: 204433
Symptom
Enhancements were added to a hierarchy (for example area menu) whose language is not the original language of the hierarchy. In the system in which the enhancements were added, all entries are displayed correctly. After a transport to a different system, the texts of the added enhancements are missing in this system. In the display or maintenance of the corresponding hierarchy the message 'Node text not found' is issued. In the Easy Access no message at all is displayed.
Additional key words
Area menus, enhancements, transport, IMG
Cause and prerequisites
Due to a program error, the texts of a hierarchy are only transported in the original language even if enhancements were made in other languages.
Solution
Implement the attached correction.
Regards
Jose Luis Valverde

Member In Outline, Not Found During Data Load

I am exporting data from DatabaseA (zero level export in columns to a text file) using MaxL. I then to import this data (using MaxL) into Database B on another server but which has the same exact outline. We set this up about 3 weeks ago and the export import scripts run every day and have been working fine. However today I got an error while loading members into Database B, 3 members were not able to load:
Member 73997612 Not Found In Database
Member STCR Not Found In Database
Member 22-340101 Not Found In Database
Initially I thought that these 3 members got added to DatabaseA, and were therefore in the export file and probably didn't exist in Database B. However when I went to database B and did a "find members" on the outline, all 3 members are there. Just a note that they had been added manually, but were added.
Then I thought maybe they had been added in the wrong dimension. I checked the location of the above three members in Database A, and they were added in the same location in the hierarchy in Database B.
So if the members exist in Database B and are not in the wrong location, why can't they be loaded to Database B ?
I also wanted to add that there seemed to be several data values which existed for these members. I am guessing they came from the export.
Version is 11.1.2.1. OS = Oracle Enterprise Linux
Has anybody encountered an issue like this before ? I don't think it has to do with the member names, they seem to fit syntax requirements PLUS they are exported from the production database.
Thanks in advance
Edited by: EssbaseApprentice on Feb 9, 2012 11:12 AM
Edited by: EssbaseApprentice on Feb 9, 2012 11:54 AM

Check member names are exactly same( Without any extra spaces, spellings etc...)
Check storage type

[PPC] new install fails to boot: root partition not found

Hi,
new ArchPPC installation on a iMac G3. It does not boot further than initramfs because root partition is not found. I get something like:
Root device /dev/sda4 doesn't exist
Attempting to created it
ERROR: unable to determine major/minor number of root device /dev/sda4
then I get a dropbox recovery console but keyboard doesn't work.
I chroot in the installed system to change mkinicpio pata hook to ide, regenerated initramfs but that didn't help.
Any guidance to diagnose and solve this issue would be greatly appreciated.

Hi, sorry I just realized you replied to my thread.
I don't have my mac at the moment, but I must have done something like :
- boot the live CD
- get the output of lsmod
- copy this output to mkinitcpio.conf (the one that's on your HD), remove the autodetect hook
- chroot into your HD setup
- regenerate initramfs
- update yaboot (is this really mandatory?)
- exit chroot and reboot.

Page not found for: Oracle10g Objects for OLE Documentation

I just open "Oracle Objects for OLE Documentation" on
http://www.oracle.com/technology/docs/tech/windows/ole/index.html, but can not open
"Oracle10g Objects for OLE Documentation" with link http://www.oracle.com/technology/pls/db10g/db10g.to_toc?pathname=win.101%2Fb10118%2Ftoc.htm&remark=portal+%28Books%29
and got this "Sorry, this page was not found".

Hi Ferrvanto,
Apologies for the delay responding to you.
Unfortunately the location to which the link points is a decommissioned server, whose contents can no longer be retrieved.
Please try our documentation pages at: http://www.oracle.com/technology/documentation/index.html
Regards,
Les

[Solved] - Root device not found - Unable to boot!

Before posting links to other threads or to the pacman/mkinitcpio wiki page please go through the following.
I know that many others are facing a similar problem, but I am posting this after spending 8+ hours (in 2 days) trying to get my system to boot.
And worst of all I don't have a working CDROM so I have to boot via an iso on a pendrive which is very frustating.
The exact message I get after the GRUB menu is:
ERROR: resume: hibernation device '/dev/sda3' not found
ERROR: Unable to find root device '/dev/disk/by-uuid/...'
You are being dropped to a recovery shell.
Type exit to try and continue booting
Now I have already tried the following, by chrooting into my system:
1. As per the pacman wiki page, boot via live arch, chroot and run full upgrade. Then reinstall udev followed by mkinitcpio and then remake the image.
2. Downgrading to linux-3.3.4-2, udev-182-2x86-64 and mkinitcpio-0.8.8-1
3. Rearranging hooks in mkinitcpio.conf (usbinput before udev), and adding ext4 to MODULES array. Done this in both downgraded version and new kernel version (3.3.8-1)
After trying various permutations and combinations, I have failed and haven't been able to get past the first 8 lines after the grub menu.
An important point to note:
I had used the --force switch for 1 more package other than filesystem while updating which I don't remember now. I had to use it because some packages had gotten corrupted while downloading and I had to upgrade in parts. Also at no point during any of these trials did I get an error while rebuilding the initrd image.
If I remove the resume hook in /etc/mkinitcpio.conf then the first line "ERROR: ... " changes saying that "no hibernation device specified".
Please suggest anything if you can!
Last edited by theta (2012-06-15 15:44:15)

ewaller wrote:
Do you know the partition that is supposed to be your root partition?
Grub cannot find it by its UUID. Reboot, at the grub menu, highlight the kernel you want to boot, and press 'e'. You are dropped into a simple editor which will allow you to change the boot command. Replace references to /dev/disk/by-uuid/... with /dev/sdan, when n is the root partition number.
One other possibility. Does your system have multiple drives? Any chance the BIOS could be swapping them ? (On second thought, that would not break UUID, But... it is something to be aware of using the technique I proposed)
If you do not know the partition arrangement, use that limited recover shell you mentioned to go look around and determine it.
Hmm, Thanks for this advice but I can't help saying that I'm not a noob .
Somehow the problem resolved itself with the new kernel update which came about half an hour ago (3.4.2-2). Suppose it will remain a mystery now!

[SOLVED]kexec into arch fails : root device not found

Hello,
I have a fresh arch install with only base, base-devel and openssh.
I boot on penbuntu, at this point I can see my devices in /dev.
Then I mount my root arch partition on /mnt/rootfs and do :
kexec --load /mnt/rootfs/boot/vmlinuz-linux --initrd=/mnt/rootfs/boot/initramfs-linux.img --command-line="root=/dev/sda3 ro vesa video=vesafb"
which returns :
setup_linux_vesafb: 1280x720x32 @ 10028000 +708000
I then do kexec -e, It seems to start loading the kernel since the screen is cleared and each time it does
[0.845500] i8042: No controller found
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3' /
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
I tried everything as root in the kexec --command-line, root=LABEL, root=UUID but it always do exactly the same thing, waits for 10s for device and then ERROR and drops to the recovery shell.
Any idea of what's going on ? Why can't it see devices ?
EDIT : If that can help, the kernel from which I am kexecing is 2.6.24.3 and If I try to just chroot I notice :
mount -t proc proc proc/
mount -t sysfs sys sys/
Works but when I :
mount -o bind /dev dev/
It returns :
mount: mounting /dev on dev/ failed: Invalid argument
So somehow I think when the kernel loads it has trouble passing the /dev along and therefore sees no devices. But I still can't figure out what to do.
Thanks in advance
Last edited by Nolhian (2012-07-28 17:47:30)

I can't because I'm booting on penbuntu and not arch linux. Anyways the command used in the wiki is similar to the one I'm using.

[Solved] kernel 2.6.27 - Root device not found (2.6.28 too)

since the last kernel update, my ArchLinux won't boot anymore, as it seems to be unable to find the root partition "/dev/sda5". The exact output is:
:: Loading root filesystem module...
Attempting to create root device '/dev/sda5'
ERROR: Failed to parse block device name for '/dev/sda5'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
Waiting for devices to settle...done.
Root device '/dev/sda5' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda5'
ERROR: Unable to create/detect root device '/dev/sda5'
Dropping to a recovery shell... type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/sda5' gets created while you are here,
try adding 'rootdelay=8' or higher to the kernel command-line
ramfs$
What I have tried:
1.- I have booted with an old Ubuntu LiveCD, and /dev/sda5 seems to be working and healthy, as it mounted flawlessly while in Ubuntu.
2.- I have also found that not even /dev/sda is created from the fallback recovery shell so, obviously, there is no root device to create.
3.- None of the suggested kernel command-line parameters worked: 'rootfstype=ext3' and/or 'rootdelay=8'(I mean, using them separately or both in the same kernel GRUB line) didn't give any positive result, or any behavior change.
And now, two questions:
1.- How can I fix this?
2.- If it's not possible, how can I downgrade the kernel from a LiveCD? I suppose this is possible by booting an ArchLinux LiveCD, chrooting my '/dev/sda5' finding a 2.26.X kernel pacman package and installing, but I'm almost iliterate in kernel issues, and some help would be nice.
Thank you all in advance!
EDIT: Oh, I have also waited for some time to see if the hard disk gets ready after the failed booting proccess but it seems it doesn't, so 'rootdelay=8' wouldn't help anyway, just to give some more details about the problem.
Last edited by 4s|m3tr|ko0 (2009-01-21 10:14:32)

4s|m3tr|ko0 wrote:
ballon wrote:It seems like my problems can be the same, however I haven't managed to solve it myself so if you can be more detailed that would be nice.
Of course I can, it's quite easy.
First of all, you have to boot from an Archlinux install CD, to have an usable environment. Once you have booted, I will assume a couple of things to make the examples, which are:
"/dev/sda2" is the root partition where the system is currently installed but not booting.
"/dev/sda1" is the boot partition (not needed if you don't have a separated boot partition, obviously).
"/mnt/myarch" is the directory where sda1 will be mounted on the live session.
The kernel version on sda2 is "2.6.27-ARCH", you can find which kernel versions are installed on sda2 by checking the directory names under "/lib/modules/"
Next you have to mount your root partition on any directory and mount the "boot" partition if you have one too:
mkdir /mnt/myarch #Creates the mount directory on the live session, you can use /mnt/ so this command is not neccesary
mount -t auto /dev/sda2 /mnt/myarch #Mount the root partition on the live session
mount -t auto /dev/sda1 /mnt/myarch/boot #Mount the boot partition, if you have to
Now, you'll have to bind three system directories to their true locations on the root partition:
mount -t proc proc /mnt/myarch/proc
mount -t sysfs sys /mnt/myarch/sys
mount -o bind /dev /mnt/myarch/dev
Next step is to use the command "chroot <target> <consolebin>" to "move" the system root to the <target> directory, using the <consolebin> command interpreter:
chroot /mnt/myarch/ /bin/bash
Now, you will be using your system just like if you had actually booted from your hard disk, but running the kernel from the liveCD, so the only remaining step is to generate the initcpio image.
In the example for this step, I will run the mkinitcpio twice, the first one to check that it's correctly generated, and the second to install it, using the parameter "-g". Another thing to keep in mind is that even before chrooting, the liveCD kernel is still running, so you will have tu use the "-k <kernelversion>" parameter to manually specify the kernel to use. Otherwise, mkinitcpio won't be able to find the correct modules to use:
mkinitcpio -k 2.6.27-ARCH #This will simulate the generation, if it runs fine, run the next command
mkinitcpio -g /boot/kernel26.img -k 2.6.27-ARCH #This will actually generate the image
And that's all, this should regenerate a default image. More info about mkinitcpio: http://wiki.archlinux.org/index.php/Mkinitcpio
Hope this heps
PS: Sweden, nice country .
I follow this guide and I saved my Arch installation. I don't know why the HOOKS array in my mkinitcpio.conf just contains "base" :-?
So, just before regenerate the ramdisk image I edit my /etc/mkinitcpio.conf and add all the neccessary hooks and generate. I can bring my Arch box back to life

Root Node not found in Data Object

Similar Messages

Maybe you are looking for