Ubuntu Multimedia :: Unable To Open Device /dev/dsp - Device Or Resource Busy
Apr 13, 2010All my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?
View 3 RepliesAll my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?
View 3 RepliesI 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]...
Trying to complete a RAID 1 mirror on a running system and have run into a wall at the last part. I can't add the active physical disk to the mirror. This is on a Centos 5.6 x86_64 system. Anybody know where to go from here? I've tried adding the nodmraid line to the kernel boot line with no luck. Tried removing the logical volumes from LVM, but it won't let me. Not a Linux newbie, but haven't set up a RAID in a long time.
[root@blackbox-0-2-e3-23-72-c5 ~]# mdadm /dev/md1 --add /dev/sda2
mdadm: Cannot open /dev/sda2: Device or resource busy
Here's output from fdisk -l:
[root@blackbox-0-2-e3-23-72-c5 ~]# fdisk -l
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
[code]....
Here's mdadm.conf:
[root@blackbox-0-2-e3-23-72-c5 ~]# cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3c6f7354:b9bfc86a:aa9d0dfb:cdd51bd8
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=31ee55ba:be3b3606:974ac87d:627435a9
Using debian testing.
Pulseaudio got installed by default here during installtion. Since I don't want it I first ran "systemctl disable pulseaudio", "pulseaudio --kill", then without rebooting I use mpd with alsa alone and it worked fine.
But then i rebooted, and now all applications, mpd, mpv, chromium etc just says that alsa returns with "Device or resource busy", tried rebooting again with no effect.
The soundcard appears as card 1 according to the output of "aplay -l", and defined that card 1is suposed to be default with this in "/etc/asound.conf":
Code: Select allpcm.!default {
type hw
card 1
}
ctl.!default {
type hw
card 1
}
It occurred to me that there might be an issue with permissions to the soundcard so I ran "ls -l /dev/snd"
Code: Select alldrwxr-xr-x 2 root root 80 Mar 31 03:27 by-path
crw-rw----+ 1 root audio 116, 8 Mar 31 03:27 controlC0
crw-rw----+ 1 root audio 116, 2 Mar 31 03:27 controlC1
crw-rw----+ 1 root audio 116, 12 Mar 31 03:27 hwC0D0
crw-rw----+ 1 root audio 116, 7 Mar 31 03:27 hwC1D0
[Code] ....
My user is a part of the audio group:
Code: Select alluid=1000(roberth) gid=1000(roberth) groups=1000(roberth),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),108(netdev),111(scanner)
As far as I can tell, that looks fine unless I am missing something?
I am trying to set up a mdadm raid in a new machine that I am building as a home theatre PC. the machine boot just fine from /dev/sdc running ubuntu 9.10 However in gparted /dev/sda and dev/sdb show to be part of /devmapper/sil_ajbicfacbaej
Both dev/sda and /dev/sdb were drives that used to be part of a sil hardware raid on a previous machine. I would like to use them as a new mdadm raid on this new machine the old hardware card was really quite slow. the drives are now pluged into the MB and should be much faster there.
fdisk -l shows this
It produces no errors but does not remove it.
I am dual-booting my Gateway laptop with Windows XP Media center Ed. and Ubuntu Notebook 10.10. Several weeks ago I was in the midst of downloading a program from the software center and my system starts running slow (this is in the Ubuntu kernel, not the Windows OS). So I decided to cold-boot the laptop in mid-download. When it boots back up, I get dropped to a grub-rescue menu that states the following:
Code:
Now, the only way I can even remotely use my laptop at the moment is to use my Live USB with the corresponding version of Ubuntu Netbook 10.10 or the Live CD I made with Ubuntu 10.04 on it (I'll explain why I made this below).
I read somewhere that I need to run fsck on my device to try to fix the partition, which btw my Ubuntu partition on my device is /dev/sda5, and before someone suggests it, I even tried using GParted and it doesn't work.
The reason I made a 10.04 CD is because I read somewhere that using the fsck from 10.04 might be more effective (for whatever reason) than the 10.10 fsck version.
I'd also like to add that I'm incapable of booting onto my Windows OS at all, yet I can access the partition from my Live CD/USB. the Ubuntu partition however, I can neither access or mount.
I tried running fsck on the entire device partition table, and I get the following:
Code:
This is me running fsck from the 10.04 version, I get a similar msg from the 10.10 Live USB but replace fsck.ext2 with fsck.ext4 in the message.
My son's netbook with 10.10 netbook remix failed to boot. Using the Live install CD and Gparted I couldn't repair the EXT4 filesytem. The error reported was:
e2fsck : Device or resource busy while trying to open ...
After trying many solutions and web searching I decided to try a different live CD and tried Knoppix 6.4.4
Using the command interface I typed e2fsck -v -f -y /dev/xxxx (xxxx = your device). This worked first time and the machine rebooted without hesitation.
After upgrading to fedora 15, I have problems mounting XFS filesystem.
The short tale:
Code:
08:01:38 localhost root>mount -t xfs -vv /dev/sdb1 /data/disks/old
mount: /dev/sdb1 already mounted or /data/disks/old busy
08:01:39 localhost root>fuser /data/disks/old
08:01:41 localhost root>lsof /data/disks/old
08:01:44 localhost root>xfs_repair -t 1 /dev/sdb1
xfs_repair: cannot open /dev/sdb1: Device or resource busy
08:01:48 localhost root>fuser -mu /dev/sdb1
08:02:08 localhost root>dmesg | tail -n 5
[1655779.759764] SGI XFS Quota Management subsystem
[1659275.905756] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[1659275.908745] SGI XFS Quota Management subsystem
[1659389.154986] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[1659389.156519] SGI XFS Quota Management subsystem
Device is not mounted, and directory is not in use, it has just been created. There is nothing in log files that could remotely point the cause. After removing device (echo 1 > /sys/block/sdb/device/delete) and reattaching it, disk started working.
When installing I am selecting the manual partitioning scheme( I have arch on another partition). After I have selected my custom partitions and their mount points it starts the installation but almost immediately it gives the error message that it cannot create a partition on the specified one, as it is used by the OS. I have also tried to create partitions through gparted in the live session but to no avail. I am sure that no partitions are mounted or in use by the system, I have checked this using the mount and fuser commands. I also tried the oem installation but the result the same.
View 3 Replies View RelatedSomething weird happened last night and my raid5 failed. I am trying to re activate it and see if my data is dead or what. When I run mdadm -Asv /dev/md0 I get
Code:
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: /dev/dm-1 has wrong uuid.
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: /dev/dm-0 has wrong uuid.
mdadm: cannot open device /dev/sde2: Device or resource busy
mdadm: /dev/sde2 has wrong uuid.
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: /dev/sde1 has wrong uuid.
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: /dev/sde has wrong uuid.
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: /dev/sdd has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
I am trying to set up a mdadm raid in a new PC that I am building for home theatre. the machine boot just fine from /dev/sdc running ubuntu 9.10 However in gparted /dev/sda and dev/sdb show to be part of /devmapper/sil_ajbicfacbaej Both dev/sda and /dev/sdb were drives that used to be part of a sil hardware raid on a previous machine. I would like to use them as a new mdadm raid on this new machine the old hardware card was really quite slow. the drives are now pluged into the MB and should bw much faster there.
fdisk -l shows this
*********************************************** ~$ sudo fdisk -l
Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
[code]....
So I cant seem to be able to install fedora 15. I think it is the disk. I have windows 7 already installed (and would like to keep it) It was installed on the end of the hard drive leaving a 100 GB chunk in the center of the drive open and unformatted (this may be the problem). Anyway I used the live cd and tried to format the unformatted partition to exf but it gives me this error
Code:
Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/sda, start=105906176, size=104752742400, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
Entering MS-DOS parser (offset=0, size=500107862016)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
Exiting MS-DOS parser
Entering EFI GPT parser
GPT magic found
partition_entry_lba=2
num_entries=128
size_of_entry=128
Leaving EFI GPT parser
EFI GPT partition table detected
containing partition table scheme = 3
got it
got disk
new partition
added partition start=105905664 size=512
committed to disk
Error doing BLKPG ioctl with BLKPG_ADD_PARTITION for partition 2 of size 105905664 at offset 512 on /dev/sda: Device or resource busy
Do I have to reinstall windows for this to work or is there something I can try to do.
I've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
[code]....
I have an audio recorder that doubles as a music player. It can play WAV files. So I put in some WAV files and they are out of order, even if they are named numerically. Read somewhere about a little CLI software called fatsort so I installed. The device is located at /dev/sdc. So naturally I write fatsort /dev/sdc, it says something about permission. So sudo fatsort /dev/sdc. Thing is, it says:
Code: sort_fs: Device or resource busy! If I "eject" it (unmount) then it says something about cannot read boot sector or headers. On Windows there is FAT Sorter. It does not work in WINE. So every time I put something in, I have to get to a Windows computer to sort it. It seems like fatsort is the only program that sorts FAT systems in Ubuntu/Linux.
The error message I keep getting during mounting is:-
device-mapper: remove ioctl failed: Device or resource busy
This is from ane external USB HDD I use as a backup device. I've tried formatting it as ext4 ane encrypting it from the command line
# mkfs.ext4 /dev/sdc1
# cryptestup luksFormat /dev/sdc1
which run without errors but an attempt to mount throws up the above error as well as saying - you must specify the file type (tried that) - and fails to mount. I've tried using YaST to format and encrypt it which throws up the same error when I run mount but actually does actually mount the filesystem Googling around has brought up info saying that it's probably a race condition brought on by invalid udev rules. I've got a (mostly) working system and the udev rules documentation leaves more confused than when I started.
I'm currently running Ubuntu Maverick - 2.6.32-30-generic. I recently bought a Garmin eTrex Vista H, which connects via usb (from my reading, it looks like older versions connected over serial). Well, like so many before me, I can't seem to write to or read from the device via gpsbabel.Originally tried to read anything from the device (I have one waypoint in there) via:
Code:
gpsbabel -i garmin -f usb:
It returned "Found no Garmin USB devices." I then tried turning on the eTrex. Doing the same while locating satellites just does nothing - I have to escape from the command in terminal. Trying again produces the error:
Quote:
Claim interfaced failed: could not claim interface 0: Device or resource busy
After doing some research, I unblacklisted and then reblacklisted garmin_gps. I also went into
Code:
/etc/udev/rules.d/51-garmin.rules
to verify that the contents were:
Quote:
SYSFS{idVendor}=="091e", SYSFS{idProduct}=="0003", MODE="666"
as directed in this . Everything seemed to be correct.I then followed some other advice found here and created the policy under /etc/hal/... Still no luck!
When I try to suspend to RAM my Fedora 12 system (2.6.31.12-174.2.22.fc12.x86_64), Screen goes blank for about 15 seconds, and then comes back as if nothing happened. I see the following error in /var/log/pm-suspend.log
[Code]....
I have a little problem with my RHEL5.5 IA64. I mounted a Windows directory with 'mount -t cifs'. After a little while someone else mounted the same windows directory in the same mountpoint. The output from 'mount -v' shows me that the same directory is mounted twice in the same mountpoints. I cannot unmount it, not even with the force option. The error is "Device or resource busy". There are no open files in the shared directory and no one using the directory or subdirectories.
View 6 Replies View RelatedI installed mdadm fine and all and proceeded to run:mdadm --create --verbose /dev/md0 --level=stripe --raid-devices=2 /dev/sda /dev/sdbWith sda being my primary hard drive, and sdb being the secondary.I get this error message upon running the command"mdadm: chunk size defaults to 64Kmdadm: Cannot open /dev/sda: Device or resource busymdadm: create aborted"I don't know what's wrong!
mdstat says:
"Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
unused devices: <none>"
I have a 250gb External HD and wanted to format it using the disk utility but every time I try Ubuntu tells me that the drive is busy.
How is it busy? I have nothing opened and haven't used it in anyway other than plugging it in. It doesn't even tell me what's using it.
I have installed moto4lin, as I want to be able to get pictures off my razr v3mM, which I could easily do in Windows. I found a guide for connecting a v3m, but for some reason moto4lin is screwing around with me. Here is my log:
[info] Phone is unplugged. Please connect it
[info] Phone plugged as AT
[info] Switching device /dev/ttyACM0 to P2K mode...
[error] Unable to open device
[error] Please check preferences
[info] Switching device /dev/ttyACM0 to P2K mode .....
Code:
HP 210 Mini
Fedora 14 xfce
2.6.35.11-83.fc14.x86_64
I have inserted my handy drive. However, when I right click and select unmount I get the following message:
Code:
An application is preventing the volume "New Volume" from being unmounted
So I try from the command line:
Code:
umount /dev/sdb1
And I get the following message:
Code:
umount: /media/New Volume: device is busy. All I have done is copied some files to my handy drive. So I am not sure what process is keeping my handy drive busy.
Is there any command that I can use to see what process of anything else is using the handy drive?
When booting up my IBM Thinkpad Ubuntu stalls giving the following messages:
Cannot open root device "uuid=58a5831c-5757-49f8.....
Kernal Panic - not syncing: Unable to mount root fs on unknown-block
Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.
I am or was using Hardy.
It seems to me that the program is telling me it can't find the hard drive or the partition where the OS resides. I have my drive partitioned with into sections for booting, the OS and my Home directory.
I had this problem after my mainboard crashed (my clumsiness) and I replaced my dual-core AMD with a Triple-core and a MSI mainboard deal from a dealer clearencing. Before my MBR was on my 80 gig IDE but I dropped it and put my SATA 320gig in its place and did a fresh install of Lucid. Preparing a machine for a friend that wanted Mepis on her computer with WindowsXP in VirtualBox I could not compile the vbox kernel and in the mepislovers forum I was instructed to run sudo m-a and to then compile the kernel. This worked perfectly.
This morning (01:57 Texas time) after trying a few solution suggestions from the forum here I said, what the snot and I typed sudo m-a in the terminal and was instructed to download the module-assistant with the useual 'apt-get install module-assistant. After the install I ran the sudo m-a and then with my arrow keys selected the second option and hit enter. As soon as it finished I used my down arrow and selected the third option and entered it. After that I selected exit and have been cold starting my machine without the aggravation.
Named has been working fine for months on Fedora core 14 with updates current.a few days ago it stopped working. I tried a service named restart and received the error message: stopping named: umount:/var/named/ chroot/var/named: device is busy.I tried using kill process, which did not work. However if I use kill 9 <named process>, followed by service named stop, I can then restart the service and it works for a number of hours (less than a day), then stops again and produces the error message above when I try to restart it.I can get it working again using the procedure above, but only temporarily.
View 7 Replies View RelatedI have an Ubuntu server x64 (10.04) that is running FOG for imaging Its installed on an Intel server board (1 RU rackmount) I configured the RAID in an Intekl based BIOS utility which Looks similar to This Ubuntu installed and runs perfectly. however im unable to monitor the status of the drives from the OS, so Im unaware of any drive failures that may occur I manged to install megacli but it returns blank data (along with exit code: 0x00) Iv also tryed megactl wich says
Code:
unable to open device /dev/megadev0: No such file or directory
one of my colleagues who had used the server previously was certain that the raid was on board the intel site also makes mention of intel using LSI products in their RAID controllers Relevant section of dmidecode:
Code:
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Intel
[code]....
I have installed it (11.3) with KDE desktop.I have a problem with openening a device (harddisc) directly from sysinfo:/It is a ext4 partition, but also with my others (ntfs), this error occurs...
View 9 Replies View RelatedI have been trying to get tvtime or any tv package to work with my Pinnacle PCTV HD usb but I have not had success. I have correctly installed every driver imaginable. So, here is what it what it comes down to: When I open tvtime it says "cannot open capture device /dev/video0" and the screen is blue. But my usb PCTV HD stick is NOT /dev/video0 so the question is how can I get tvtime to look for the usb tv tuner rather than video0?
View 9 Replies View RelatedI'm trying to view the output of a dv firewire capture device (advc-100) fullscreen through vlc. I've read of people being able to do this but a detailed explanation of how eludes me.
I'm running Ubuntu 10.10 and VLC 1.1.4
The error message I'm given after trying to open through 'media>open capture device>play' is;
Quote:
Your input can't be opened: VLC is unable to open the MRL 'v4l2:///dev/ffc1/'. Check the log for details.
(and I can't find the log)
I'm not even sure if I've got the device name right so I ran lspci from the command line which gave the following output (and I still can't work out what it is);
Quote:
[ 0.008410] ... event mask: 000000000003ffff
[ 0.014418] ACPI: Core revision 20100428
[ 0.020016] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 0.020023] ftrace: allocating 21756 entries in 43 pages
[Code].....
The server comes up after rebooting and after setting the hostname it starts setting up logical volume management. It says that 2 logical volume(s) in volume group "VolGroupOO" now active But then it starts to check the file system and errors with fsck.ext3: Device or resource busy while trying to open /dev/sdb1 [failed]
***An error occured during the file system check
***Droppping you to a shell, the system will reboot when you leave the shell
Give root password for maintenace
After I log in with the root I get the message mesg: error tty device is not owned by group 'tty' Can the forum tell me how to troubleshoot this issue so I can boot back up again? I have 2 harddrives in this server and only 1 drive was detected when I first installed CentOS. The error first appeared when I mounted the 2nd drive at the mount point /UserGeneratedData. drive was formatted with ext3 before mounting and did not have any data on it I don't want any software RAID if thats what seems to be going on with "VolGroup00"