Recently, I created a device sc0 through device mapper. The divice could be found in /dev/mapper/sc0. My problem is that the device doesn't exist in /dev/partitions which will block my following test.BTW, I found dm-0 in /dev/partitions. Is it the same as /dev/mapper/sc0? But the device /dev/dm-0 doesn't exist!
View 2 RepliesI've got the F13 LiveCD that I was able to boot and use using the "nomodeset" boot option. From the desktop I'm trying to perform an Install to Hard Drive. I've read the Install from LiveCD post regarding the creation of a /boot partition and a / root partition. I've tried creating them without the LVM group and with. But every time I appempt to install I get...
An error occurred mounting device proc as /proc: mount failed: (9, None). This is a fatal error and the install cannot continue.
Hardware is a Sager 8887 (P4, 3.06HT, 60GB HDD, Radeon 9000 graphics adapter)
Dell PowerEdge R610 with QLogic HBA card connected to HP EVA6000 SAN through a pair of switches.When I present space to the server, device mapper doesn't see it unless I restart the multipathd service. Same thing with unpresenting - the /dev/mapper/mpatha does not go away unless I restart multipathd.Here's what it looks like in 'multipath -ll' before and after I unpresent the LUN (without restarting multipathd)...
== BEFORE ==
# multipath -ll
mpathb (3600508b40010716b0000900001a40000) dm-8 HP,HSV200
[code]....
I'm facing a problem on Boot on San installation, Os is installed, now I'm trying to define mapper device
for others lun/disk with alias for multipath references
Code: # pvcreate /dev/dm-14 /dev/mapper/disk_bin_rac
Device /dev/dm-14 created
[code]....
Slackware 13 Kernel 2.6.29.6 have three hard drives. Root is on own drive sda1. sdb and sdc are raid via mdadm with two partitions. one for /home raid0 md0 one for swap raid1 md1. md0 is encrypted vi cryptsetup. md1 is encrypted vi fstab. everything boots fine and is accessible. However, /dev/mapper/* shows sda1 as block device connected to the raid md0. swap crypted device is correct in /dev/mapper/*. fstab is set correctly. problem seems to be with initrd. I would like the correct device in /dev/mapper so that I can access drive info; size, available space, etc. now info shows only sda1 info
View 1 Replies View RelatedI am trying to prevent the dm_mod and friends from loading during install.I am installing by PXE boot with NFS and kickstart files over http. This works fine for other machines.Ok, I have a Dell PowerEdge 2900 III with 8gig ram, PERC 6/i raid controller.The raid has 8 1TB drives in it, so the total size of the device is >2TB.There is also an SATA drive, which is NOT on the raid controller.
The problem is, I want to install CentOS on the SATA drive. The SATA drive comes up as a device-mapper drive, with a big crazy device name.This is ok, but the problem is, when the system goes to boot, it just says 'missing operating system'.I can't boot from the raid because it is large enough to require a GPT partition, and CentOS says it can't boot from a GPT partition.The SATA drive would work FINE if I could just prevent the damn device mapper from loading, so that I could install on the SATA drive in ordinary SATA mode.
I have tried re-squashing the stage2.img with /etc/modprobe.conf with alias dm_mod off and such, no luck.I also tried adding an /etc/modprobe.d/blacklist file, that did not work either.I also tried putting blacklist= dm_mod in the kickstart file, but that seems to be a fedora-only option and it kills my install. any ideas on preventing the dm_mod et. al. from loading at install time??
Greetings Fellow Knights Of The Penguin Clan....!I am having issues with device mapper seeing a 275GB Raid5 Lun from my SAN storage.I'm using IBM 2145 San Volume Controller.I am able to see a 40 GB Raid 10 device though..
########################################################################
fdisk -l |grep 'dm-*'
Disk /dev/dm-6: 42.9 GB, 42949672960 bytes
[code]....
I have a linux machine, attached to a fibre channel SAN.
We're in the testing phases and we're attempting to get all of the bugs worked out before this goes live.
If i have my host streaming data to the storage device on the san (or from the device on the san) and simulate a path failure (by shutting down one of the host's ports on the FC switch), multipath does not pick up on another path until about 45 seconds have passed.
I can verify this by watching the statistic graph (which updates once per second) on the storage system.
I see iops running along rather nicely, and then they drop to 0 for 45 seconds, then pick right up to normal again.
This is a RehHat EL 5.5 system, with qlogic HBA's.
Am i being too picky? I'd expect multipath to recover in under 30 seconds, so as to not alarm host applications running on the linux host... 45 seconds seems like a long time to wait for a disk operation to complete.
Any tips on tuning Multipath, or the qlogic card? As it is, i've got the following options in my modprobe.conf.
alias scsi_hostadapter2 qla2xxx
Code:
My multipath.conf looks like:
Code:
I've bought an X10 Home Automation USB interface: the CM15.
This is the information lsusb gives:
skerit@KIP-DU-SKER:~$ lsusb Bus 008 Device 002: ID 0bc7:0001 X10 Wireless Technology, Inc. ActiveHome (ACPI-compliant)
But this tells me nothing about where the device file is! How can I find that, or create one myself?
Trying to do a yum update to get everything to latest, towards the end it says this:
[Code]...
how to get around this? I tried yum clean all, then yum update, again but it did the same. I had other deps missing on other servers but yum clean all fixed them -- can't find anyone else who's had this specific issue either, nor an rpm called 'device-mapper-event' or the other things that are missing - am kinda stuck!
I'm having some difficulities with truecrypt and cannot figure out what's wrong since this is my first attempt to create hidden encrypted partition. I'm using ubuntu 9.10 64b with latest 6.3a truecrypt. After using truecrypt gui (just command truecrypt) I've tried: create volume-->create volumne within a partition/drive-->hidden trucrypt volume --> select some /dev/sdX by my choice --> select aes & sha512 --> password --> and format it.
when formating finished message "wrong ss, swith or wrong superblock of /dev/loop0" appeared. I've got no idea what could I do with it neither know whats program trying to do! Ok formating's done, then if you're trying to mount that partition then I would expect prompt for password, but that did not happen ...
EDIT: sudo mount /dev/loop0 /media/tmp/ also complaint about wrong superblock, but that does not ring any bell since i've got no idea what /dev/loop0 is or is for...
EDIT2: I've tried another approach also:
sudo truecrypt -t -c
sudo truecrypt -t /dev/sda3 --filesystem=none
but the first command finished creating 100G drive in 1 sec (nonsense) and latter one prints:
Error: device-mapper: reload ioctl failed: Invalid argument
Command failed
Anyone know how device-mapper works, or can someone point me to any docco (other than the man page)?
Couple years ago I wrote a TrueCrypt wrapper script for use on Puppy Linux, and am reworking it for Ubuntu. Puppy sometimes didn't have the 'dmsetup' device-mapper utility available, but TrueCrypt still works without this when the '-m nokernelcrypto' option is used.
My script notices when dmsetup is available and skips this option. When the TC volume gets mounted (somehow using dmsetup), the Desktop icon is labled with the leaf name of the /media/mount_point -- so far, so good.
However, if I force the script to add the no-kernel-crypto option, and the TC volume is mounted without using dmsetup, the Desktop icon ls labled with the size of the volume. Say what?
Running df shows the difference between the two mounts is whether /dev/mapper is used. So *how is* dmsetup making this happen? The manpage isn't much help. Is it just the 'rename' sub-command? I am unable to find any details about this mechanism.
Code:
I run many 5.2 virtual machines inside of VMWare ESX3.5 I've updated a couple of test VMs from 5.2 to 5.3. The thing that stands out is that during boot time, the sequence gets to this stage:
device-mapper: dm-raid45: intialized v0.2429 Waiting for driver initialization.
Here it takes about 3 times longer than the previous Centos 5.2 (about 9 seconds instead of 3). Whereas inside a physical box the wait in 5.3 is the same as it was in 5.2
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
[Code]....
When I connect my Treo 650 with a USB cable it works sometimes and not others. A little investigation showed
that it always works when I see the Palm device listed in the output of lsusb. While trying to diagnose why it appears sometimes and not others, I discovered that it sometimes appears in /proc/bus/usb/devices and not
in lsusb. I didn't think that was possible!
I've tried running kudzu (the Red Hat hardware discovery tool) and killing and restarting udevd.
We are having issues with LVM on CentOS 5.4 both 32bit and 64bit on one particular machine. I just can't get my head around it. Usually a device in /dev/ is created when a LVM Volume Group is created. e.g. if you add a volume group called foo, you would have /dev/foo to work with to access LVs inside the volume group.
For some reason it's not being created. The udev service is running, the volume group is created ok, I cant see anything strange in logs or strace.
I had to reinstall 10.04 because I got an error, waiting for root device. And I figured I knew why I got this error: I changed my xconf.cfg (or whatever the file is in /etc/x11/) -- So this time I downloaded the 64 bit, because I have a 64 bit computer, so though, might as well get it! I've narrowed the problem down to this:
After I install nvidia settings (the x server or whatever?) And change my view to TwinView (I have my laptop monitor and an external monitor), and save the config file, this happens. I will do some more testing, but here is the whole error message: Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system not wait long enough?)
- Check root= (did the system wait for the right device?
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/bcb49367-8554-4116-8e4d2b39d92415cf does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash) Enter 'help' for a list of built-in commands.
I've read hundreds of threads on this problem but they seem to be intermittent and the resolution has been using a different kernel version.
I'm using the latest kernel but I still have this problem
Running Logical Volume Manager gui and attempting to extend the volume results in the same error.
I have the following webcam installed:Bus 001 Device 002: ID 5986:0241 Acer, Inc BisonCam, NB Pro The kernel (linux 2.6.32-5-686) successfully recognizes it. issuing lsmod shows:
[code]....
I have installed 1tb hard drive and would like to partition as follows:
1) / - 20g
2) /swap - 6G
3) /photos /150g
4) /videos /500g
5) /audio /300g
After 2-3 partition an extended partition automatically created in which I am not able to create specified capacity i.e., say I want 150g of /photos partition, the /videos partition is automatically reduced and a free space at the end appears. Some free space is always there which i am not able to understand. Nevertheless i clicked to create, but I get an error viz. 'device not created'.
Why a usb touch screen device is not created on /dev? It can be detected on lsusb but no particular dev location like /dev/input/event0 or something like that. I've already updated my kernel for 5.6. do i need a driver to be able for this device to have a dev? No calibration tool works on this hardware. Same also on my tm u220 usb printer. It can be detected but no /dev/usb/lp0 being created.
View 1 Replies View RelatedIn my understanding, the way /proc/scsi/scsi gets populated, /proc/paritions also gets populated in the same fashion. i.e. the description for first entry of /proc/scsi/scsi can be seen in the first entry of /proc/partitions and same for rest.
So, With this assumption, in my project, I used to relate first entry of /proc/scsi/scsi with first entry of /proc/partitions to get its total size and same for all entries.
But, I observed some differences in following scenario, where
1) The first 4 entries in /proc/scsi/scsi are SAN luns attached to my system and for which the actual device names in /dev/ are sda,sdb,sdc and sdd.
2) The last 4 entries are the internal HDDs on same system. In /dev/, their respective device names are sde,sdf,sdg & sdh.
(Output attached at end of the thread)
But in /proc/partitions, the device order is different.
You can see their respective sizes in /proc/partition output as well.
So, my question is, in this particular scenario, I can't relate the first entry of /proc/scsi/scsi with first entry of /proc/partition. i.e. scsi0:00:00:00 is not /dev/sde, because it is actually /dev/sda.
It seems that my assumption is wrong in this scenario.
Is there any way or mechanism to figure out actual device name for an entry in /proc/scsi/scsi in /dev/ directory?
How can my application should relate /proc/scsi/scsi entries with their respective device names and sizes?
Installed Maverick last night... the system has been working fine all day... then on a reboot tonight got the following.
RAMDISK: gzip image found at block 0
usb 1-2: new high speed usb device using ehci_hcd and address 2
uncompression error
VFS: Cannot open root device "mapper/mylaptop-root" or unknown-block(0,0)
[code]....
Then it gives the Kernel Panic
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper not tainted 2.6.35-22-generic #35-Ubuntu
Then a call trace...This is a brand new install of Maverick I copied my files onto a USB and did a fresh install on the whole drive using the alternate CD (the desktop and netbook editions both failed to read on my system) was previously using Karmic with no issues. I tried to e2fsck the dev/sda1 from the CD in "repair broken system" mode but the return was "clean" I read that as the file system being intact but this is an area that I have no real knowledge in.
I have Debian Testing. I am testing XFCE and LXDE and i want to use display manager other than GDM. I have tried SLIM and XDM but when i use them i can't mount partitions and USB through Thunar, PcMan or Nautilus - i get message that i am not authorized (if i do groups in terminal - adm dialout fax cdrom floppy tape audio dip video plugdev games fuse powerdev netdev lpadmin scanner sambashare). When i install GDM everything works fine. I have installed FUSE, HAL, Udev,...I have tried a lot of stuff from AcchLinux forums but nothing worked really.
View 4 Replies View RelatedI try to install 10.04 from CD Rom. At the prepare partitions step, no devices appear.Some details: - I already check the md5sum of the CD.- GParted see it and I'm able to partition it. But always nothing detected with the prepare step.- Intel P4 with 80 GB with 1GB of ram
- No windows already installed on the machine
I am working on an embedded system, which is an USB MSC device that supports some vendor specific scsi commands. I am using FC10 laptop as USB host for testing, and it runs some small apps based on sg3. All has been well for ~ a week. The FC10 laptop is able to communicate with the device and retrieve data. Suddenly, starting from today, the laptop is not able to properly detect the device. When plugged-in, the MSC device is detected as input device (I thought). This is observed from "dmesg" output and changes in "/dev/input/".The device under development is running at full speed. When I connect to winXP, no problem. A windows file explorer pops up, showing the content of the drive.Also, the FC10 has no problem with other USB flash drive (high speed).
View 1 Replies View RelatedAll my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?
View 3 Replies View RelatedI rebooted my server and out of nowhere the RAID5 array won't assemble. I've tried everything I could think of to reassemble the thing. I fear that the array is ruined, but I can't imagine how. Here are various bits of information: The simplest failure (with and without partition numbers, which have not been needed in the past):
Code:
richard@nas:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/sd[bcd]
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/sdb: Device or resource busy
[code]...
For those that use Virtualbox on their slackware host and have a windows (xp) guest running. I have tried various settings for sound (Alsa, PulseAudio), the AC97 drivers are installed in the Windows xp guest os, but there is no sound and there is an unknown audio device (in the windows device manager). If I remove the AC97 drivers and use the soundblaster16 drivers in the Vbox settings there is no unknown sound device, but there's still no sound. why I can't get sound working?
View 13 Replies View Relatedthe message from dmesg for the IrDA device:
[ 3635.194162] usb 3-1: new full speed USB device using uhci_hcd and address 2
[ 3635.338159] usb 3-1: New USB device found, idVendor=066f, idProduct=4200
[ 3635.338165] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[code]...