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
LOSETUP(8)						       MAINTENANCE COMMANDS							LOSETUP(8)

NAME
losetup - set up and control loop devices SYNOPSIS
Get info: losetup loopdev losetup -a losetup -j file [-o offset] Delete loop: losetup -d loopdev... Print name of first unused loop device: losetup -f Setup loop device: losetup [{-e|-E} encryption] [-o offset] [--sizelimit limit] [-p pfd] [-r] {-f[--show]|loopdev} file Resize loop device: losetup -c loopdev DESCRIPTION
losetup is used to associate loop devices with regular files or block devices, to detach loop devices and to query the status of a loop device. If only the loopdev argument is given, the status of the corresponding loop device is shown. Encryption It is possible to specify transfer functions (for encryption/decryption or other purposes) using one of the -E and -e options. There are two mechanisms to specify the desired encryption: by number and by name. If an encryption is specified by number then one has to make sure that the Linux kernel knows about the encryption with that number, probably by patching the kernel. Standard numbers that are always present are 0 (no encryption) and 1 (XOR encryption). When the cryptoloop module is loaded (or compiled in), it uses number 18. This cryptoloop module will take the name of an arbitrary encryption type and find the module that knows how to perform that encryption. OPTIONS
-a, --all show status of all loop devices -c, --set-capacity loopdev force loop driver to reread size of the file associated with the specified loop device -d, --detach loopdev... detach the file or device associated with the specified loop device(s) -e, -E, --encryption encryption_type enable data encryption with specified name or number -f, --find find the first unused loop device. If a file argument is present, use this device. Otherwise, print its name -h, --help print help -H, --phash hash_type Specify the password hash function. Valid values are: sha512(default), sha256, sha384, rmd160, none. -j, --associated file show status of all loop devices associated with given file -k, --keybits num set the number of bits to use in key to num. -o, --offset offset the data start is moved offset bytes into the specified file or device --sizelimit limit the data end is set to no more than sizelimit bytes after the data start -p, --pass-fd num read the passphrase from file descriptor with number num instead of from the terminal -r, --read-only setup read-only loop device --show print device name if the -f option and a file argument are present. The short form of this option (-s) is deprecated. This short form could be in collision with Loop-AES implementation where the same option is used for --sizelimit. -v, --verbose verbose mode RETURN VALUE
losetup returns 0 on success, nonzero on failure. When losetup displays the status of a loop device, it returns 1 if the device is not con- figured and 2 if an error occurred which prevented losetup from determining the status of the device. FILES
/dev/loop0, /dev/loop1, ... loop devices (major=7) EXAMPLE
If you are using the loadable module you must have the module loaded first with the command # modprobe loop Maybe also encryption modules are needed. # modprobe des # modprobe cryptoloop The following commands can be used as an example of using the loop device. # dd if=/dev/zero of=/file bs=1k count=100 # losetup -e des /dev/loop0 /file Password: Init (up to 16 hex digits): # mkfs -t ext2 /dev/loop0 100 # mount -t ext2 /dev/loop0 /mnt ... # umount /dev/loop0 # losetup -d /dev/loop0 If you are using the loadable module you may remove the module with the command # rmmod loop RESTRICTION
DES encryption is painfully slow. On the other hand, XOR is terribly weak. Both are insecure nowadays. Some ciphers may require a licence for you to be allowed to use them. Cryptoloop is deprecated in favor of dm-crypt. For more details see cryptsetup(8). AVAILABILITY
The losetup command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/. Linux 2003-07-01 LOSETUP(8)
All times are GMT -4. The time now is 11:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy