Fedora :: F14 - Very Annoyed With Software RAID Setup - Cannot Find Superblock At Reboot?
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
ADVERTISEMENT
Sep 16, 2010
i trying to recreate(after zero-superblock) raid 10 but get stuck with near=1, far=2 layout, how i can setup this layout using mdadm.
View 2 Replies
View Related
Apr 14, 2010
One of my raid disks (was a software raid5 with 4 drives) failured. I wanted to buy a new 1.5TB harddisk anyway so i i copied all the Raid data onto the new disk and disconnected the old ones. But then the new Disc crashed right before i could mirror it with another 1.5TB disk. So i need to reassemble my old Raid 5 now. I connected the drives in the former order except the first one, because this was the failed disk. The problem is, mdadm can't find the raid, no superblocks. Fdisk doesnt show mdraid superblocks, too. But fdisk has never showed superblocks. The thing is, this raid was crypted, but i crypted the /dev/md0, so this doesn't affect anything here, or?
some infos:
Code:
server:~# mdadm --misc -d /dev/sda
mdadm: option -d not valid in misc mode
server:~# mdadm --misc -t /dev/sda
[code]....
Disk /dev/sdc doesn't contain a valid partition table But fdisk always said there is no valid partition table and the raid was working.
View 4 Replies
View Related
Apr 5, 2011
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.
View 4 Replies
View Related
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
View Related
Jun 16, 2010
I have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Does anyone know who I can repair the drive and retrive data?
View 1 Replies
View Related
May 14, 2011
After several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
View 9 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
May 12, 2010
I'm logged into a server through the CLI and did a df -T and confirmed all my volumes are ext3. but when I do a tune2fs -l /dev/sde it tells me
tune2fs 1.39 (29-May-2006)
tune2fs: Permission denied while trying to open /dev/sde
Couldn't find valid filesystem superblock.
I don't have root access on the server, but is that why it's complaining, or is my syntax incorrect?
View 8 Replies
View Related
Dec 7, 2010
I have a Dell workstation, 2 HDD, HDD 1 setuped Red Hat 5.3 with LVM, and that HDD 2 is empty, not install RAID 1. And, I want to setup RAID 1 (hardware RAID)...but, have a problem. I don't want to lost data on HDD 1 when I setup raid, I try ghost or backup it, but when I restore, it error because LVM is setup on that.
View 4 Replies
View Related
Aug 11, 2009
I've been trying to setup RAID 10 with Fedora 11 on my desktop using this tutorial:[URL].. Everything has been going well, except when following the instructions and getting ready to format, it says I need to define / and boot partitions. This was never included in the instructions.
- LVM Volume Gropus
-- vg_jordan
--- fedoraRAID (type: ext4)
- RAID Devices
-- /dev/md0 (mountpoint/RAID/volume: vg_jordan ; type: LVM)
[Code]...
View 2 Replies
View Related
Nov 18, 2009
I am trying to set up bridge, and everything seems to be ok, except 1 thing, it disappears after reboot. So, what I am doing:
Code:
brctl addbr br0
brctl addif br0 eth0
and adding /etc/sysconfig/network-scripts/ifcfg-br0, here it is:
Code:
GATEWAY=192.168.1.1
DEVICE=br0
BOOTPROTO=none
NETMASK=255.255.255.0
DNS1=208.67.222.222
DNS2=208.67.220.220
TYPE=bridge
HWADDR=00:18:f3:75:18:78
IPADDR=192.168.1.3
IPV6INIT=no
ONBOOT=yes
USERCTL=no
and my ifcfg-eth0 is:
Code:
GATEWAY=192.168.1.1
DEVICE=eth0
BOOTPROTO=none
NETMASK=255.255.255.0
DNS1=208.67.222.222
DNS2=208.67.220.220
TYPE=bridge
HWADDR=00:18:f3:75:18:78
IPADDR=192.168.1.3
IPV6INIT=no
ONBOOT=yes
USERCTL=no
How to make it working after reboot?
View 1 Replies
View Related
Jan 22, 2009
I have had no problem installing Fedora OS on any of my Dell servers prior to this post. Anyway, I wouldn't call this a problem but recently, we bought another DELL server with Quad Core, 4GB, etc... AND this model has 2 swappable SAS Harddrives.
I wouldn't call myself an expert but then again I am not a newbie too. However, I have never setup any RAID before and now I am forced to setup RAID1 on this server. So, in a way, I am a newbie in setting up RAID
Would someone please point me in the right direction as I have no idea what I am supposed to do to setup the RAID. FYI, I will be installing Fedora 10 64bit on this server. I would appreciate if you can start from the very beginning, ie. partitioning, formatting the harddrives during OS installation, etc..
View 3 Replies
View Related
Jun 7, 2010
I'm looking to set up a bit of a home server, and am wondering about storage. What I'd like is something like RAID 6, which has good redundancy built-in, but with this being a home server, I'd prefer to start a little smaller and leave room to build it up in future. I'd been looking at commercial products like the 'drobo', which seems fairly ideal, but I'd really like to see if I can do it myself. I understand that throwing the RAID into an LVM will allow for some expansion, but the last time I checked, most RAID setups called for the same sized disks, or at least limited the array by the size of the smallest disk present.
What I'd like is the ability to build a basic framework with a few cheap disks, and then as things start filling up, to be able to add larger ones (perhaps eventually pulling out smaller ones as though they'd failed and replacing them with big ones)
View 1 Replies
View Related
Nov 18, 2009
I just tried to install Fedora 12 x_64 on a machine that is currently running Fedora 11 x_64. It's a new machine for use as a server and is running a Phenom II 4 core on a gigabyte M/B - 4GB RAM, onboard ATI graphics, an Adaptec 5405Z RAID Controller that is in the 16 lane PCIe slot, and 3 SSD SATA dives in a RAID 0.I installed Fedora 11 x_64 on this machine just last week and it went perfectly smooth. The install recognized the video hardware, controller card and the RAID, installed correctly, boots fine, runs solid.When I attempt to install Fedora 12 x_64 on the same machine, it does NOT recognize the controller, nor the RAID and doesn't seem to like the video hardware. I stuck on a floppy drive and made a driver disk from the Adaptec provided Linux drivers, but the install fails to mount the floppy when I try to add the driver during boot from DVD - although it tries. (It's possible that my floppy drive and/or disks are too old to be useful. Seriously, loading drivers from a FLOPPY? Most computers don't even HAVE one any more.Sheesh...). The video also seems squirrelly and works better using the "simple" video drivers.
Anyone got any clues on this. It seems odd that the newer version works less well than the previous one.Maybe I'll try a different .iso - CDs or a live version or something just to check - and maybe try an install on a different machine. Yes, I put the install DVD through the self-test and it passed. I have tried 2 different copies and both fail.LATER - tried with live CD - boots OK, splash screen is OK, after bootup finishes it looks like maybe it's trying to start a different video driver - then the screen goes black and stays that way. Tomorrow I may stick in a discrete video card and see if that makes any difference.
Still Later: I have tried discrete video card, tried moving the RAID controller to the 4 lane slot, tried to install a driver from floppy (still no go) and have tried noprobe on boot command line. Although the "noprobe" got the video to keep going (albeit at a low resolution) it STILL refuses to see the RAID controller. The LED indicators on the RAID card SEEM to be indicating that the card locks up during Fedora 12 boot, but I haven't checked on that just yet. Fedora 11 continues to boot and run fine on the same machine - I'm running it right now. as I type this.Later yet: Ubuntu 9.10 86_64 that was released a couple weeks ago DOES, IN FACT see the controller and the RAID when I run the install process. Looks like Fedora 12 is badly broken after all. (Damn those even numbered releases anyway.....{;>D)=) Guess I'm going to be "stuck" with either Ubuntu or Fedora 11 unless a solution appears pretty soon. I have sent an inquiry to Adaptec, but I'm guessing they are going to say, "we don't support Fedora linux except Fedora 5 and Fedora 6" as those are the only drivers they seem to have available
Friday 11/20 - I've attached a SATA drive to the same computer. By using the "basic" video driver from the install DVD I am able to install F12 to the SATA drive without issue - it installs fine, boots fine, runs fine. However, it still will NOT see the RAID controller. I tried installing the driver .rpm from the disk that came from Adaptec, but the vanilla linux driver doesn't seem to be effective. So far, Fedora 12 continues to be a big FAIL! as far as this particular machine goes.
View 4 Replies
View Related
Dec 15, 2010
So I didn't notice when I setup my CentOS 5.5 server that I left / as RAID 0 on md1. All the rest are RAID 1. Is there a way I can modify the array to RAID 1 without a risk of data loss? I'm glad I caught this before I setup any other services. I've only setup smb so far...
[root@ftpserver ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 16G 3.0G 13G 20% /
[code]....
View 1 Replies
View Related
Jun 4, 2010
I've been all afternoon trying to install Ubuntu Lucid on my fakeRAID 0 configured (2) HDDs and am unable to set GRUB up. The fake RAID setup is provided by Intel Matrix Storage Manager, it is correctly enabled and the BIOS is also correctly set up -- in fact, I've managed to install Windows 7 with no significant hitch. After struggling with partioning the drives (had to follow advice I found on a very helpful guide online [0]), creating the filesystems AND getting Ubuntu's installer to actually do what it is supposed to do, I now cannot seem to set GRUB up. My system, as it stands, is unbootable at all; via live CD only.
This is how the RAID0 dev is partitioned:
Code:
# fdisk -l /dev/mapper/isw_ecdeiihbfi_Volume0
Disk /dev/mapper/isw_ecdeiihbfi_Volume0: 1000.2 GB, 1000210694144 bytes
255 heads, 63 sectors/track, 121602 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disk identifier: 0x6634b2b5 .....
View 2 Replies
View Related
Jul 8, 2010
I'm attempting to install F13 on a server that has a 2-disk RAID setup in the BIOS. When I get to the screen where I select what drive to install on, there are no drives listed. The hard drives were completely formatted before starting the 13 installation. Do I need to put something on them before Fedora will install?
View 3 Replies
View Related
Apr 15, 2009
I have been battering with FC10 and software RAID for a while now, and hopefully I will have a full working system soon. Basically, I tried using the F10 live CD to setup Software RAID 1 between 1 hard drives for redundancy (I know its not hardware raid but budget is tight) with the following table;
[Code]....
I set these up by using the RAID button on the partition section of the install except swap, which I set-up using the New partition button, created 1 swap partition on each hard drive that didn't take part in RAID. Almost every time I tried to do this install, it halted due to an error with one of the raid partitions and exited the installer. I actually managed it once, in about...ooo 10-15 times of trying but I broke it. After getting very frustrated I decided to build it using just 3 partitions
[Code]....
I left the rest un-touched. This worked fine after completing the install and setting up grub, reboot in to the install. I then installed gparted and cut the drive up further to finish my table on both hard drives. I then used mdadm --create...etc to create my RAID partitions. So I now have
[Code]....
View 2 Replies
View Related
Sep 19, 2010
I just went out and bought stuff to build a new computer, and among the parts was a Gigabyte ga-890fxa-ud5 motherboard ([URL]). The board has 3 (well, 4, but we'll stick to the 3) main sata interfaces, with 2 slots per interface, allowing 6 sata drives. In slot_0 i put my blu-ray drive, in slot_1 i put my drive that will host the OS and its partitions, and that is in the sata connector pair on the left. The middle sata connector pair (slot_2 and slot_3) i have 2 2tb drives, and in the sata connector pair on the right (slot_4 and slot_5) i have 2 1.5tb drives.
[Code]....
View 14 Replies
View Related
Jun 23, 2011
I'm looking to set up a server with attached mass storage device and tape autoloader to run linux. It's set up under Windows at the moment. Goal is to have users, connecting from individual workstations and laptops, backup their data to the linux server. On their personal machine, some users run linux, some MacOS, some Windows. I plan to set up the 5 500 GB drives as RAID5. I understand that if setting up as software raid the format is "physical volume for RAID". Under this setup, will Windows users be able to read/write and function as expected? I can't assume only linux user access.
View 3 Replies
View Related
Feb 22, 2011
I was minding my own business watching loombo and just like that the sound cut out. so I was like okay I will watch it on mega video and no such look no sound there too so I checked my ..... and that wont even load videos.so !I'm running the latest version of ubuntu on my dell insperon laptop if this helps
View 3 Replies
View Related
Jan 26, 2011
Running Ubuntu 10.10 and I'm getting annoyed by the password authentication each time I want to do something. I find this more annoying than Windows 7 and UAC
View 9 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
