- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: problem in Linux Startup
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2006 09:19 PM
тАО08-06-2006 09:19 PM
"Uncompressing Linux....ok, booting the kernel.
audit(1154959027.963:0):initialized
Redhat nash version 4.1.18 starting
WARNING: can't access (null)
exec of init ((null)) failed!!!: 14
unmount /initrd/dev failed:2
Kernel panic-not syncing: Attempted to kill init!"
kindly help me out in this regard so ill be thankful..waiting for ur reply....
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2006 09:59 PM
тАО08-06-2006 09:59 PM
Re: problem in Linux Startup
unfortunatly I'm not such expert...
here is some documentation which may help
http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/initrd.html
http://www.faqs.org/docs/evms/x3834.html
anyway if it's not necesery to have this distribution I would try anotherone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2006 03:55 AM
тАО08-07-2006 03:55 AM
Re: problem in Linux Startup
"? ?? ?? ?? etc"
"? ?? ?? ?? root"
and all the rest fs are fine
kindly help me in this regards...thankyou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2006 11:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2006 10:25 PM
тАО08-08-2006 10:25 PM
Re: problem in Linux Startup
# cp /boot/initrd-
#mkdir initrd
#cd initrd
#cpio -cid -I ../initrd-
#cat init (this script execute many instructions to boot) and verify the instructions in this script.
Best Regards...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 06:20 AM
тАО08-09-2006 06:20 AM
Re: problem in Linux Startup
?? ?? ?? ? ? ? ? etc
?? ?? ?? ? ? ? ? root
so now my question is i want that these two files in their orignal position as in etc the are devices and while etc is crrupted it is not mounted those fs through fstab and there is in initrd it is showing errors so kindly help me out in this regards as i also dont have any backup .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 10:04 AM
тАО08-09-2006 10:04 AM
Re: problem in Linux Startup
/etc on the other hand IS painful. ALL configuration data is over there and without backup.... The next step depends very much on the file system you have chosen for the root partition. If it is ext3 (RH default option), I suggest to run fsck using the "alternate superblock" (-b) option. For proper usage of this tool it is mandatory to read the fsck.ext3 man page.
In my opinion however, I think it would take less time to copy the /etc directory from another computer and to carefullly adjust it to your needs. I for one would go this way. The reason is that, even if you recover the lost info from the original /etc, you will still need to verify each and every recovered file.