Debian Installation :: Mount Root Filesystem Failed: Device Or Resource Busy
Jun 16, 2010
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.
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.
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.
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.
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"
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 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 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 decided to try to do the 3 distro upgrade stretch from 8.04 to 10.04 this weekend and now I am hung on 9.04 to 9.10.. The upgrade went swimmingly, but I hit a wall upon boot. When I try to load kernel 2.6.31-22 I am greeted with the following error:
Code:
[ 20.879845] ACPI: I/O resource vt596_smbus [0x400-0$407] conflicts with ACPI region SMOV [0x400-0x406] Mount of root filesystem failed.
A maintenance shell will now be started ... After doing some digging I found this thread which appears to be similar in the inability to mount the filesystem. However, it does not mention the ACPI error. I tried everything in that thread; verifying device ID's, editing fstab options; running a filesystem check, and flipping the UTC option in the rcS file but nothing worked. The OP of that thread eventually did a fresh install of Karmic; but I would rather not have to go that far.
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 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 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.
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 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 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.
I have a dual booting newly installed 64 bit Ubuntu 9.10 on my machine. It was all fine until today. Now when I boot into Ubuntu, I see the error Failed to mount root filesystem. I cant remember any significant changes during the last session. One thing I remember is I upgraded the system using the update manager which asked me to choose an option for grub boot loader. I opted for its upgradation. After the upgrade, I was able to work with Ubuntu for a few more sessions. Windows XP works very fine.I checked other threads which suggested running fsck, but it did not help. fsck does not report any errors.
Running F12 on my compaq evo N410c. Did a system restart 4rm gnome logged in as root & now grub cant mount my root filesystem, it boots vista though. How do i rectify dis.
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
I had a LiveUSB of CentOS 5.5, so I decided the install it.With no installer,I just copied the files to my hard drive.his was in a multi boot with Windows 7, Ubuntu 9.10, and FreeDOS.I updated GRUB2 and it detected CentOS. I loaded my entry and it failed to mount the root filesystem.I took the initrd0 file from the LiveUSB syslinux folder and added that ramdisk to the entry. Now it finds the root filesystem (/dev/sda9 as Ext3).But it fails shortly after loading /sbin/init. It talks about an init error where it says "File not found!!!".The previous lines involved umounting old filesystems, like /dev.
A friend of mine upgraded his pc to ubuntu 10.04. Sadly enough we ran into issues with his graphics card, which apparently doesnt work well with lucid. We decided to downgrade to 9.10. I did this by installing over the old partition and chose to import the settings from the old account.The problems started when the pc booted for the first time:The list of kernels in grub2 was the one from 10.04.Somehow grub2 from the old installation seems to be still around and messes everything up. Any ideas how I could fix this?
I've downloaded Fedora 12 and decided to try and install it on my old laptop which is currently running Ubuntu 9.10 with no problems.
When I boot from the live cd, it starts to load with the 3 bars on the bottom, one on top of the other, one is white, one is dark blue, the other is in between those colours in the spectrum somewhere....
Anyway, the load bars complete and "Fedora 12" turns white, then the following output populates:
mount: unknown filesystem type 'DM_Snapshot_Cow' (<----- repeated a bunch of times) can't mount root filesystem Boot has failed, sleeping forever.
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 was using 9.04 for a while because it was working for me, I decided to upgrade yesterday using the Upgrade button on synaptic to 9.10. Now when I boot I get an error message: Code: chroot: cannot execute /etc/apparmor/initramfs: No such file or directory Mount of filesystem failed. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try I want to try to fix the problem so I do not have to do fresh installation.
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.
I upgraded 9.10 to 10.04 via the web. The program announced it would take several hours, and when I came back to check, computer was off (kids?). Anyway, machine boots and 10.04 starts, but then blinks a few times and goes to a prompt. What should I tell it?
I have a 10.04 disc too, but it won't run from that either (Cannot mount dev/loop0 on filesystem.squashfs failed). Same message when I tried to start a nearby Windows machine with it. Disc "verified" when I made it. What's with that?