Search the Community
Showing results for tags 'restore'.
Found 3 results
Hi, I lately ran into a problem with some Lacie 2Big Network v2 NAS units and had to restore the firmware onto the disks - for those who dont know - these damn units have the firmware on the actual disks and not in a ROM (ARGHHHH!!!!) - and speaking with Lacies support is jumping out an airplane and hoping it wont hurt.. it will.. trust me. Anyway, after some (alot) of Googling i found the solution, but it was bits here and there and nothing that really got the job done fully - so... hopefully this post will help out people. First of all.. some reference points: - http://lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2)(the big one, but not the entire solution) Cache copy: https://web.archive.org/web/20180210210928/http://lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2) YOU NEED TO READ THE ABOVE LINK BEFORE GOING ON Requirements: a. A 2Big Network v2 NAS (other models might be supported as well) b. A machine running Ubuntu (or some other debian based linux) c. 2x Disks of the same brand/model/size ... others might work as well d. You have downloaded all of the files attached to this post. How-to: 1) Start by connecting the first disk via USB to your Linux machine and run "fdisk -l" to find out the device path .. in my case its /dev/sdd 2) Init the disk by running: gzip -dc //mbr+label.gz | dd of=/dev/sdd (Take a moment to understand what we are doing there) 3) Now we need to fire up fdisk to recreate the partition scheme (Run: fdisk /dev/sdd) - mine looks like this: Device Boot Start End Sectors Size Id Type /dev/sdd1 63 4016249 4016187 1.9G 5 Extended /dev/sdd2 4018176 1953525167 1949506992 929.6G fd Linux raid autodetect /dev/sdd5 126 514079 513954 251M fd Linux raid autodetect /dev/sdd6 518144 620543 102400 10M 83 Linux /dev/sdd7 622592 724991 102400 10M fd Linux raid autodetect /dev/sdd8 727040 2365439 1638400 500M fd Linux raid autodetect /dev/sdd9 2367488 4005887 1638400 1200M fd Linux raid autodetect After you have created the above config, its time to run some commands on the disk. This is how it looks like (get a copy in step2.sh): (IMPORTANT: If your disk is called anything else than /dev/sdd you have to change that in the below lines) echo -------- preparing raid arrays -------- echo -- Fixing /dev/sdd5 - swap mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdd5 missing --metadata=0.90 mkswap -f /dev/md0 mdadm --stop /dev/md0 echo -- Fixing /dev/sdd7 - initfs mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdd7 missing --metadata=0.90 mke2fs -j /dev/md0 mkdir /tmp/md0 mount /dev/md0 /tmp/md0 cd /tmp/md0 tar xzf /home/lsb/Desktop/lacie/sda7.tgz cd .. umount /tmp/md0 mdadm --stop /dev/md0 echo -- fixing /dev/sdd8 - ro layer rootfs mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdd8 missing --metadata=0.90 mke2fs -j /dev/md0 mount /dev/md0 /tmp/md0 cd /tmp/md0 tar xzf /home/lsb/Desktop/lacie/sda8.tgz cd .. umount /tmp/md0 mdadm --stop /dev/md0 echo -- Fixing /dev/sdd9 - rw layer rootfs mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdd9 missing --metadata=0.90 mke2fs -j /dev/md0 mdadm --stop /dev/md0 echo -- Fixing /dev/sdd2 - data partition mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdd2 missing --metadata=0.90 mkfs.xfs -f /dev/md0 mdadm --stop /dev/md0 echo -- Fixing /dev/sdd6 - kernel gzip -cd /home/lsb/Desktop/lacie/sda6.gz | dd of=/dev/sdd6 ... now repeat the above on disk2, pop in the disks, start your NAS and you sound see it come online again. Hope it helps somebody out there from alot of headaches. Files: - http://files.osxlatitude.com/leon/Lacie/lacie1.zip
Hi, with the use of myHack I've created a Mavericks 10.9 installation (Hackintosh). Everything works great, only problem occurs when I try to make a System Restore ... can't get to Select destination step ... the problem is that I get everything else shown, except the thing I need ... My backup is on external HDD and process of creation a backup goes through without a problem ... the backup is normaly shown when I start the Restore process ... Thanks in advance ...
Hi, I recently had a few problems when 10.9.3 failed to install properly. I gave up trying to fix what I was left with and tried to restore from my myHack Installer USB drive. Although my backups were made on the same computer, it received the message "You can't restore this backup because it was created by a different model of Mac". Would I be right in thinking that this is a problem with my Installer? Because I didn't have a way of doing anything with my Installer, I installed 10.9 on my HDD, installed my kexts and decided to re-create my Installer. I gave it a test, made a new backup, and it didn't work. I then tried copying my smbios.plist over to the Installer and editing the org.chameleon.Boot.plist to use it. I ran myFix on the Installer and tried the restore again. No change. What is causing me to get the message and how can I fix it so that I can restore from backups. I don't really want to be updating things until I know my backups can actually be restored. Thanks