Red Hat / Fedora :: Unable To Replace Drive In RAID 5 After Filesystem Check Freezes?
Apr 28, 2011
I'm a bit of a Linux newbie, but I did manage to set up the following RAID-5 system:1x 500GB system drive on ATA IDE4x 1TB SATA drives in software RAIDLinux = Fedora 13So here's what happened. I set up the system to send me an email every time the mdadm stat file changed, so it would send me emails when in periodically ran a self-test. I was away and noticed that the self-test was going incredibly slow (usually took 8 hours...was on course for taking 250 days!) A colleague decided to just reboot the system.Afterwards, the system would not boot and, while all 5 drives were connected, would stop at an endlessly scrolling error message of: Code: ata4.01: exception Emask 0x0 SErr 0x0 action 0x0
ata4.01: BMDMA stay 0x64
ata4.01: failed command: READ DMA
ata4.01: (a bunch of hex numbers)
I am very new to linux, and I have a question regarding the filesystem check (fsck). The power recently went out and when I tried to restart linux the following error appears:
*/dev/sda1 contains file system w/errors, check forced it then goes on to say..
*An error occured during the file system check. Dropping you to a shell; the system will reboot when you leave the shell. Give root password for maintenance (or type Control-D to continue) I wasn't sure what to do, but checked some other online forums and they suggested running fsck manually - so I typed in the root password - and used the command, "fsck -A -V ; echo == $? ==" it then gave the following message
*WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage *Would you like to continue (y/n)
Again, I wasn't sure what to do so i just checked no. I then manually turned off the computer and was prompted at the beginning to press Alt-3. I was brought to another screen and it informed me one of the drives was degraded and suggested rebuilding the array. I tried doing this, but it still brings me back to the original error of, "/dev/sda1 contains file system w/errors, check forced," and the process continues.
Also, when I tried to rebuild the array, I didn't backup any of the data on our home directory before doing this (which was probably a big mistake). After being prompted to type the root password, I was able to give the ls command and look at all the directories...the home directory where our data was stored was empty and I am afraid I may have lost some information. Is there a possibility that data was lost when I was trying to rebuild using the old drives?
I want to be able to add a physical drive to an existing filesystem, and PRESTO! That filesystem has more storage and/or redundancy. When one of the physical drives eventually fail, no problem, Ive lost some redundancy, I just have to install a new drive before another one fails.Lets assume I have 4 physical drives.*What Is This Configuration? *[URL]...But I am unclear how to get a logical volume that is mirrored and linear.
The last time I tried software RAID 1 (dm-x) under lvm, it was very fragile. Systemd could not start it,and then an update to mdadm put a stake through its heart. So I know that does not work.
I'm trying to partition/format a new external hard disk for backup and have run into a snag that now prevents my computer from booting. In the description below of what happened please bear with me as I do my best to remember the commands and screen output (which for obvious reasons I don't have in front of me).As root.The disk was subsequently writable. However, I then realized that the default start and end cylinders had resulted in a very small partition apparently occupying some free cyclinders in the beginning of the disk.
So next I ran fdisk again, deleting the sdc4 I had just created and creating a new one instead, this time using the cylinders at the end of the disk. When I exited fdisk I got a message something like that the new tables can only be read upon a subsequent reboot. I ran mkfs again, but not e2label. Indeed using /sbin/fdisk -l, sdc4 still had the small size as defined initially. So I rebooted.
Now when it comes up I get something like "checking filesystems. fchk.ext3: can't resolve 'LABEL=/media/LaCie2TB1'" and am prompted to login as root to correct. I tried to simply delete sdc4 again but that didn't help. I also tried to edit /etc/fstab (using vi, which I don't know at all) but it kept telling me that this is a read only file, even though permissions are rw for root.Can anyone out there help me so that (1) I can boot into my computer, and (2) I can correctly partition and format the hard drive??
i have edge server. raid(5) have been installed but not able to check raid health. using command line able to.but using monitoring tool opsview, showing error -NRPE: Unable to read outpumachine Arch- 64 bit centos -5.2 package installed -MegaCli-2.00.15-1.i386.rpm
my Fedora 12 does fsck on boot time to time and sometimes it's really annoying having to wait for the check to complete. In Linux Mint pressing <Esc> cancelled the check; however in Fedora this does not work (nor does Ctrl+C nor anything other I've tried). What is the key to cancel the check in Fedora?
I have three raid volumes, md0, md1, and md2. The weekly raid-check cron always causes md0 and md2 to get checked but never md1.
/etc/cron.weekly/99-raid-check
Volumes md0 and md1 are on the same 8 disks. Volume md0 is a small raid1 across all 8 disks for boot and md1 is a raid5 that occupies the rest of those 8 disks. Volume md2 is a raid5 on a separate set of 6 drives. When I check /var/log/messages* I see that every Sunday md0 and md2 get checked but md1 is never checked. However, when I run 99-raid-check manually, all three volumes get checked. There is clearly something different between how crond runs that script and how I run it, but I can't imagine what that would be.
I've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
i was recently trying to boot my fedora 12 installation of a usb device today when i went to boot it i enter my LUKS pasfrase and it stops with an error mesege:
Code: ***an error occured during the filesystem check ***droping you to a shell; the system will rebot
I'm trying to do a fresh Fedora 14 install from usb live stick. On installation got to partition program and since I want my old /home partition I pointed the partitions as they're supposed to be and apart from /home marked all partitions to be formatted to ext4. After the format or in the end of it came up a prompt I couldn't past. The following link shows a pic of that prompt:
[URL]
What should I do to complete the install? I have partitions:
/ /home /boot /swap
Solution: Burned the image on CD and installed from it.
How long does hardware Raid card (raid 1, 2 drives)take to mirror a 1 TB drive (500gb used)?Is there a general rule of thumb for this?4 hours? 12 hours? 24 hours?
I have a CSV file with 8 columns. I want to check the 5th column, which will contain a single capitalised letter. If that letter is say "B" I would then like to replace the 2nd column in the csv with an incremental number starting at 0 (basically a count) with a prefix of B (B0000001) Sample row would be:
Have the following partitions, I've grown md1 from 3 drives to 4 drives with mdadm. It is now the size below of 531899712 from 354599292.
[Code].....
As you can see above however, the filesystem is not growing. What am I missing. I don't believe I need to do anything with the partitions. I should just resize my array as I have and xfs_grow and be finished.
I have got arch Linux dual booting with Win XP on my laptop. I have been getting a filesystem check error since yesterday and am unable to start Arch. Upon googling and searching the arch fora, I came upon some advice which I tried which has not worked yet. Hence the new post.Basically, I was attempting to print something off and accidentally chose a printer that was not connected to my laptop. After half a minute or so, it repeatedly started giving me notifications that the printer was not connected...in excess of 200 messages that the printer was not working which continued to pop up despite me canceling the print job. The whole system got really sluggish (for the first time in the last year) and I had to restart the laptop upon which the boot messages appear. It gets to the point where its loading the various filesystems. It mounts root and says it fine.
I tried fsck which tells me that home and boot are still mounted.So I booted up using an Ubuntu Live CD and checked and repaired each file system which it successfully did. Upon rebooting into Arch, I am getting the same message.I have not installed anything new and had upgraded the whole system a few days before the problem started.
fsck from util-linux-ng 2.17.2 e2fsck 1.41.11 (14-Mar-2010) /dev/sda1 is mounted. WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you really want to continue (y/n)?
I don't want to cause damage, but I'd rather not go into BIOS.
I cannot seem to get past the "creating File System.." window on a laptop upgrade
Setup: Thinkpad T23 (dual boot) upgrade from fc10 using DVD iso.checked with checksum and burnt by K3b.
History/actions taken:
Burnt iso to DVD and install/upgrade froze "creating File System " froze after approximately 10 minutes. (completely froze and had to use the power button!)
Checked disk OK on laptop, tried again, same fault.
Bought another DVD.(different die) and tried again, same fault.
Tried another laptop HD, (full install not dual boot) , same fault.
Removed partitions with fdisk, but still no luck.
Tried disk on a spare HD on my PC and it works, I get into the window allowing software selection!
Tried a "Linux Format" fc 10 disk and that works, also tried a PCLinux LXF disk which also worked.
The laptop does not report any problems at bootup and I do not not what else to try
I have ubuntu server acting as a router installed on a 60 gig drive, i'd like to use that drive in another machine and replace it with a 5 gig drive. how can i transfer from the 60 gig drive to the 5 gig drive?
I have just moved my /home to a 1TB, 2 disk, raid 1 setup (using btrfs). I benchmarked the individual disks using the Gnome Disk Utility, but how do I go about benchmarking, specifically the read speed of the file system?
Playing with the Box, I deleted a Raid-0 partition intentionally, saved it, and reboot drops me to (Repair Filesystem#) prompt. I notice during boot-up that the box didn't find /dev/md0, which is expected.
So what's the recovery procedure, since I can't edit #/etc/fstab, permission denied.
#fdisk -l shows all other partitions.
Not much familiar with fsck/e2fsck, yet like to give it a try.
Until a recent software update, I encountered no problems when 'Safely Removing' my external hard drive.
After the following update:
Aug 23 14:36:03 Installed: kernel-devel-2.6.35.14-95.fc14.x86_64 Aug 23 14:36:13 Installed: kernel-2.6.35.14-95.fc14.x86_64
The system freezes when I try to safely remove the drive. What I see is the blue screen with the Fedora logo, the caps lock key lights up and the system is totally frozen. Following is the information on my external drive gleamed from the messages log file when the device was mounted:
Aug 26 07:53:03 localhost kernel: [ 496.855476] usb 1-1.2: new high speed USB device using ehci_hcd and address 7 Aug 26 07:53:04 localhost kernel: [ 496.942025] usb 1-1.2: New USB device found, idVendor=1058, idProduct=0704 Aug 26 07:53:04 localhost kernel: [ 496.942031] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
how can I disable the automatic file system check after power outages or system crashes? The check sometimes prompts for a key (ignore, repair etc.) but the panels do not have a keyboard.
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
you can refer to this ubuntu thread for context, but i'll sum up what i'm trying to do here to spare the reading. basically i want to be able to schedule a filesystem check with automatic repairs at the next boot time. but i'm not sure if this will try to automatically fix errors which is what i want to do. the reason i want to do this is because i experienced a power outage (the machine was not plugged into an UPS) and i want to make sure everything is ok.
i have created RAID on EDGE server but when i run this command to check RAID status #megacli -CfgDsply -aALL |less
its shows nothing so how can i come to know whether my RAID is degraded or online also in opsview (monitoring tool) i have enable mega raid its shows ok but DISK showing 0
We have a Dell Poweredge 1750 server with 2 harddrives in RAID 1 running Debian Etch. Yesterday one of the hardrives stopped working but no error message appeared in syslog. The only indication was the amber LED diode. Is there a software way how to check that both disks are OK?
This is a Natty system. I ran update manager to update to the latest releases for Natty, and it crashed. I ran it again and it told me it could only do a partial upgrade, and that I should do apt-get install -f. I did that, but apt-get told me the system was locked by another program. Not to worry I thought, I'll just reboot. So I did that, and I think Update-Manager got a lot further through the process than I thought, because my system is borked. It'll boot into Gnome, but when booting up the Boot Screen no longer shows the pretty Ubuntu Logo, but rather a line of text that says "Ubuntu 11.04".
When it gets into Gnome the keyboard and mouse more or less don't work (although the keyboard based Fn+9 and Fn+10 brightness control still works) and there is no desktop background. After about 30 seconds something crashes but I can't click on it to find out what. Going into the recovery console doesn't help either. The latest Kernel (2.6.38-7) stops moving forwards after "Begin:Running /scripts/init-bottom...done". has occurred for the second time. Luckily I still have the previous kernel, which gets to the same spot and then tells me: "init: udevtrigger main process (390) terminated with status 1" and then "init: udevtrigger post-stop process (394) terminated with status 1".
I then get the message "The disc drive for / is not ready yet or not present. Continue to wait; or Press S to skip mounting or M for manual recovery". S goes back to "Begin:Running /scripts/init-bottom...done" a second time, M brings up the message: "Root filesystem check failed. A maintenance shell will now be started" and then it asks for the root password and gives me a terminal. Everything seems to be there, but apt-get and dpkg both can't do anything as the filesystem is read only.
