Ubuntu :: Software RAID Fails After Reboot (Ubuntu 9.10)?
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
ADVERTISEMENT
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
Aug 22, 2010
When I try to use Wubi to install Ubuntu it fails on reboot. It seems to run a script on reboot then nothing. I get a command prompt window with the script and the laptop seems to lock up. Only a hard re-boot will restart the system. I do get a dual screen boot prompt Windows/Umbutu but if I choose Umbutu, I get the same command prompt screen and the system is locked up again. Chosing Windows at the boot screen works fine.
View 3 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
Sep 8, 2010
I did a search and couldn't find anything pertaining to this - if I've missed something please direct me in the right direction We have an Ubuntu box set up as a headless office server (latest desktop install of Ubuntu) and we recently set up two 1TB HDDs in a RAID1 array using mdadm - as far as I can tell it worked successfully and created /dev/md0 with an ext3 file system. After sharing the drive I can see it from the other office computers and could transfer data to and from the RAID array just fine.
I didn't figure out how to get it to automatically mount on boot so I restarted it to see if it would do so by default - however, when I restarted I couldn't see the RAID array any longer on the desktop and it came up as a 0.0kb RAID array in Disk Utility, saying it was broken. It wouldn't let me check it until I stopped and restarted the array.
After restarting I hit "check array" and it appears to be repairing the drives. What have I missed? What happened here? How can I fix it? What other info can I provide to assist:
sudo blkid shows:
/dev/sda1: UUID: "<snip>" TYPE="ext3" (system HDD)
/dev/sda5: UUID: "<snip>" TYPE="swap"
/dev/sdc1: UUID: "<snip>" TYPE="linux_raid_member"
/dev/sdb1: UUID: "<snip>" TYPE="linux_raid_member"
/dev/md0: UUID: "<snip>" SEC_TYPE="ext2" TYPE="ext3"
disk utility: RAID Array: Mirror (RAID-1), Metadata version 0.90.0, Partitioning: Not Partitioned, Components: 2...
View 1 Replies
View Related
May 17, 2010
I'm installing 10.4 x64 on a Dell PowerEdge R610 RAID 1 and the install goes fine until I have to reboot the finish it. On reboot after about a minute it gives the error
Code:
Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline/
-check rootdelay= (did the system wait long enough?)
-check root= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/mysql1-root does not exist. Dropping to shell!
what to do and my co-worker who knows a little more about Linux can't get it to let him check any of the above common problems.
We're tried letting GRUB manually configure itself at the end og the install before we reboot and we've also pointed it to /dev/sba partition which is what should be the boot partition.
EDIT: in the code tag it's ALERT! /dev/mapper/mysql(one)-root.... the L and 1 look the same
View 9 Replies
View Related
May 18, 2010
I'm installing 10.4 x64 on a Dell PowerEdge R610 in a RAID 1 configuration and the install goes fine until I have to reboot the server to finish the install. On reboot after about a minute it gives the error.We've tried letting GRUB manually configure itself at the end of the install before we reboot and we've also pointed it to /dev/sba partition which is what should be the boot partition.In the code tag it's ALERT! /dev/mapper/mysql(one)-root.... the L and 1 look the same.I've got 3 of these server to get setup and running as part of our back end and network restructuring and have been stuck at this point on the first one since Friday.
View 9 Replies
View Related
Dec 30, 2010
I recently installed Ubuntu 10.04.1 LTS and have it set to dual-boot with windows 7 on my gateway tablet PC. Since installing, sometimes when I suspend or reboot, my wireless does not work. To be more clear - it is working fine, then I either suspend/reboot, then I come back and no wireless networks show up at all. I can still connect with ethernet cable though. I can solve it by rebooting multiple times (usually around 1-5 times) and then it (magically) seems to work again. I have also tried switching from network-manager to wicd, but the problem persists. With both network-manager and wicd, I've tried simulating a reboot for the wireless by using the command 'sudo modprobe -r iwl3945 && sudo modprobe iwl3945' (network-manager) and 'sudo /etc/init.d/wicd restart' (wicd), but these do not seem to work.
View 9 Replies
View Related
Mar 9, 2010
Just installed Ubuntu a month ago (installed within windows), and for the 2nd time it has gotten stuck in grub upon restart after doing an automatic update. Last time, I reinstalled from the CD, but I can't do that every time. Learning how to start up from grub would probably be worth learning so I don't have to use the CD. But fixing the problem is most important. It makes me wonder if it was a mistake to install Ubuntu from within Windows (does this mean I have "wubu"?). I did find a webpage on booting Ubuntu from grub, but I could not get the kernel to load, regardless of if I used the instructions for wubu or not.
View 3 Replies
View Related
Jun 15, 2010
I've installed Ubuntu 10.04 LTS (64-bit) server edition on a box here (a few times now), and each time I attempt to boot post-install, I get RAID errors. The box has 4 hard drives in it, and I've disabled the hardware RAID in BIOS because I couldn't seem to get that to work.During the installation, I opted to handle partitioning manually. One set of hard drives has two partitions: one for swap, and one for /. When all is said and done, I end up with three RAID 1 mirrors: one for swap (/dev/md0), one mounted at / (/dev/md1), and one mounted at /srv (/dev/md1).
View 3 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
Mar 19, 2010
reason my wireless is constantly failing. the only solution is a reboot but it will start to fail again. I use hp mini 210 ubuntu netbook remix.here is a log file
Mar 19 19:37:37 nicky-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 19 19:37:37 nicky-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (
[code]...
View 4 Replies
View Related
Feb 19, 2011
I can get connected to the Internet when I reboot the system, but the connection usually fails after within 10 mins. However, even then the network manager says it's connected. Never reconnect, manually or automatically.
View 2 Replies
View Related
Aug 18, 2011
I have successfully managed to connect a Razer Orochi bluetooth mouse with no issues. This also connects automatically when i start up the machine.
I also have a Logitech MX5000 keyboard that i can connect but it never survives the reboot. I have to manually connect it each time.
The only difference i can see between the two is the keyboard asks for a passkey whereas the mouse doesnt.
Ubuntu 11.04 32bit.
View 1 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
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
Feb 12, 2010
No matter which ubuntu version at 95% through the install it will complain that grub failed to install.
I'm installing this on an HP XW6600 with hardware raid striped.
I can use the supergrub rescue CD to boot to ubutu after, but whatever I do doesn't seem to get grub installed.
Any ideas on how to proceed? I'm guessing I need to install grub from scratch.
View 3 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 4, 2010
I am trying to upgrade from F11 to F12.Using Preupgrade, everything went well and then it asked me to Reboot. Anaconda started then says something about updating some files then the screen goes blank.
View 14 Replies
View Related
Jul 28, 2010
I am having a HARD, PARTIAL FAILURE OF SOUND on my Linux system (Slackware 13.1, the latest, with a 2.6.33.4-smp kernel and KDE 4.4.3). The failure is "HARD" in the sense that once it occurs it remains broken until I reboot the system. It's a "PARTIAL" failure in that it affects ONLY SOME sound software on my system. Here is a list of what fails and what doesn't. (I'm sure there are other programs I could use to test with, but I don't know what they are since I am "just an average user" when it comes to multimedia software.)
These don't fail:
Amarok
KDE event notification
These do fail:
Firefox
Xine
Mplayer
In the things that fail it is only the sound portion of whatever (flash, mp4, etc) which goes away; the video portion plays normally.n I leave my system up for days at a time. The failure occurs some "long-ish" time (days) after I reboot. I have no idea what triggers it. I do not use sound most of the time, but when I do it's music through Amarok (which doesn't fail) so I do not notice the failure when it occurs.
It seems clear to me that it is NOT the failed programs which are at fault but it is, rather, some underlying set of sound libraries and/or servers used in common by all the programs which fail, and that the failure occurs when something happens which affects that set of sound libraries and/or servers. I don't think this is specifically a Slackware issue since I've seen a few other problem reports on the web where the sound simply stops on non-Slackware Linux systems. Some of the problem reports I've seen suggest that playing sound from one program stops sound from other programs. I've tried various combinations of sound-producing programs but none have triggered the problem.
I've looked at /var/log/{messages,debug,syslog} and see nothing relevant. I've gotten process lists from ps before and after the failure and no "relevant" processes have gone away. (But note, as before, that I am NOT a Linux "multimedia guy" so I can only make intelligent guess at what is "relevant".) Does anyone know what this problem is and, better still, how to solve it? Or where I could look for additional clues? Is there some way to "reset" the sound system without having to reboot?
View 5 Replies
View Related
May 14, 2010
I can't seem to get past step 6 of he installation of Ubuntu 10.04. I get the error: The ext4 file system creation failed... on single partition (no raid). I chose ' / ' as the mount point, and have tried with and without a swap drive. I'm installing on a Sony VAIO VGN-NS160D, and the HDD was previously formatted to NTFS. There's no other OS so I don't see any way of getting a command line to try a sudo fdisk..
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
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
Jul 1, 2009
I am applying a virtual interface (eth0:0) which is failing after the system reboots. It actually cause the default interface (eth0) to fail as well, I must manually go in and remove the configuration for the eth:0:0 and restart the network to get it running again. How do I successfully add a Virtual interface to Fedora 11 that will stick when rebooted.
eth0: 192.168.0.200, 255.255.255.0, 192.168.0.1, BROADCAST: 192.168.99.255
eth0:0 192.168.0.98, 255.255.255.0, 192.168.0.1, BROADCAST: 192.168.99.255
View 1 Replies
View Related
Aug 3, 2010
I am trying to update my OS from Opensuse 11.2 to 11.3 using the installation DVD (checked OK). Everything is OK during the installation process until the message "System is going to reboot" is displayed with a countdown : when the countdown is finished, the screen becomes black and the screensaver starts, but the system does not reboot. When I reboot manually, after selecting "Opensuse 11.3 desktop" on the first menu, the screen becomes black and the screensaver starts.
So the installation seems incomplete and I do not know how to finalize it. When I select the failsafe option on the first menu, it seems to work but some behaviours are quite "strange"... When I choose update instead of installation at the beginning, the behaviour is the same.
I do not know if it is linked but the firmware tests started from the installation DVD show the following errors :
Memory tests are OK.
View 5 Replies
View Related
