Fedora :: Software Raid 5 - UUID And Md Number Changes On Reboot?
Jun 18, 2010
So I recently set up a fedora 13 server using software raid. Let me go over the initial install and maybe that will help explain why I'm running into problems with one of the arrays. During installation I had only 2 disks in the equipment (WD 750GB each) Partitioned them thusly:
Code:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00062206
[Code]...
View 3 Replies
ADVERTISEMENT
Feb 1, 2010
I put my two SATA hard drives in a new computer (new mb, cpu, no pci SATA adapter, built-in nVidia graphics), and I thought everything was going well. The Mythbuntu logo came up, but the bar at the bottom did not move. It eventually dropped me out to a (initramfs) prompt.
When I used the recovery mode, this is where it had problems:
[ 4.756000]ata1:SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 5.068000]ata2:SATA link down (SSTatus 0 SControl 300)
[ 5.552000]ata3:SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 5.864000]ata4:SATA link down (SSTatus 0 SControl 300)
[Code]....
I had a SATA PCI card in my old computer, would adding that to the new system make it work? Is there someway to update the UUID numbers (I think I have done this before).
View 5 Replies
View Related
May 9, 2010
I'm running 64bit Lucid. I've recently had a severe problem with my softraid (5) array, and have had to recreate the array to fix it. However this now means that something is up with GRUB/initramfs, and booting times out while waiting for the root device (md0) to be ready. /boot is on a normal partition, not the raid array itself. A friend of mine has rebuilt my initramfs file with the new UUID, but now I get the message: 'Kernel panic not syncing: VFS: unable to mount root fs on unknown-block (9,0)'.So my question is either how do I sort this error, OR how do I rebuild initramfs/grub in a way that will boot?
View 6 Replies
View Related
Nov 20, 2010
I recently upgrade to Fedora 14 from 13. It was an in-place upgrade. I can't recall for sure, but I do believe I had these problems in F13 before the upgrade. The F13 install was from a Live CD. Anyway, I have a three drive RAID 5 array setup - 3x 750GB. For some very annoying reason, each time I reboot my F14 system, it hangs with an error about not being able to find a superblock on /dev/md126 and /dev/md127. I have tried to stop and remove /dev/md126 and /dev/md127 but they always seem to come back. I have also noticed in the output of fdisk -l that drives sda and sdd like to swap places sometimes for an unknown (to me) reason. Any other output that is needed, please ask. I recreated the array just yesterday with:
Code:
mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
I would cat mdadm.conf in /etc, but I removed it previously to try to figure out the problem and it was not
[code]....
View 1 Replies
View Related
Jan 6, 2011
1st I am relatively new to linux (but not to *nix). I have 4 disks assembled in the following intel ahci bios fake raid arrays:
2x320GB RAID1 - used for operating systems md126
2x1TB RAID1 - used for data md125
I have used the raid of size 320GB to install my operating system and the second raid I didn't even select during the installation of Fedora 14. After successful partitioning and installation of Fedora, I tried to make the second array available, it was possible to make it visible in linux with mdadm --assembe --scan , after that I created one maximum size partition and 1 maximum size ext4 filesystem in it. Mounted, and used it. After restart - a few I/O errors during boot regarding md125 + inability to mount the filesystem on it and dropped into repair shell. I commented the filesystem in fstab and it booted. To my surprise, the array was marked as "auto read only":
[Code]...
and the partition in it was not available as device special file in /dev:
[Code]...
View 1 Replies
View Related
Jun 28, 2010
I have an SiI hardware SATA RAID card, with two 500GB disks in mirrored RAID configuration. When I first plugged them in and set it up, things seemed to work ok, but on boot the raid controller told me that the RAID needed rebuilding, and it would happen automatically after POST. So I didn't worry about it, and the drive mounted fine, and it's been that way for years. I just went in and manually on-line rebuilt the RAID in the controller's BIOS, and now when I boot into Ubuntu, both disks show up in fdisk, but neither show up in /dev/disk/by-uuid. Am I missing something?
View 9 Replies
View Related
Feb 23, 2010
When every reboot, the eth number is increasing one, such as eth1 becomes eth2,...
I have deleted the 75-persistent-net-generator.rules in the ubuntu 9.10 PC
but In the file 70-persistent-net.rules, the eth number is still increasing by one when every reboot?
View 1 Replies
View Related
Oct 27, 2010
So I have been doing some RAID 5 performance testing and am getting some bad write performance when configuring the RAID with an even number of drives. I'm running kernel 2.6.30 with software based RAID 5. This seems rather odd and doesn't make much since to me. For RAID 0 my performance consistently increases as I add more drives, but this is not the case for RAID 5. Does anyone know why I might be seeing lower performance when constructing my RAID 5 with 4 or 6 drives rather than 3 or 5?
View 2 Replies
View Related
Jan 7, 2010
This has to be the sixth time I am going to have to reinstall Ubuntu (Can't get enough of that Linux greatness) in the past 6 months. I just don't understand what exactly is wrong, I don't install anything extra (but the ubuntu restricted extras) yet updates that ask me to reboot will take me to a GRUB command line screen and trying to boot through the command line interface gives me an, "Invalid Magic Number", error.
There should be an official tool for when problems like this come up, so that users like me can easily move their files off their HDD before reinstalling. I didn't come here to rant but, does anyone know what may be causing this everytime, how it can be avoided maybe even how to deal with the Magic Number error and boot in (I wouldn't mind typing in the commands every time BTW)?
My system
Hp Compaq 6730s
2.0Ghz 575 Celeron
4GB RAM
Intel X4500MHD
Broadcom 802.11b/g
View 2 Replies
View Related
May 13, 2010
I have two SAS RAID controller cards in a Dell server in slots 2 & 3, both with an array hanging off them. I went to install a third card into slot 1, but then when it boots it says two of my sd's have bad magic number in the super-block and it wants me to create an alternative one, which I don't want to do. If i remove the new card, the server boots perfectly like it did before I added the new card. Is the new card trying to control stuff that isn't hooked up to it because its in slot 1, so its confusing RHEL?
View 5 Replies
View Related
Jan 7, 2010
I currently am setting up an htpc running Karmic. The problem I am having is getting my Raid 0 to be mountable. My raid is not my boot partition, but is for data storage. My setup is a zotac motherboard with three sata connectors. I have a 300 GB drive, my eSata port, and my DVD attached to these. In the PCIe expansion slot I have installed Syba 2 port Sata PCIe 1a card using the Sil3132 sata II host chipset. Off of this I have 2 1.5Tib Hdds that I am setting up as Raid 0. During the boot I enter the chipset BIOS and establish this as a Raid 0.
When I install Karmic it sees the Raid and my 300 GB drive so I install to the 300 GB Drive and everything works fine. I am able to boot to the Hdd and run the OS. I then installed GParted and setup a partition on my RAID as GPT since I want one large partition of 2.78Tib. I then Format it through GParted as ext4 and I am able to mount and access it. I then reboot the system, and can no longer mount the filesystem. What I found interesting is If I reopen GParted I can then mount it. I traced it down to the fact that the until I access GParted the Block Special Device (sil_bgabagabaedd1) does not appear in /dev/mapper. Everytime I reboot I need to go into GParted to restore the Block Special Device then it is mounted. I think I am missing something in the raid setup as to why it is not being retained. What have I missed? What do I need to do to retain the Block Special Device? Is there a boot config setting?
Edit: I did further research and found that if I do kpartx it will appear just as gparted, but on reboot vanishes. I found something similar at this thread but not comfortable in updating dmraid: [URL] I think it is related to gpt and I will try to use a smaller partition to see if the behavior changes.
View 1 Replies
View Related
Apr 24, 2011
I had some issues with my RAID6 array (with 15 disks), where 5 disks got disconnected (each five disks is connected to the motherboard via 1 SATA cable), which brought down the RAID array. I fixed this problem via readding the disks and running the array:
Code:
mdadm -R /dev/md1
However, after rebooting, the array appears inactive, and I have to go through the same motions to fix this and make it active.
The array is present in the /etc/mdadm/mdadm.conf, though also 2 other raid arrays (3 arrays total):
Code:
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
[code]...
View 1 Replies
View Related
Mar 24, 2009
configure my raid devices so it can be started and mounted at start-up.
View 1 Replies
View Related
Aug 12, 2010
I just configured two raid setups but after a reboot they are not mounted and seem to be inactive.
md127 = sde1, sdf1 and sdi1 (raid 5)
md0 = sda1 and sdh1 (raid 0)
Code:
root@server /]# cat /proc/mdstat
Personalities :
md127 : inactive sdf1[1](S) sde1[2](S)
78156032 blocks
md0 : inactive sda1[0](S)
488382977 blocks super 1.2
unused devices: <none>
Code:
[root@server /]# fdisk -l | grep "Disk /"
Disk /dev/sda: 500.1 GB, 500107862016 bytes
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
Disk /dev/sdc: 122.9 GB, 122942324736 bytes
Disk /dev/sdd: 160.0 GB, 160041885696 bytes
Disk /dev/sde: 40.0 GB, 40020664320 bytes
Disk /dev/sdf: 40.0 GB, 40020664320 bytes
Disk /dev/sdg: 1500.3 GB, 1500301910016 bytes
Disk /dev/sdh: 251.0 GB, 251000193024 bytes
Disk /dev/sdi: 40.0 GB, 40020664320 bytes
Disk /dev/sdj: 500.1 GB, 500107862016 bytes
Code:
[root@server /]# cat /etc/mdadm.conf
DEVICE /dev/sdi1 /dev/sdf1 /dev/sde1 /dev/sda1 /dev/sdh1
ARRAY /dev/md127 UUID=5dc0cf7a:8c715104:04894333:532a878b auto=yes
ARRAY /dev/md0 UUID=65c49170:733df717:435e470b:3334ee94 auto=yes
As you can see they now show up as inactive. And for some reason sdi1 and sdh1 are not even listed. What can I do to get them back? To make matters worse I placed some important data on them, and even if I was clever enough to keep an extra copy on another drive, guess which drive that was? So, I need to get them activated as is (at least so I can get the data of them) before I can rebuild them from scratch. I'm running Mandriva 2010.1 and rated tehm using the built in disk partitioner.
View 14 Replies
View Related
Jun 22, 2010
I installed CentOS 5.5. After install, I decided to put 3 identical disk for raid 5. All the disks are IDE disk. Then I put a sata disk and partitioned it to add another partition to the raid 5 array. Everything works fine until I rebooted my system. After reboot, the sata partition I added into raid 5 is showing removed. I had to readd it using "mdadm --add" to make raid 5 array works.
View 5 Replies
View Related
Nov 5, 2010
There seems to be a problem with Raid on Debian. I got a new Fujitsu Primergy TS 100 S1 server, with hardware Raid (and 2 disks) installed everything nicely over the net including GRUB - but when it comes to reboot the system does not boot.
Is there anybody here who knows about the problem?
View 1 Replies
View Related
Jun 20, 2010
Basically, I installed Debian Lenny creating two RAID 1 devices on two 1 TB disks during installation. /dev/md0 for swap and /dev/md1 for "/"
I did not pay much attention, but it seemed to work fine at start - both raid devices were up early during boot, I think. After that I upgraded the system into testing which involved at least upgrading GRUB to 1.97 and compiling & installing a new 2.6.34 kernel ( udev refused to upgrade with old kernel ) Last part was a bit messy, but in the end I have it working.
Let me describe my HDDs setup: when I do "sudo fdisk -l" it gives me sda1,sda2 raid partitions on sda, sdb1,sdb2 raid partitions on sdb which are my two 1 TB drives and sdc1, sdc2, sdc5 for my 3rd 160GB drive I actually boot from ( I mean GRUB is installed there, and its chosen as boot device in BIOS ). The problem is that raid starts degraded every time ( starts with 1 out of 2 devices ). When doing " cat /proc/mdstat " I get "U_" statuses and 2nd devices is "removed" on both md devices.
I can successfully run partx -a sdb, which gives me sdb1 and sdb2 and then I readd those to raid devices using " sudo mdadm --add /dev/md0 /dev/sda1 ". After I read devices it syncs the disks and after about 3 hours I see fine status in mdstat. However when I reboot, it again starts with degraded array. I get a feeling that after I read the disk and sync array I need to update some configuration somewhere, I tried to " sudo mdadm --examine --scan " but its output is no different from my current /etc/mdadm/mdadm.conf even after I readd the disks and sync.
View 1 Replies
View Related
May 30, 2011
Every time I reboot my server, one of my hard drives drops out of the RAID5 array. I'm pretty sure that there's nothing wrong with the drive itself. I bought all three drives at the same time, and they are identical in make/model/capacity. While the server is running, it's smooth sailing. However, whenever I shut down or reboot, I get an email message that the array is degraded. It's always /dev/sda1 that drops out of the array. I can always rebuild the array by adding the partition back in, but it's a bit of a pain. Any suggestions on how to troubleshoot this?
View 13 Replies
View Related
Jul 24, 2010
I've got a file server with two RAID volumes. The one in question is 6 1TB SATA drives in a RAID6 configuration. I recently thought one drive was becoming faulty, so I removed it from the set. After running some stress tests, I determined my underlying problem hadn't cleared up. I added the disk back, which started the resync. Later on, the underlying problem caused another lock up. After a hard-reboot, the array will not start. I'm out of ideas on how to kick this over.
Code:
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
[code]....
View 4 Replies
View Related
Jun 24, 2009
I've tried to install Fedora 11, both 32 and 64 on my main machine.It could not install as it stops on the first install window. I've already filed a bug but really haven't seen any feed back yet.The bug has something to do with Anaconda and the Raid array but I really can't tell.
I have an Intel Board (see signature). I am running intel raid software under W7 currently.It works fine. But, I'm wondering, when I attempt to install F!!, is my current raid set-up causing problems? Do I need to get rid of the intel raid software and use a Fedor/Linux raid program to manage the raid array??
View 2 Replies
View Related
Mar 25, 2010
I have a 10x2tb disk array that i'm trying to build into a single software raid 5 i have tried this 2 times now the first it made it to 58.7% and the machine locked up and the array would not restart after a reboot. On my 2nd try all was looking good until about 50% i noticed that the speed dropped in 1/2 and that ksoftirqd/2 is taking up a lot of cpu (about 90%) the md0_resync and md0_raid5 are also taking 60-90% when the build started they took 7%. when i do a dmesg i see a lot of the message compute_blocknr: map not correct.
For a little info on the physical setup this is running on an Atom 510 with 2GB of mem the drives are connected to an addonics 4-Port RAID 5 / JBOD SATA II PCI Controller using the sil3124 chipset. I'm using 2 addonics 5X1 SATA Port Multiplier connected to the controller to get the 10 drives attached. All drive show up and don't seem to have any issues. I'm running a fully updated as of 3/20/10 version of centos 5.4
I will let this continue to run over night but i expect it to be locked up by morning if it follows what the last attempt did.
View 9 Replies
View Related
Dec 9, 2010
I have created a raid0 on my system using mdadm. It works wonderfully except when I reboot the system.It was created as md0 and the mdadm.conf states that. But when I reboot the system it will change the device to md127 and thus the raid doesn't mount because the fstab has md0 in it. If I change the fstab to mount md127 it will invariably change the device back to md0. The other problem with this is my system disk is sdc and sdd when md0 gets mounted correctly. The raid disks under md0 are sda and sdb. It reassigns the drives letters when it setups up md127. I really don't care what device number it uses but consistency would be really nice.
Code:
mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Thu Nov 18 14:06:42 2010
Raid Level : raid0
Array Size : 1953517568 (1863.02 GiB 2000.40 GB)
[Code]...
From a hardware standpoint I have two sata cards in the system ( Highpoint and an ATTO). The Highpoint is where the disks for the software raid are. The ATTO also has a couple raids setup but they are hardware raid so the system sees them as one device.
View 3 Replies
View Related
Apr 3, 2009
I have 2 CPUs Which are Intel and AMD based. I used F9 before and didnt have any issues while I removed the hdd that I'd installed F9 on INTEL based and then put my hdd on my AMD based cpu. Well it booted and ran perfectly no issues came up.And then I've done the upgrade to F10 (clean install on INTEL). I do the same case above.But I got error msgs it said that the UUID cannot be found (I was using label on F9 fstab and worked fine).
I put back my hdd to intel based cpu and then try to edit my fstab and menu.lst (change UUID to LABEL). WOW I thought by changing UUID from fstab and menu.lst would resolve my problem but it doesnt solve anything. My devices (sda1/2/3, /boot, and /home) cannot be reconized.Well do you guys know how to change UUID to LABEL? and what exactly my problem?
View 2 Replies
View Related
Apr 7, 2011
I am trying to figure out how to get the UUID for some of my external hard drives.the internet revealed a couple of promising leads, this is what I have tried so far:
ls -l /dev/disk/by-uuid -> didn't list the hard discs
blkid -> didn't list the hard discs
lsusb -v -> listed the hard disc but no uuid
A normally formatted usb key is listed with uuid. The external hard discs are fully encrypted by truecrypt(realcrypt). I have been reading not so great things about that itself, but for now I don't have a promising alternative that I can use with windows as well.Any google searches don't seem to cast any new light on this for me,I'd be open to suggestions if there's a better way to get a definite ID for a hard drive... I just need to be able to mount it with realcrypt
View 3 Replies
View Related
Mar 11, 2010
I am trying to recover some data on some drives that are in the same LVM. When I upgraded the motherboard, I had complications getting the drives to all load under the LVM, and in the process I made the mistake of formatting one of the drives. The problem now is that the UUID changed on the drive so when I try to mount the LVM it can't find device with a certain UUID. When I try to set the UUID back to the old one it says 'Invalid UUID format'.
I can set it to a UUID generated through 'uuidgen', si I then noticed that the format of that UUID is different than the old one which I'm trying to set it to. Why is that? Is there a way I can get it to change to the old one in the different format?
The old format: yQtrVB-5jCk-vF10-05c2-AcDL-GNn1-ivdxxh
The new format: d5224587-a6cd-4a66-a12b-d7b75eec5871
View 1 Replies
View Related
Aug 17, 2010
when my grub references the UUID for the root= parameter, I get a kernel crash. If I change the root= parameter to /dev/<partition>, grub boots without a problem (f13 64-bit)
[Code]....
View 8 Replies
View Related
Feb 16, 2011
last -a shows server rebooted, how to identify the source or cause of reboot? thx reboot system boot Wed Feb 16 08:52 (02:0 2.6.21.7-2.fc8xen
View 2 Replies
View Related
Feb 1, 2011
Could any RAID gurus kindly assist me on the following RAID-5 issue?I have an mdadm-created RAID5 array consisting of 4 discs. One of the discs was dropping out, so I decided to replace it. Somehow, this went terribly wrong and I succeeded in marking two of the drives as faulty, and the re-adding them as spare.
Now the array is (logically) no longer able to start:
mdadm: Not enough devices to start the array.Degraded and can't create RAID ,auto stop RAID [md1]
I was able to examine the disks though:
Code:
root@127.0.0.1:/etc# mdadm --examine /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 00.90.00
code....
Code:
mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
As I don't want to ruin the maybe small chance I have left to rescue my data, I would like to hear the input of this wise community.
View 4 Replies
View Related
Jul 14, 2010
I've been away from Fedora for a long time, since FC3/4. I seem to recall that at that time grub in Fedora used the standard drive notation such as /dev/sdax instead of the current UUID. Can anyone tell me why this change was made?
Seems to me that using UUIDs presents severe problems if a drive has to be replaced as the restore media (we all backup, don't we?) would not work without modification. How does one determine trhe UUID of a new drive to change the restore media? Sounds like a chickenand-egg routine. There must be some way which I haven't run accross yet. I do notice through experimentation that the standard notation still works, at least in /etc/fstab.
View 7 Replies
View Related
Apr 2, 2010
I set up a 4 disk RAID 5 arry using the Palimpsest utility several months ago, and all was well until last week. After a hard reboot, the RAID array failed to come up with the message: Failed activating drive: Error assembling array: mdadm exited with exit code 1: mdadm: cannot open device /dev/sdb1: Device or resource busy mdadm: /dev/sdb1 has no superblock - assembly aborted
The disk in question was still visible in Palimpsest, and the test utility succeeded. After searching the archives, I checked /proc/mdstat to see if another array had possession of the device. No such luck. I looked in syslog and found this, but don't know how to proceed:
Mar 28 08:42:26 david-phenom kernel: [ 61.297959] md: md0 stopped.
Mar 28 08:42:26 david-phenom kernel: [ 61.418841] md: bind<sdc1>
Mar 28 08:42:26 david-phenom kernel: [ 61.424179] md: bind<sdb1>
Mar 28 08:42:26 david-phenom kernel: [ 61.424384] md: bind<sda1>
Mar 28 08:42:26 david-phenom kernel: [ 61.424543] md: bind<sdd1>
[Code]...
View 1 Replies
View Related
