CentOS 5 Hardware :: File System Check Fails On Boot - Device Busy
Jul 20, 2009
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 one hard disk for my root partition and a disk array on a separate mount point. I rebuilt my disk array, but I didn't delete my original mount points beforehand because I was hoping it would just "pick up". So now when I boot up, the OS tells me that the filesytem check fails because it can't find the array to map to the mount point. I know that I need to edit my /etc/fstab and remove the line that defines my mount point on the disk array. But it appears to be read only filesystem when I am in repair mode. I can't force the write with vi.
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.
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..
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
On my laptop I have a dual boot system, CentOS 5.4 on one partition and Windows Vista on the other. In Windows, I have a program installed that allows me to access my linux partition so I have access to the files. Every time I boot into linux after accessing the linux partition through windows, I get a forced file system check. I was wondering if there is a way to disable or perhaps bypass this check?
Vista Recovery Windows 7 GRUB Extended -->Fedora 12 (ext4)
so, I shrunk my recovery in Windows 7 successfully, and booted into my Fedora 12 live cd to run Gparted, and move the partitions so that the free space could go towards fedora, I did such, and then I couldn't expand the partition to my dismay. Next, I woke up this morning, tried to boot to fedora to run SSH, grub loaded, but when I tried to boot fedora, I got the "File system check failed" error, and when I tried 7, it just went to a blank screen with a single "_" in the top left-hand corner.
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've been stupid, and used kleansweep, which deleted a load of files and in the process killed everything. When I boot I get "file system check failed". Then it gives me a command prompt. I really don't want to have to reinstall ubuntu as I have a lot of stuff installed on it.
I have recently noticed that my HDD fsck during boot up (generally done after 30 mounts) is always skipped. A file system check has never happened. I don't remember if this is the case ever since I upgraded to Lucid or was it after I tweaked some settings.I am a learner who keeps tweaking some minor settings, so I am not sure if I have screwed up something.At boot I get the following message:
Code: fsck from util-linux-ng 2.17.2 fsck from util-linux-ng 2.17.2
I have a 2TB file-system and when the machine reboots it fails the fsck, halts and goes into maintenance mode.Stats: I have have RHEL 5, 2.6.18 kernel, the file-system is an ext3. The file-system is on an EMC AX4 connected with fiber channel HBA.So far my reading tells me this should work because under 2.6 4TB is OK. Any ideas why this fails?If I take it out of the fstab file and mount it manually the boot is OK and the file-system behaves well. I can change the fsck check option in the fstab to 0 but I don't think I should have too. Everything I read says that 2TB ext3 file-systems are OK.
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
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 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.
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.
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.
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've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
From one day to the other my system stopped booting properly. Since I (finally) fixed it, I wanted to share my solution. It runs on a fakeraid pair of SSD's of 60 GB each (actually a single Revodrive device, but it shows up as two devices). When Ubuntu 10.10 boots, I'm dropped to a shell.During boot, when I removed "silent splash" from the kernel's command line, I got these messages:
I doubt that this is what was needed (as I had that already when it didn't work, but I might be required in addition to installing dmraid)
# update-initramfs -a
After installing this, the problem was solved!! This is strange since I don't recall uninstalling this package or changing anything important, for that matter (perhaps did apt-get upgrade, but that's about it!). [URL]
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.
