Sponsored Content
Operating Systems Linux SuSE Waiting for device /de/sda2 to appear .... not found Post 302344989 by revenna on Tuesday 18th of August 2009 06:54:43 AM
Old 08-18-2009
Waiting for device /de/sda2 to appear .... not found

hi all

Code:
waiting for a device /dev/sda2 to appear:... not found -- device nodes: console disk fb0 full hdc input kmem kmsg loop0 loop1 loop2 loop3 loop4........................................................................................................................................................

sles9 sp2 installation, after 1st reboot it's happening

please help

thanks
revenagj
 

8 More Discussions You Might Find Interesting

1. Programming

tcpdump error: no suitable device found

Hi, I'm trying to use tcpdump for the first time. I installed tcpdump from the rpm. Now when I issue the command tcpdump port 6666, I get an error tcpdump: no suitable device found Can you tell me what's wrong there? Thank, (0 Replies)
Discussion started by: zampya
0 Replies

2. IP Networking

tcpdump error: no suitable device found

Hi, I'm trying to use tcpdump for the first time. I installed tcpdump from the rpm. Now when I issue the command tcpdump port 6666, I get an error tcpdump: no suitable device found Can you tell me what's wrong there? Thanks. (5 Replies)
Discussion started by: zampya
5 Replies

3. BSD

Netbsd root device not found

Hello there. I installed NetBSD yesterday on an older system to try it out. Everytime I boot, I have to enter in the root device (disk) manually wd0 which then proceeds into asking to define the dump device: is the default then, the sbin/init My question is where am I supposed to... (1 Reply)
Discussion started by: septima.pars
1 Replies

4. BSD

Installing FreeBsd. No usb device found

Hello, all. My english is not good. I have a problem installing FreeBsd. I have not CD-Roms, so i use program FlashBoot for convert iso-image to USB Device. After, I was beginning to install FreeBsd (Sorry my english) When it's time to choose an installation media, i select 9 USB:... (3 Replies)
Discussion started by: snet
3 Replies

5. UNIX for Advanced & Expert Users

Gave up waiting for root device.

Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source code and today, I reboot the system with "crashkernel=64M@16M". The system cannot boot now and... (0 Replies)
Discussion started by: liklstar
0 Replies

6. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

7. Ubuntu

Cannot access or boot encrypted drive (gave up waiting for root device...)

I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before. When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies

8. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
MEM(4)							     Linux Programmer's Manual							    MEM(4)

NAME
mem, kmem, port - system memory, kernel memory and system ports DESCRIPTION
mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even patch) the system. Byte addresses in mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned. Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file kmem is the same as mem, except that the kernel virtual memory rather than physical memory is accessed. It is typically created by: mknod -m 640 /dev/kmem c 1 2 chown root:kmem /dev/kmem port is similar to mem, but the I/O ports are accessed. It is typically created by: mknod -m 660 /dev/port c 1 4 chown root:mem /dev/port FILES
/dev/mem /dev/kmem /dev/port SEE ALSO
chown(1), mknod(1), ioperm(2) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 1992-11-21 MEM(4)
All times are GMT -4. The time now is 10:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy