Ubuntu Servers :: LVM - RAID Device Not Present On Restart
Jan 29, 2011
I've decided to toy around with LVM and mdadm this weekend. I can get everything working, and all is well, until I restart. After that, I no longer have any /dev/md0 device, which during the auto mount process, causes an error. I've looked through several HOWTOs, as well as the LVM/mdadm man pages, and I believe I've tracked it down to mdadm's "assemble" that is needed (so that LVM can see the md0 device).
Not exactly sure how to go about having this occur during the boot process to ensure that the LVM mapped drive is available for when fstab is read. In case it helps this is a base install of 10.10 server 64. I have four drives, the first is used for the OS and is not in the RAID array (nor LVM). The second and third are RAID1 (/dev/md0) and there is a volume group associated with /dev/md0. The last is a LVM, but not RAID, and it has its own volume group.
I have three WD 1.5 GB harddrives. 2 of them already in a linear RAID also called Concatenated i think. (the same as JBOD). Can i add the third drive to the RAID without losing data? Update "Using mdadm software raid."
I am finally, and happily ditching Windows IIS, SQL Server, and ASP in favor of LAMP. Not only will I save a bunch of money on operating systems but I've found php and MySQL development to be much faster than their Microsoft counterparts.Currently I have two W2008 and two Ubuntu servers running and doing virtually parallel tasks. I want to can the W2008 machines but I am not 100% sure of my Ubuntu mirrors.Everything seems to be working fine. I've copied tons of data back and forth as a primitive test but sometimes things work fine for all the wrong reasons. Here's where I get confused.
Question 1:Do I need to partition the RAID device (MD0) and then format it?From my experience this is necessary to get the device to mount.
Question 2:In this case was it also necessary to format the individual drive partitions?
Question 3:If I do a daily cat /proc/mdstat is this all I need to do to check the drive status.
Question 4:Is there any other check I can do to assure that the mirrors are created, mounted, and operating correctly?
I currently have 3 drives installed to be used as a file server. 1 holds the Ubuntu OS The other is the file server drive with 1 additional for backup using raid1.
2 Questions: 1) How do I get to the drive or Raid device to put files on the drive using command line (the 2 drives are sda & sdc that are connected to the raid1 device)?
2) How do I set the path in Samba to connect to this RAID drive.
I am trying to create a new mdadm RAID 5 device /dev/md0 across three disks where such an array previously existed, but whenever I do it never recovers properly and tells me that I have a faulty spare in my array. More-specific details below. I recently installed Ubuntu Server 10.10 on a new box with the intent of using it as a NAS sorta-thing. I have 3 HDDs (2 TB each) and was hoping to use most of the available disk space as a RAID5 mdadm device (which gives me a bit less than 4TB.)
I configured /dev/md0 during OS installation across three partitions on the three disks - /dev/sda5, /dev/sdb5 and /dev/sdc5, which are all identical sizes. The OS, swap partition etc. are all on /dev/sda. Everything worked fine, and I was able to format the device as ext4 and mount it. Good so far.
Then I thought I should simulate a failure before I started keeping important stuff on the RAID array - no point having RAID 5 if it doesn't provide some redundancy that I actually know how to use, right? So I unplugged one of my drives, booted up, and was able to mount the device in a degraded state; test data I had put on there was still fine. Great. My trouble began when I plugged the third drive back in and re-booted. I re-added the removed drive to /dev/md0 and recovery began; things would look something like this:
To test stability, I rebooted the system, but on reboot, the array wasn't assembled correctly. Basically it had one device in "md_d2000", as a spare. So I stopped that device with
I don't have any important data on the array yet ... so I zero'd the superblocks on all devices, deleted the partitions, and started over .. here I go again:
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]
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.
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'm currently setting up a dell server with hardware raid 1 on sas 6r. i got 4 sas installed on the server and configured to raid 1 as stated below, array 1: slot 0 & 1
array 2: slot 2 & 3
during the installation, the installer detect the array 2 as sda and array 1 as sdb.. so i proceed with installation on array 2. after completed the installation, the first reboot lead me to a 'grub-rescue" prompt. by following the guide at url Mode, i've noticed that the boot folder has changed to (hd1,1), which i believe it has changed to sdb1. default root device shows that prefix=(hd0,1)/grub.
I can't use my line-in/microphone jack. In system-management-sound input tab there is no input device listed, and the input controls are grayed-out. sudo lshw -C sound produced:
description: Audio device product: N10/ICH 7 Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b
Installed Centos 5 on IBM T60P laptop. Intel 82573L Gigabit ethernet controller. Keep getting this erro message, "e1000 device eth0 does not seem to be present, delaying initialization."
I have swapped out four known working, different bran network cards. Each one I get the same error as in the subject. If I boot to a Live CD such as CentOs 5.3 LiveCD both Nics are given an IP. This seems to only be happening with my CentOs 5.3 server install.I noticed the CentOS Live CD the Nics were reversed from eth0 to eth1 and eth1 to eth0.
At the moment as of the output of the commands, I am running two identical Nics, since the first one has always worked. I have previously used an rtl8139, 3com c3905-TX, onboard Rhine III based (now disabled) Here are steps I have done to try and figure this out:
Quote:
[root@centos ~]# lspci | grep -i eth 00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) 00:0e.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86)
Quote:
[root@centos ~]# cat /var/log/dmesg | grep -i eth eth0: VIA Rhine III at 0xee800000, 00:1b:11:bb:17:7d, IRQ 177. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
[code]....
I went through the system-config-network-tui. I copied /etc/sysconfig/network-scripts/ifcfg-eth1 to the ifcfg-eth0 and edited for sanity. and as stated earlier, have swapped out four different nics for eth0, and booted to two different LiveCD's. Both LiveCD's work fine.
I have installed Open SUSE in my DELL server which has 2 broadcom NIC cards, it showing both the NIC cards in Network configuration in YAST ,but it showing as not configured and not connected . Kernel device eth0,wlan0 are not present. In device manager also 2 Broadcom nic cards are detected.
i have problem related nici am using a dell inspiron 1545 laptop outputs are following---(1) [root@localhost ~]#lspci |grep -i ethernet 09:00.0 Ethernet Controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
(2) [root@localhost ~]#cat /etc/modprobe.conf alias scsi_hostadapter ahci alias scsi_hostadapter1 usb-storage
I'm running CentOS 5.2 on an ASUS M2NPV-VM motherboard. This motherboard includes an NVIDIA nForce 430 built-in Gigabit MAC (network interface). I've also installed a second PCI network interface card (NC100 Network Everywhere Fast Ethernet 10/100). The PCI-based card was configured as eth0, while the built-in NIC was configured as eth1. The machine is used as my firewall/router, so eth0 is my internal interface, while eth1 is my external interface. I've had some intermittent problems with the built-in (eth1) NIC. When booting the machine and it attempts to bring up the interface, I get the following message: forcedeth device eth1 does not seem to be present, delaying initialization From that time forward, there is no eth1, and so no external network, etc. If I try running /etc/sysconfig/network-scripts/ifup eth1 (from that directory), it results in the same error.
Originally, I was getting this error when installing the operating system on the machine. At that time, I was using a 75' ethernet cable (as I was working on the machine in my office, and the external ethernet jack was in another part of the house). As soon as I moved the machine to its permanent location (which is within 2 feet of the ethernet jack), the problem went away. However, I just updated the kernel (via yum) from 2.6.18-92.1.22.el5 to 2.6.18-128.1.6.el5, and now it fails 9 out of 10 times. I'm not even sure what I can do to debug this. I'm assuming there is some kind of timing problem with the initialization. Is there a configuration parameter I can set to allow more time for the initialization to do what it needs to do, to prevent this error?
I just attempted to install to a USB drive, and somehow in the process, GRUB overwrote my Windows 7 bootloader on the internal disk. My work laptop is now booting into a grub recovery whenever my USB key isn't present (with error: no such device and the uuid) - and hangs on a blinking cursor whenever the key is plugged in.I'm not familiar with what my options are for grub rescue, but ls shows (hd0) (hd0,msdos2) (hd0,msdos1) (fd0)
My laptop is encrypted, so I don't have much chance of recovery unless I can get back to the windows bootloader.
I have one hard disk for my root partition and a disk array on a separate mount point. I rebuilt my disk array, but I didn't delete my original mount points beforehand because I was hoping it would just "pick up". So now when I boot up, the OS tells me that the filesytem check fails because it can't find the array to map to the mount point. I know that I need to edit my /etc/fstab and remove the line that defines my mount point on the disk array. But it appears to be read only filesystem when I am in repair mode. I can't force the write with vi.
I have installed Linux SuSE 10.3 on a PC (Lenovo Thinkstation A58). However, when I start the computer I get the following error message:
"No valid Host_ID or host-name found."
I then use YaST to set up the network. I get the following error message:
"Unable to configure the network card because the kernel device is not present."
The computer has Windows 7 installed and everything seems to work fine. The LED on the Ethernetplug is blinking when using Windows, but not when using Linux. I guess this means that there is no driver for the Ethernet card (Marvell Yukon 88E8057). I have not found any driver for the card and am considering buying a new one. Which PCI card works with SuSE Linux 10.3?
It's been a real battle, but I am getting close.I won't go into all the details of the fight that I have had, but I've almost made it to the finish line. Here is the set up. ASUS Z8PE-D18 mother board 2 CPU, 8 Gig Ram. I recently added an OCZ Agility SSD, defined a raid 1 virtual disk on the 1 terabyte WD HDD drives, which will holds all of my user data, the SSD is for executables.The bios is set to AHCI. Windows 7 installed fine, recognizes the raid VD just fine.
I installed Ubuntu 10.04 by first booting into try and mode, then opening a terminal and issuing a "sudo dmraid -ay" command. Then performing the install. I told it to install the raid components, and told it to let me specify the partitions manually. When setting up the partitions, I told it to use the free space I set aside on the SSD from the Windows 7 install as ext4 and to mount root there. Ubuntu installed just fine, grub2 comes up just fine, and Windows 7 boots with out a hitch, recognizing the mirrored partition as I indicated previously. When I tell grub to boot linux however, it pauses and I get the "no block devices found" message. It will then boot, but it does not recognize the raid array. After Ubuntu starts up I can run "dmraid -ay" and it recognizes the raid array, but shows the two component disks of the raid array as well. It will not allow the component disks to be mounted, but they show up which is annoying. (I can live with that if I have to)
I have fixed a similar problem before by setting up a dmraid script in /etc/initramfs-tools/scripts/local-top ... following the instructions found at the bottom of this blog:[URL].. To recap: My problem is that after grub2 fires up Ubuntu 10.04.1 LTS (Lucid Lynx), it pauses, and I get "no block devices found" It then boots but does not recognize the raid array untill I manually run "dmraid -ay". I've hunted around for what to do but I have not found anything. It may be some timing issue or something, but I am so tired of beating my head against this wall.
Installed a TP-Link TG-3269 Gigabit card in a machine running OS 11.3 32 bit, when I go into Yast, Network Devices, Network to try configuring the card I get this errormsg: Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details. Couldn't find any mention of the card in dmesg's output, (though the 8139 onboard card is in there) there is some stuff about pci host bridge but I don't know whether they would be relevant or not
The chip on the card says it's rtl8169sc but lspci lists it as being 00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8369 (rev 10) Done some googling and there don't seem be any drivers for a Realtek 8639 and it returns no matches from a search on realtek's site, but there is a driver there for rtl8169sc chips, which I downloaded and installed, no errors when installing it Even after a reboot I still get the same error in Yast's Network Settings screen, lspci still lists it as 8369 and the device isn't listed at all if I run ifconfig
this explanation could take a paragraph or two. I have 7 hard drives in my system. One is a 250GB PATA I use for the Ubuntu install, 3 are 1.5TB SATA Seagates and the other 3 are 1TB SATA Seagates. I have had to replace 4 drives (one of them is the same drive twice) in order to get 6 that actually work well. That's a 40% failure rate. Most of the failed within a week or so of putting them in.
Through all of that I have learned a few things and now have them configured as follows. I have all six of them Raid5 with 1TB partitions. And then the 3 extra 500GB partitions I put as Raid 5 also. Seems weird, but it saves 1TB of space instead of having 3 1.5TB RAID5 and 3 1TB RAID5.I then use LVM to make it all one big 6TB drive. Yummy, lots of space.
Here's the problem I have had the last couple of times I restart the computer the 6X1TB RAID does not start up, or I should say it has all the drives as spares (the 3X500GB RAID starts fine). I have to use --force to get the raid to load, and all 6 load fine. I believe it says something about having to write something to two of the drives (I believe it is something about the superblock) to make them the same. I'm sorry I did not catch the message.Is that enough information for someone to tell me why it does this? It's done it twice now, when I reboot the computer.
This is my first time on a forum and the first time I tried to set up a web server.I am following a tutorial on how to set up a web server here: [URL]We get to a part were I have to install a firewall. The tutorial suggests shorewall. The command I am told to use is sudo aptitude install shorewall. However is returned is could not find package shorewall. I have searched the net and could not find anything on my issue. I then attempted to search aptitude but no luck. I found shorewall online but how do I download it without a GUI.
This is also my first time having an OS that is only command line. I have done other things from the command line only before. Things such as computer science homework on the computer science servers.For simplicity, how do you install software off the internet on to ubuntu server without creating a CD or using a flash drive
I have a raid 1 array which I did setup on a Centos box. I can configure the array fine the problem is every time is restart my machine I can no longer see the array and have to go create it all over again. I tried doing a few searches on it but have came up with nothing so far.
I made a software RAID 0. It works fine, but when I add it to fstab and reboot the server, I can't restart the server. Code: # cat /etc/fstab LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 LABEL=SWAP-sda5 swap swap defaults 0 0 /dev/md0 /vz ext3 defaults 0 0
When I go to rescue mode and delete /dev/md0 from fstab, I can restart, but I get this when I try to mount it again: Code: mount: you must specify the filesystem type
So I try to make it to a ext3 Code: # mkfs.ext3 /dev/md0 mke2fs 1.39 (29-May-2006) mkfs.ext3: Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table. #fdisk /dev/md0 Unable to read /dev/md0
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.
Just set up a home server with Ubuntu 10.10 desktop. I've set up a software RAID 1 device using System/Administration/Disk Utility which seems to work well. However when I reboot the machine and try and access the drive I get the error that 'authentication is required to start this raid device' and then I have to enter my password, after which all is good
My only issue that I can't figure out thus far is the remote. I'm using a Hauppauge Nova-T USB Stick, and generally the setup for the Nova-T 500 is good. No problem with lircd.conf, .lircrc etc. My problem is that the remote doesn't work on startup. Looked in /etc/lirc/hardware.conf and it says, as expected: REMOTE_DEVICE="/dev/lirc0"
Which doesn't work because I have no /dev/lirc0 (I do have a /dev/lircd). However, running /proc/bus/input/devices, I discover that my IR receiver is event5, so if I change the /etc/lirc/hardware.conf to: REMOTE_DEVICE="/dev/input/event5"
And restart lirc, it works fine. Unfortunately, upon restarting the PC, the IR receiver doesn't always have the same path - eg it could be event6 or event8 etc - so then I need to fix the /etc/lirc/hardware.conf again.
