If you want a full run down as to WHY I want to do this, read here: webhostingtalk.com/showthread.php?t=899909Basically, my ISP could not get my server running stable on a simple raid 1 (or raid 5) so what it came down to was having them install my system on a single disk. I don't exactly like this, main reason being, if the system (or HDD) crashes, I'll end up with another several hours of down time..
View 1 Repliesmy Fedora 11 system is not starting anylonger. It stops with the message:
Code:
VFS: Can't find ext4 filesystem on dev dm-0
The system told me since a while, that a lot of the sectors of one disk of the (software) RAID compound are failed already. So tried to disconnect each of the disks and start them separately. Unfortunaltly this is not working (for one its is not working at all, the other wents the same far as with both), when I tried to recover the system with the Fedora DVD, it said no distribution found. I am quite new and do not know so much about linux system, so i do not know what further information you could need. Maybe it can be important, that both disks are encryped (the system wents so far, that I can type in the password).
Can RAID be implemented on a single hard disk ? If yes, plz give a link for it.
View 2 Replies View RelatedI had done a new lucid install to a 1 TB RAID 1 array using the alternate CD a few weeks back. I messed up that system trying to some hardware working that lucid doesn't have drivers for yet, so I gave up on it and reinstalled to a single 80 GB disk that I now want to move over to the RAID array.
I moved all of the existing files on the array to a single folder, then copied all of the folders from the 80 GB disk over to the array with permissions and symlinks (minus the contents of /proc and /sys, which I created empty).
These are the commands I used:
Quote:
p -a -d -R -v -t /media/raid_array /b*
cp -a -d -R -v -t /media/raid_array /d*
cp -a -d -R -v -t /media/raid_array /e*
cp -a -d -R -v -t /media/raid_array /h*
[Code]....
I tried to change fstab to use the 689a... for root, but when I try to boot, it's still trying to open /dev/disk/by-uuid/412d...
So then I booted from the single disk again and chrooted into the array, then ran update-initramfs -u. I got 3 "grep: /proc/modules: No such file or directory" errors, and "cat: /proc/cmdline: No such file or directory"- so I created directory /proc/modules, created an empty file /proc/cmdline, and ran the initramfs update again. Then I tried to shut down, which hung (probably because I was doing all of this from a terminal window in Gnome), so I killed the power after a couple of minutes.
It's still trying to use /dev/disk/by-uuid/412d... to boot.
What am I missing? I assume I just have to change the UUID to mount as root, but I don't know how.
Recently, one the SMART utility said that one of the drives had failed and another drive was about to fail. I downed the box and hooked them up to my windows machine to run sea tools on them (They are all seagate drives). Sea Tools said that the drives were fine, while ubuntu said they were failing/dead. Yesterday I decided to try to fix one of the drives in the raid. I turned the server off, took the failed drive out, and restarted. Of course the raid didn't work because only 2 of the 3 drives were there, however it had been working w/ only 2 of the 3 drives for a couple months now (I'm a lazy college student). I turned it back off and back on with the drive there just to see if I could get the raid up again, but I havn't been able to get it to go. So far I've tried:
Code:
mdadm --assemble /dev/md0 /dev/sd[b,c,d]
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
[code]....
I'm looking for a way to trick the raid into working with just 2 drives until I can warranty the seagate and buy an external 1.5 TB drive to use as another backup. how to remove the bad drive from the array and replace it with a fresh drive, without data loss.
Currently, my disk layout is as follows:
Code:
/boot /dev/sda1
/ /dev/sda5
windows /dev/sda3
/home /dev/sda4
/dev/sda2 is currently an extended partition.
I purchased a small SSD, and I'd like to move most of the root partition and my home directory over to it. Assuming the new drive is /dev/sdb, my desired layout is this:
Code:
/boot /dev/sda1
windows /dev/sda3
/data /dev/sda4
[code].....
What's the best way to go about this with minimal downtime? Second, what configuration files would I need to update?
I need to copy data from a single HD, which used to be part of a Linux RAID 1. I've googled around, but can't find any clue how to mount partitions from this single HD.
Background: The HD comes from a linux based NAS box Synology DS207+. The NAS uses ext3 as filesystem. Both NAS disks are fine, but the other NAS hardware is dead and not worth repairing or replacing.
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 RelatedI tried installing Ubuntu 10.04 WS on my PC but it did not see any disks to install on. I believe this is because my drives are all configured as RAID. My mobo is an Asus M3A78-EMH HDMI AM2+ socket with an Athlon 2X 5000+ CPU. The chipset is AMD 780G. I have the BIOS configured for RAID drives and I already run Win XP x32 and Win 7 x64 on it. My boot drive is configured as 'RAID READY' and I have 2 RAID 1 disks consisting of pairs of SATA drives.
From what I have researched it seems that with some tuning it should be possible to install Ubuntu 10.04 but I have little Linux experience and don't want to mess up my existing drives. I have installed Linux before a few times and run it but never with RAID. Is anyone aware of an existing disk image that I will be able to install from on my system or would it be possible for someone to create one for me to use?
I had used DELL 1950 with 300 GB raid disk. Now, I purchased Dell 2950 with 450 GB (6 disk - 3 pairs of raid). I wanted to pull out old 300 GB from 1950 and put it in 2950 (temporarily) to copy all contents to the new system. How do I know which HDDs I need to pull out from 2950 so that I can replace them with 300 GB HDD to mount. I do not know how raid setup (I know unix alone - not raid commands). Is this possible? How to do it?
View 5 Replies View RelatedI'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)
We have a server with RAID 0 with 4 hard disks on it each 250 GB. Linux kernel must find one hard disk named: /dev/sda with 1TB capacity. right? And also we have 2 partitions on sda: sda1 and sda2. We want to add another partition but we don't have enough space.
Now the problem:
If we add another hard disk and run
Code:
fdisk -l
Will the /dev/sda space incremented automatically so we can add new partitions or we must do something?
I have run Ubuntu in the past and then switched to OpenSUSE several months ago and set up raid 0 on a 500gb hard drive and 700gb hard drive (I went with openSUSE because of the graphical raid setup.)
My whole partition setup looks like this:
500gb Hard Drive:
750gb Hard Drive:
md0 is the two 400gb partitions on each drive for a total of 800gb space on my /home partition ext4 filesystem ( 380gb space used ) md1 is 100gb ext4 / partition.
all raid 0
Now I was wondering if I downloaded the alternate install cd for ubuntu ( as OpenSUSE has crashed for the second time because of bad updates ( starts, but gets to terminal only ) ) would I be able to keep my raid 0 home partition and wipe the rest of the each drive and setting up Ubuntu keeping all of my files and settings intact, just to install my programs I need all while keeping my old settings ( such as firefox bookmarks, virtual box utilities etc. ) intact.
From what I know it's possible, but I don't know much about the Ubuntu Alternate install disk ( as I have been dealing with dependancy hell on OpenSUSE ) but in OpenSUSE it wont let me keep the old raid setup ( md0 ) Im guessing it is possible to set up the home directory on a different hard drive and then going back into the live cd, editing the fstab, and switching it to md0, if this is even possible, or would I need to configure the driver on that system before I did that Oh and I forgot to mention that I've only been running 64bit operating systems.
System Specs: AMD Dual core at 2.8ghz ( overclocked, stable, cpu ran at full bore for a day. only reaching 120f) Nvidia 9600 gso 368mb ram, 4gb ram at 800mhz
I had Ubuntu 10.04 on a machine with SilImage and 3Ware raid controllers (Fakeraid) working in it just fine. Built a new machine with 10.04 as well then moved the whole array across (Cable for cable etc. - NO changes). The new machine 'sees' the controller and 2 drives per card in Disk Utility - all looks good, BUT the array does not seem to work as an array. Obviously the drives are full.
View 7 Replies View RelatedRecently I was working on something on my windows partition (on the same HD as opensuse), and all the sudden windows stopped working and I got some bad sectors on my HD.
Now, my opensuse installation is on the same HD as windows, but I need to get rid of that HD soon because it's starting to get worse (and I think opensuse is randomly crashing because of it).
Is there any way to transfer my opensuse parititon/os to another hard drive?
I have a Linux installation that currently uses a 40GB hard disk. It is partitioned as follows:
Code:
The disk has recently started to make a lot of noise, so I'd like to replace it before I lose data.
I have a pair of identical 160GB blank hard disks that I would like to use as a software raid1 array (The existing 30-odd GB root partition would be resized to fill the new disks).
How I could get the data on to the new hardware without losing anything?
I'm having trouble with Ubuntu 10.10 and stable device names. When I installed Ubuntu, the root drive was the only one in the machine; it obviously got /dev/sda.
After the base installation, I installed three additional 2TB drives to make RAID-5 array. Ubuntu renamed the root drive to /dev/sdd. While annoying I lived with it.
After creating a single partition set to "Linux raid autodetect" on each drive, I created the RAID-5 array:
Code:
All was going well until a reboot. When rebooting Ubuntu decided to make the root drive /dev/sda this time and now mdadm --detail /dev/md0 reports:
Code:
How to fix the array and make the device names stable?
A while back I successfully set up a software raid (mdadm) install of ubuntu server on a cheap Compaq machine. I'm pretty sure it's running an nForce 430 chipset. Anyway, I put 3 2TB drives in it and set up two arrays: a small raid1 array for /boot and a raid5 array occupying the rest of the drives.
One point of note here is that the raid1 array never seemed to "take hold": the partition is empty, and the system has been booting entirely from the raid5 array. I'm not sure if this is relevant or not: just throwing it in there in case it is.
Anyway, I recently upgraded my desktop PC, and planned to hand down the Q6600 and DG33TL motherboard from it to the server. I did the hardware upgrade, but now the system will not boot. My question is: why.
Boot fails with the following error message:
"No bootable device -- insert boot disk and press any key"
This to me suggests that it's not even getting to the point of running grub2: the mobo itself just isn't finding anything it considers to be bootable.
I've tried all combinations I can think of of configuring the SATA support in the BIOS (modes include IDE, ACHI and RAID, all in combination with UEFI boot enabled and disabled). The system does detect the three drives: it lists them in the BIOS config screen.
I've booted from an ubuntu rescue USB drive and I'm able to see the drives and even assemble the array. I can mount the LVM partitions therein and do what I'd normally be able to do with them.
Everything *seems* fine: it just can't boot.
Grub2 is something of a mystery to me, so I'm not exactly sure what I need to do to get it booting again, if indeed it is a problem with grub.
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 RelatedI have the H8dmu Supermicro mother board with the MCP55 RAID. CentOS 5 is detecting the four hard drives separately. The operating system resides on a hard drive not defined as a part of the RAID. The RAID was setup as striped.The sata_nv driver is loaded.why the OS would not be seeing the raid as a single drive?
View 2 Replies View RelatedI have installed fedora 11, now i want to install touch driver for my dell 15 laptop. when i m moving cursur its moving but when i m clcking on touch pad to open anything its not opening, to open i have 2 select any file then i have to click touchpad keys.
View 2 Replies View RelatedI kept my movies on a 2 drive software raid1 mirror, but now I changed my mind about needing a raid and pulled one of the drives for another use. Can I convert the remaining raid drive back to a regular single drive and keep the data in place? Can I change the raid partition back to regular partition and be able to mount it?
View 6 Replies View RelatedWhat I'm doing is attempting to create a minimalized CentOS which only installs the base components.
I decided that I'd install everything I need, then I did a ..
rpm -qa > installed-packages
I think used this new file to move all the RPMs that were used during the installation from ~/CentOS/disk/CentOS/ to ~/CentOS/graveyard
[root@localhost CentOS]# cat installed-rpms-no-vers | while read file; do mv disk/CentOS/${file}* ~/CentOS/graveyard/ ;done
mv: cannot stat `disk/CentOS/iptables-ipv6*': No such file or directory
mv: cannot stat `disk/CentOS/nss-tools*': No such file or directory
[Code]....
If I have a windows installed in raid-0, then install virtualbox and install all my linux os,s to virtualbox will they be a raid-0 install without needing to install raid drivers?
View 1 Replies View RelatedI have xp/fc8 on an older ide drive and just installed a new sata 1T and planned to put fc10 on it but in the process I killed my fc8 installation. I told the installer that the other disks were off limits but it was somewhat confusing at the bootloader page. So, I suspect that I told it boot off the fc8 disk. If that is the case is there a way to restore the fc8 install by somehow rescuing the /boot partition on the fc8 disk?
View 14 Replies View RelatedI've setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.What I'm going to do now is:
1. Mount the new mirrored filesystem under /root1
2. use find | cpio to copy everything from the existing / to /root1
3. use grub to create a boot record on /root1
4. edit /root1/etc/fstab to point / to the new disk
5. reboot the system and keep my fingers crossed
Is this the way to go? Am I missing anything?
Especially /var because I am running a MYSQL server on this box. I want to know if there is a safe procedure to follow to move these partitions from the current sda2 and sda3 that they are now to sdb2 and sbd3 because this is a much bigger disk. I don't want to break MYSQL and I don't want to be down for a long period. I have heard of some people suggesting a sym link to a /newvar and /newuser on sdb but I have also read this will not work when moving to a different physical drive.
View 3 Replies View RelatedIve setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.
What Im going to do now is:
1.Mount the new mirrored filesystem under /root1
2.use find | cpio to copy everything from the existing / to /root1
3.use grub to create a boot record on /root1
4.edit /root1/etc/fstab to point / to the new disk
5. reboot the system and keep my fingers crossed
Is this the way to go? Am I missing anything?
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 RelatedHow would you go about moving one users home folder to a different partition, while maintaining other users home folder on the current one. Will simply running "usermod -dm /path/to/new/home username" on one of the users do the trick.
I want to run one of the users of an SSD, while the other runs of a bigger SATA disk.