Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had a dual dell 600 running a small network attached storage for my home for about 6 months. I was using 2 western digital 250gbs in raid0. Last night I migrated the box to a new case, motherboard, cpu and ram. When I tried to boot I got an error saying that /dev/md0 had no superblock attached to it. My boot,swap, and root partitions are not on the raid device they are located on another drive /dev/hda. I am using suse 9.1, I should have used slackware. The computer has been pretty sluggish for use, but as a NAS, Web, & Ircd server its been pretty good. Im a slackware fan and im looking forward to playing with LFS pretty soon. So heres the deal:
After digging around I learned that on the old dell, the array consisited of two harddrives:
/dev/hdc
/dev/hdd
And on the new computer they are located at:
/dev/hdf
/dev/hdg
So I changed my raidtab and fstab files and rebooted still I got the same error. I did a mdstat and the status on the array was it was there but dirty.
Not thinking clearly at 3:30 in the morning I forced mdadm to create a new array!!!!!!!!!
I Belive I have screwed myself!?
Is there anyway to get this information back or recover it to another drive?
Per the LQ Rules, please do not bump your own thread until at least 24 hours have elapsed without a reply. Because the LQ membership is global, people in other time zones may not have seen this post yet, and thus it may take some time before a response is received.
Nope, you should have backed up. Its best to take the time backing up then trying to correct problems that may occur moving the RAID array. You are lucky that it was not a server for a company. You can try placing the RAID array back on the old system because changing from one controller to a new controller changes everything how the hard drives are formatted. You can try to find programs that will help you get the data back but make an image of your hard drive to test the program.
I do not know about you, but I will be very worry using RAID 0 for a NAS and Web server. This is because there is no prediction when one of the hard drives will fail. Anyway you should use RAID 1 for a Web server because two or more files can be read at the same time. Though RAID 1 will not help much for NAS, but you can use a combination of RAID 5, RAID 1, and LVM. This will give you speed in both reading and writing. Also it gives you unlimited storage with the use of LVM. Setting up RAID 5 through Linux's software RAID is ok if your system is a dual or quad processor. RAID 0 or RAID 5 should never be used to run Linux. Use another hard drive or use RAID 1 for Linux. You can also use RAID 10 (aka RAID 1+0, RAID 0+1, RAID 1-0, RAID 0-1), but it takes atleast four hard drives.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.