CentOS 5 :: Mdadm: Cannot Open /dev/sda2: Device Or Resource Busy
Dec 5, 2010
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
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
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 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!
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 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.
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.
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.
Got a little problem after the install of Fedora 12. First there was not problem in opening the raid-device, after i tryed to automount it with crypttab and fstab im not longer able to open it. Here some outputs 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"
I have 4 SATA's in a RAID 5 array using mdadm. Yesterday when I started the computer the RAID did not build/mount. When trying to load the array manually I get the message "mdadm: cannot open device /dev/sd(a,b,c,d)1: Device or resource busy" The drives should not be mounted or in use. The output of the drives in mdadm (mdadm --examine /dev/sd_1) looks normal.
The weirdest part is that rebooting often changes which drive is marked as busy, it can be any of the 4 SATA drives. how to figure out why/what is being used and how to disable it? I have tried searching for similar threads here and in google and haven't found anything similar or that worked.
I have 4 SATA's in a RAID 5 array using mdadm. Yesterday when I started the computer the RAID did not build/mount.
When trying to load the array manually I get the message "mdadm: cannot open device /dev/sd(a,b,c,d)1: Device or resource busy" The drives should not be mounted or in use.
The output of the affected drive in mdadm (mdadm --examine /dev/sd_1) looks normal.
The weirdest part is that rebooting often changes which drive is marked as busy, it can be any of the 4 SATA drives. What is being used and how to disable it?
I just successfully installed ubuntu 10.10 Meerkat Maverik parallel to manufacturer installed Windows 7 Professional on a newly bought ThinkPad t410. All works find just that on the boot screen instead of 1 Windows partition (usually something like "Windows 7 loader on sda1") I find two Windows partitions. Now, I know that Thinkpads have a recovery partition. Funny is though that both "Windows 7 loader on sda1/2" login to what seems the identical Windows (not one of them the "normal" and the other some form of a recovery).
I am planning on setting up a 4x1TB RAID5 with mdadm under Ubuntu 9.10. I tried installing mdadm using "sudo apt-get install mdadm", all worked fine except for the following error: Code: Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found failed. The end result is the /dev/md0 device has not been created, as can be seen here:
Code: windsok@beer:~$ mdadm --detail /dev/md0 mdadm: cannot open /dev/md0: No such file or directory After googling, I found the following bug which describes the issue: [URL] However it was reported way back in April 2009, and it does not look like it will be fixed any time soon, so I was wondering if anyone knows a workaround for this bug, to get me up and running?
openSUSE Install/Boot/Login: I am looking for a Linux distribution with a working LTSP OOTB. LTSP-openSUSE / KIWI-LTSP looks interesting (http://en.opensuse.org/LTSP).
When I boot openSUSE-11.1-DVD-i586.iso, go through the installer, and attempt to use encrypted LVM, I get the following error dialog:
Code: YaST2 Error Failure occurred during following action: Setting up encrypted dm device on /dev/sda2 System error code was: -3034
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?
I have added CentOS5.5 x86-64 to a linux box that already contains installations of Ubuntu 9 and SL 5.2. Grub2 was installed with Ubuntu and is on the MBR of the disk. I did not install grub with anaconda/Cent. Grub update in ubuntu finds the Cent install and addes it to the grub.conf, and Cent appears in the grub menu at boot. If I select Cent, I get the following error. VFS: Cannot open root device "sda7" or unknown-block(0,0) Please append a correct "root=" boot option
Below is the output of boot_info_script, which gives the relevant boot file data. There are still grub conf files on the SL install, but grub is not installed there anymore. Boot Info Script 0.55 dated February 15th, 2010 => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub ..... sda3/boot/grub/grub.conf: # grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that all kernel and initrd paths are relative to /, eg. # root (hd1,2) # kernel /boot/vmlinuz-version ro root=/dev/sdb3 # initrd /boot/initrd-version.img
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.
