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.
I 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
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.
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.
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.
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"
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.
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
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.
Something 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.
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.
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.
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
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
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.
I 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!
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?
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.
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.
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"
Having problems with external hard drives. I may be wrong, but I suspect they originated with an upgrade to 10.04 last Christmas. Around that time I also started using Amazon's S3 storage system, and, as a consequence, I stopped using my WD 80G external drive, previously used to backup my important files.
A week or so ago I decided to start using the WD drive again. I can't remember exactly what I did, but it wasn't happy - never caused any problems before. When I plug it in, the on-off light as the front keeps flashing on and off, and when I try to remove the drive I get the message: Error unmounting volumne An error occured while performing an operation on "My Book" (Partition 1 of WD 800BB External): The device is busy
Details: Cannot unmount because file system on device is busy Assuming the device had died - it's about 5 years old - I bought a 160G Samsung S-Series drive - my but they do look neat! Unfortunately, this doesn't seem to have solved my problem. I plugged the new drive in, and it happily appeared on my desktop. It seemed a good idea at the time, but I then started to format the drive - using the default option of FAT. All went well at first, but then the format process stopped.
My new Samsung drive now seems to be operating pretty much as the WD device, I can't copy to the drive, and attempts to unmount it generate a response similar to what's happening with the WD drive. Currently, although plugged in, I can't see the drive on my desktop, although it appears under Places. However, when I try to mount the drive, I get the message: Unable to mount SAMSUNG A job is pending on /dev/sdb1
Have Karmic 9.10 ,Changed from Epson RX595 all in 1 (uses a ton of ink)Got the Lexmark Pro 805 3 in 1 because it says it supports Linux and the ink cartridge only cost $5 downloaded drivers and printer works but using Xsane Image Scanner error reports
'Lexmark_1_0_0:libsub/001/009': Device busy Using Image Scan - reports Could not send command to scanner Check the scanner status. The RX595's scanner drivers had to been manually instatlled,, in the Printer box the Lexmark shows available..
Recently I was trying out a boot disk I had made, and basically, I switched it off several times due to it booting the completely wrong kernel. Now, I'm getting to the stage "Checking File systems" and then comes up [Failed]. I then get a message saying Reboot required, and that it will reboot in 15 seconds, just a few seconds before it reboots I get "/dev/shm not mounted, /dev busy" or something similar.
I've booted up my sysresccd, ran "fsck.ext4 -fcv /dev/sda2" to force a check and scan for any bad blocks, it came up clean, then I rebooted and got the same error, so I copied the kernel and system.map over to /boot to make sure there's no corruption and reinstalled initscripts and util-linux-ng, rebooted, same error.Tried different kernels, I've checked fstab and menu.lst, no problems there, so I still don't get why I still get the same problem.
Am wondering if looking at the CPU process queues, vs CPU% busy, are a better indication of whether an upgrade is needed.
Afterall, processes can still queue up to be processed even if "top" doesn't shown CPU 100%. Say if it's indicating 50% busy within the top output, it's only saying that 5 out of 10 times sampled, the CPU was busy. But a process may arrive to be processed at any time, and if it arrives just when the CPU is processing something it needs to wait in the queue. Am I making senses?
How many processes queued up would suggest an upgrade is required of the CPU? I've read online (believe it's Microsoft) that 2 is the figure.
I am not sure when this started for me, but I think in a recent update of Firefox. I am running Ubuuntu 9.10 Karmic Koala. I am currently running FF 3.5.6. When I click on a link in a page, or refresh the page, the Arrow/Pointer cursor stays the same in place of the normal busy cursor that I am used to. This is more of an annoyance than a real functional issue, as I can't tell if the page is working except to see the tab showing loading, and the status bar in FF. I have searched the forums, and google/linux, but have not found a cause, nor a fix.
I also use Opera and Chrome at times and the busy cursor works there as expected. I also use Thunderbird and it is working there. So, I believe it is only related to FF. My addons are as follows, but I haven't added anything recently, and it was working before.
Extensions: ColorfulTabs 4.1 Live HTTP Headers 0.15 Ubuntu Firefox Modifications 0.8 Web Developer 1.1.8 [Code].....
I am saying good by to windows at work.I've had it! But We use groupwise email client at work, but I can't figure out how to do a busy search in evolution when setting up appointments.Also, how do I go about syncing up the novell contact list?
1. how to do busy search in evolution. 2. how to sync corporate contact list.