i am setting up a software raid6 for the first time. To test the raid i removed a drive from the array by popping it out of the enclosure. mdadm marked the drive as F and everything seemed well. From what i gather the next step is to remove the drive from the array (mdadm /dev/md0 -r sdf), when i try this i receive the error:
mdadm: cannot find /dev/sdf: No such file or directory
That is true, when i plugged the drive back in the machine now recognizes it as /dev/sdk. My question is how do i remove this non-existent failed drive from my array as i was able to re-add it just fine as /dev/sdk with mdadm /dev/md0 -a /dev/sdk
Also, is there any way to define a drive based on id or something similar to the same drive name to avoid this?
I know this is probably a very generic linux question, but since I am using ubuntu - I thought it safer to ask here. I have jumped into the deep end of linux - and I am afraid that I will be forced to swim sooner rather than later.
Let me start at the beginning - I am and probably will be a windows fan for a long time - let me not list the reasons - or else you guys will probably hang met out to dry - the one thing I have discovered - is that windows sucks in generating a software RAID - especially the RAID 5 that i was looking for any case - after loosing plenty data via windose - I decided to attempt linux/ ubuntu. I must say - so far so good.
I used this excellent guide: [URL] and must say that the raid is performing admirably - I am currently busy adding/growing the 12th 1Tb drive onto the RAID, and no issues so far(some other major WOW advantages i have noticed... like speed writing too and reading from the RAID.. )
My questions : If one drive fails on the array(for example SDK1) - how the heck do i determine which physical hardware device it is that has failed? (without compromising the other data - yes unfortunately I cant afford to backup 11TB of data - personal server). I don't have space in the box for a mouse - not even talking about a hot spare drive - thus adding the backup drive before removing the faulty drive is rather difficult - but if that's the only option I will have to keep with that as everybody know RAID5 is only 1 drive backup - so partly I would like to solve the issue as quick as possible -without having to resort to disconnecting one drive at a time to determine which is which. If the drive assignments ( SDA/SDB/SDC) is constant
What is the most intuitive/fast way to determine that a faulty drive exist in the array? - i.e. is there some sort of GUI solution for MDADM that will tell me the moment that a drive has turned faulty? - The box is currently not on the internet -meaning notification via email is not possible. Is there a non-destructible way to convert the RAID-5 to RAID-6? (I would rather sacrifice 1TB of free space - for peace of mind) - and RAID6 will make troubleshooting a bit easier since 3 drives will have to fail before data-loss.
I tryed to install ubuntu 10.04 using the beta alternative install cd.
Everything went fine until the partitioning section.
I choose manual partitioning and all my existing partitions were detected correctly included my 2 mdadm raid0 arrays.
I choose md0 as my / partition and choose to format the partition
I choose md1 as my /home partition as choose to keep the data
When I choose to continue and write the changes to disk the install started to create an ext4 partition on md0, the installer then stopped with an error that the kernel could not reread the partition table.
I aborted the installation at this point.
Now I can not access either of my arrays.
I have booted a livecd and installed mdadm. When I checked /etc/mdadm/mdadm.conf my existing arrays were already listed.
Code: # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. #
I just had a whole 2TB Software RAID 5 blow up on me. I rebooted my server, which i hardly ever do and low and behold i loose one of my raid 5 sets. It seems like two of the disks are not showing up properly.. What i mean by that is the OS picks up the disks, but it doesnt see the partitions.
I ran smartct -l on all the drives in question and they're all in good working order.
Is there some sort of repair tool i can use to scan the busted drives (since they're available) to fix any possible errors that might be present.
Here is what the "good" drive looks like when i use sfdisk:
Quote:
sudo sfdisk -l /dev/sda Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sda1 0+ 121600 121601- 976760001 83 Linux /dev/sda2 0 - 0 0 0 Empty
I bought a disk to a friend that used it in a raid array, using the entire disk for the raid usage. To put that disk on service, i used dd-rescue to copy my old disk entirely, and managed to grow and setup a the partition table without losing any data. My last step was to create a RAID between my entire old disk, with a single partition and a partition of the same size on my new disk. I ran into some problems, but i manage to somehow fix it imperfectly, but now this setup is working properly. The problems (and imperfection) came from an issue it did not suspected : at some point, the original RAID superblock of the new disk, living in /dev/sda, resisted to dd-rescue, and so it is scanned by mdadm that tries, obviously unsuccessfully, to use it.
Partition layout :
Code:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
this setup is working properly besides this raid5 declared on sda, so that is shows up here and there. Since it is using the same device name that my other, proper raid setup, i don't know how to deactivate it since mdadm uses the /dev/mdx name to identify arrays.
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 have SLES10-SP3 running on an Intel SR1600URHS board with 3 hot-swap SATA disks configured using mdadm as Raid1 with hot spare. If I pull one of the active disks, all file i/o will stop for about 2.5 minutes after which it will start again and the raid array will be rebuilt using the spare disk. Is there any way I can reduce this 2.5 minutes of inactivity? I've tried setting /sys/block/sdX/device/timeout and /sys/block/sdX/device/retries to 1 for all disks, but this hasn't made any difference. The output from messages is:
12:11:56: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen 12:11:56: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x1e data 0 12:11:56: res 40/00:03:00:00:20/00:00:00:00:00/b0 Emask 0x4 (timeout)
Is growing raid 6 in 5.3 centos possible? I'm getting errors when i run mdadm in --grow mode failed : 'mdadm --grow /dev/md0 -n 5 2>&1' -> mdadm: Cannot set device size/shape for /dev/md0: Invalid argument Do i have to create a custom kernel for centos?
I have a strange issue with my RAID5 array - it worked fine for a month, a couple days ago it didn't start on boot with mdadm reporting "Input/Output error" - I didn't panic restarted my computer, same error. Then opened a Disk utility and it reported State: Not running, partially assembled - don't know why, I've pressed Stop RAID Array and started it again, voila - it reported State: Running - I've checked components list and there was nothing wrong with it. So I run Check Array utility, waited almost 3 hours to finish it and it worked since than, till today's morning - I've started my computer, and here we go, same error.
See screenshots:
This is an initial state just after computer startup:
This is after I stop and start RAID5:
This is a components list:
I can see nothing wrong there yet not sure why mdadm fails on boot. I do not really like the windows solution I guess, when I check my array again, it will work fine again, but it then can fail in the same way without known reason.
Today i upgraded my system and started getting error when i update, install or remove a package. The error isn't restricted only to one repository so i thing something is wrong with my system.
Server with 4 disk partitions in an RAID 5 array using md. Yesterday the array failed with two devices showing as faulty. After rebooting from rescue, I was able to force the assembly and start the array and everything looks to be okay as far as the data goes, but when I run: Code: mdadm --examine /dev/sda3
I get (truncating to the interesting bits): Code: Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 1448195216 (690.55 GiB 741.48 GB) Array Size : 4344585216 (2071.66 GiB 2224.43 GB) Used Dev Size : 1448195072 (690.55 GiB 741.48 GB) Array Slot : 0 (0, 1, 2, failed, 3) Array State : Uuuu 1 failed
And Code: mdadm --detail /dev/md1 yields: Code: Array Size : 2172292608 (2071.66 GiB 2224.43 GB) Used Dev Size : 1448195072 (1381.11 GiB 1482.95 GB) Raid Devices : 4 Total Devices : 4 Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Additionally, the 'slot' for devices a-d line up like this: a - 0 b - 1 c - 2 d - 4 (!) The first number 'Array Size' from examine is twice as big as sit should be based on the output from detail and comparing to twinned server, and why does the 'Array State' and 'Array Slot' from examine indicate there's a 5th device that's not indicated anywhere else?
I have 4 WD10EARS drives running in a RAID 5 array using MDADM.Yesterday my OS Drive failed. I have replaced this and installed a fresh copy of Ubuntu 11.04 on it. then installed MDADM, and rebooted the machine, hoping that it would automatically rebuild the array.It hasnt, when i look at the array using Disk Utility, it says that the array is not running. If i try to start the array it says :Error assembling array: mdadm exited with exit code 1: mdadm: failed to RUN_ARRAY /dev/md0: Input/output error
mdadm: Not enough devices to start the array.I have tried MDADM --assemble --scan and it gives this output:mdadm: /dev/md0 assembled from 2 drives - not enough to start the array.I know that there are 4 drives present as they are all showing, but it is only using 2 of them.I also ran MDADM -- detail /dev.md0 which gave:
root@warren-P5K-E:~# mdadm --detail /dev/md0 /dev/md0: Version : 0.90
I am currently having problems with my RAID partition. First two disks were having trouble (sde, sdf). Through smartctl I noticed there were some bad blocks, so first I set them to fail, and readded them so that the RAID array will overwrite these. Since that didn't work, I went ahead and replaced the disks. The recovery process was slow and I left things running overnight. This morning I find out that another disk (sdb) has failed. Strangely enough the array has not become inactive.
Does anyone have any recommendations as the steps to take ahead with regards to recovery/fixing the problem? The disk is basically full so I haven't written anything to disk in the interim of this problem.
I have a raid 5 array that appears to have died. I was just routinely looking at /var/log/messages and noticed that a drive in the array was complaining (via SMARTD).
This is the /home directory, and so is backed up, so it's not critical, but I'd like to get some things that changed after the last backup (the week before I noticed the failure)
Let me start by outlining what I know :
It's a 2TB array spread over three disks (mdadm software RAID5), here are the drives:
MDADM gives the drives :
Now, the array *WAS* up ok, but I umounted it. (in which /dev/md0 was mounted to /home) Yes,I know - I didn't want any changes being made to the array by anything - at least that was my thinking at the time. In hindsight... I would have killed any processes, locked out the server, backed up again and 'then' unmounted it.
But we are where we are, I'm sure there'll be time for recriminations later.
When I try to remount it, I get :
Ok - looks like it's lost the type - it's normally worked, maybe we'll give it a little hint - it's ext3 with a journal.
When I tell it it's an ext3, I get :
Now, before I go charging off specifying superblocks further along the disk, but I can't remember where they're stored.
Neither can I recall what the blocksize I originally created the array as (I have a feeling I specifed 4K, but I could be wrong).
debugfs is only telling me :
I should also point out that this server is hosted, so it's 150 miles away from me at the moment, so I can't just whip them out and dd a copy.
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 an mdadm linear array of 4 500GB drives. One of them had a few bad sectors, so I've dd'ed it to a new one (conv=noerror), and tried to start my array. Mdadm refuses, saying, "mdadm: /dev/md4 assembled from 3 drives - not enough to start the array."I had diffed different samples from different positions on the source and the mirror drive and confirmed they were identical. Checking the superblocks confirms three old drives still having their superblocks as expected, while the newly mirrored one has,
daniel@lnxsrv:~$ sudo mdadm --misc --examine /dev/sdf1 mdadm: No md superblock detected on /dev/sdf1. - and, daniel@lnxsrv:~$ sudo blkid /dev/sdf1
[code]....
As before. The mirror apparently has no uuid, but the original does. To confirm my sanity, I did,
How can the uuid not be the same when bit-for-bit from the very first byte of the drive, covering MFT etc., these two drives are identical according to diff?
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 have 4 drives in my system. Two are SATA and configured in a RAID 1. This is my main drive for the system. The other two drives are IDE drives used to bulk temp storage. Before the upgrade my RAID drives were:
/dev/sda /dev/sdb
I'm not sure what the IDE drives were. Now after the upgrade the IDE drives are:
/dev/sda /dev/sdb
and the RAID SATA drives are:
/dev/sdc /dev/sdd
Needless to say on reboot the raid blow up and the system would not boot. I was able to get it working for now by removing the IDE drives. My current mdadm.conf file is as follows:
Now I assume that I could change the devices to the new devices names. However I was hoping for a better way to do this. The IDE drives are only semi permanent. Is there a way to configure mdadm with partition labels like you can in fstab?
I have a used but good harddrive which I'd like to use as a replacement for a removed harddrive in existing raid1 array. mdadm --detail /dev/md00 0 0 -1 removed1 8 17 1 active sync /dev/sdb1I thought I needed to mark the removed drive as failed but I cannot get mdadm set it to "failed". I issue mdadm --manage /dev/md0 --fail /dev/sda1But mdadm response is:mdadm: hot remove failed for /dev/sda1: no such device or addressI thought I must mark the failed drive as "failed" to prevent raid1 from trying to mirror in wrong direction when I install my used-but-good disk. I want to reformat the good used drive first right? I believe I must prevent raid array from automatically try to mirror in the wrong direction.
This has been bothering me for years now...when I go to remove a thumb drive from my computer, I have two options when I right click the device eject and safely remove. What on earth is the difference supposed to be?
To remove pendrive when I click the 'safely remove' tab instead of getting removed from the desktop it reappears again. This problem is there in fedora 14
Anyone else seeing this? I do 'safely remove' to remove USB flash drive. disappears. Five seconds (or less) later, it reappears. The second time I do 'safely remove', it stays gone.
120GB Sata HDD - Primary OS drive 3 x 1.0TB Sata HDD - Raid 5 array
This is on a C2D MSI P35 Platinum board. Anyway, did a fresh install of F12 on the 120GB, which I had problems with - Anaconda refused to see the drive. Fedora Live could see it fine, and it was listed as an 'nvidia_raid_member' - no idea why, but I completely erased the disc under the Live CD and proceeded to install F12.
Once F12 was installed, I loaded up mdadm to re-activate my Raid 5 array, using 'sudo mdadm --assemble --uuidthe uuid) - and it started with only 2 of the 3 drives. My /dev/sdb drive did not activate into the array, due to what mdadm said was a mismatched UUID. Ok, so I erased /dev/sdb, intending to rebuild the array. Erased /dev/sdb, and then attempted 'sudo mdadm --add /dev/md0 /dev/sdb' and I get this error: "mdadm: Cannot add disks to a 'member' array, perform this operation on the parent container" - I can find NO information on this error message.
[Code].....
I don't believe the hard drives are connected in the exact same order they were in before - I disconnected everything in the system and blew it out (it was pretty dusty)
I need to get a backup copy of a huge directory on one of our RHEL servers. Rather than hook the external USB drive up to my PC and manually copy it all across the network, can I just plug it in to one of my USB ports on the server and rsync it?I know how to do the rsync, I just don't know how to get the USB drive to show up when I do a df -h and how to properly remove it before unplugging it from the server. this is a live server, so I can't go playing around and possibly mess something up.
I have 350GB external Western Digital USB hard Drive.When I try to remove it from the system by executing Safely Remove Drive menu the fedora 15 system gets stuck.The processor starts giving a hum sound and it goes on even if it is left for half an hour in the stuck state.The Mouse is not working and everything is halted.
I am trying to replace an old, smaller, and dying laptop hard drive with a newer one, using a USB external drive. I first tried cloning disk to disk with Clonezilla, but it failed after cloning my root, swap, and /home directories it froze when it tried to reinstall grub. After 2x trying, I switched to dd, which I have never really used (I am fairly new to Linux in general). The actual command I used was:
All seemed ok and after approximately 2 hours my 80GB drive had been cloned onto my new 250GB, with dd giving what appeared to be a satisfactory closure summary. I tried to mount and access the drive from my external USB enclosure but could not view it, though the data is there, I believe, as the size and bytes show... The error that Dolphin is giving me is:
Quote:
error - wrong fstype, bad option, bad superblock on /dev/sdb1 Missing codepage or helper program or other error. When I installed the new drive directly into my laptop, it begins to boot (Sabayon 5.4, 2.6.35 kernel) but almost immediately I get (handwritten down, but this is close):
Quote:
detected real_root mounting /dev/sda1 on /newroot failed: input/output error !! Could not mount specified ROOT, try again !! Could not find the root block device in .
[code]....
I am assuming that my issue has something to do with grub, and maybe specific UUIDs that don't match (?) but I'm not really certain. I have both Grub Legacy 0.9x and the newer Grub 2 installed (Sabayon is already moving over) but I still boot with Legacy, not with the new 2, as I don't know how to switch, and am not sure if I should yet. I thought that dd copied bit for bit, and I added the noerrorï just to try to get it all transferred, so I don't know what went wrong exactly, though something seems wrong with grub and the bootloader, I guess...
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?
Whenever I try and add software through packagekit I get an error telling me that Authorization failed. I would assume that I need to enter my password before the install begins but the utility never asks for it. I am able to start package kit with sudo and it then adds the software but that keeps most of the packages from running as they were added as root.
