Thanks Frank, But this is kind of my backup. I don't have any capacity to backup to another drive/ext HDD.
The OS is running off a small SSD. I have 2x3TB drives for data running in RAID1. I assumed with software raid, the drives couldn't be used without being part of the RAID config, i.e. presented via mdadm. I'm fairly new to Linux and software raid, so please forgive any stupid /obvious comments. Am I right in thinking, I could get new OS up and running. Mount one of the disks as a standard drives (not raid) and them somehow rebuild a raid based with the data present? What problems might I face using the raid config as is under 64bit dist? Thanks for your advice Sam On Sunday, January 27, 2013 3:50:01 PM UTC, Frank wrote: > On 01/27/2013 02:18 PM, Sam Martin wrote: > > > > > I'm about to reinstall linux using 64bit wheezy dist rather than the 32bit > > on i inadvertently used. > > > > > > I've got a copy of /etc but I'm concerned that in /etc/mdadm/mdadm.config > > there is no reference to the array. > > > > > > The only lines that are uncommented are > > > > > > CREATE owner=root group=disk mode=0660 auto=yes > > > HOMEHOST = <system> > > > MAILADDR root > > > > Why keeping a mdadm raid which incompatible binarys? Backup you data, > > install from scratch and restore your data, makes more sense to me. > > > > > Presuably is automatically detecting /dev/md0 (the raid vol)? > > > > > > Can anyone offer any opinion/advice on this? i don't want to be in a > > position where i cannot get it back up. > > > > Make sure you have a working and up2date backup, a print out of your > > /etc/fstab and the contents from "cat /prod/mdstat" can be helpful as > > well if something goes wrong. > > > > > The raid is a simple mirror at the moment, but I'm guessing I cannot use it > > without mdadm if it did go wrong? > > > > Of course, you can boot from both disks. Just change the device name in > > your bootloader from /dev/mdX to i.e the first detected SCSI / SATA disk > > /dev/sdaX. So if you screw up one of them, boot from the other device > > and resync your data. > > > > Best > > Frank > > > > > > -- > > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > Archive: http://lists.debian.org/51054a4e.8010...@dead-link.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/11073324-3e63-481d-8dce-b3f31c5fe...@googlegroups.com
