Search the Community
Showing results for tags 'crash'.
Found 4 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
Hello, I have changed the fan of my D630. Everything went fine but now when I start the machine, it is booting alright but doing a hard shutdown after approximately 15 minutes of use if I start the system (Maverick) and 5 minutes if I just enter the bios. I used K5-PRO thermo pasta on the cpu and on one bridge (south one I think), and after checking again I could see that the pasta is well spread around the cpu but not so well around south bridge. I have followed the right procedure to fix the heat sink (1-2-3-4). Still it is crashing. Might it be related to the fact that I replaced the pad on the south bridge with thermo pasta? If yes, could someone tell me which pad should I buy to replaced it? Thanks
Unless I disable my 2 NVIDIA 8800 GTX cards with the nv_disable=1 option to Clover 3203, my Yosemite 10.10.3 system immediately crashes and reboots after Clover. I am using DVI output. I installed Yosemite 10.10.3 clean on a Gigabyte GA-Z87X-HD3 mobo and a i7-4771 CPU. To run, my kernel options are "-v nv_disable=1 kext-dev-mode=1 slide=0 " It crashes regardless of setting nv_drv=1. I can run this hackintosh with the i7's built-in gfx. I tried installing WebDriver-346.01.02f04, but that did not help. I have not messed around with other KEXTS, clover's config.plist, other config files, or DSDT/SSDT Injection. I have read through the nvidia guide at http://www.rampagedev.com/?page_id=276 but it is not up-to-date. What must I do to get NVIDIA gfx not to crash? Thanks!
Hello there, I own an ASUS N73SV laptop and have been trying to install Mac on it for a while. I found this website yesterday and eagerly started the installing procedure with myHack. Now, whenever I want to boot the installer, it goes like this; - laptop boots from USB - chameleon pops up, I enter -v (sometimes -x -f too, also tried GraphicsEnabler=No) - Mac (or chameleon?) starts loading all Kexts - screen clears, and new commandline screen pops up (the one with the bold, white letters) - everything goes well until it's done loading, the screen freezes at the commandline and stops responding until shutdown I've got Mac installers to succesfully boot with different distro's, and the USB installer I created is working perfectly on my PC, aside from not detecing my HDD's, but that's a problem I can solve myself. I thought it was the NVDA kexts that I had to remove, so I did, but still no luck. I'm going to try removing the AppleIntelHD kexts this evening/afternoon and see what it does. (with removing I mean I just take the kexts from the USB and move them to the trash, that's the way to do it right?) The compatibility page also shows this laptop as compatible (https://osxlatitude.com/index.php?/topic/2933-asus-n73sv/). I got practically the same hardware, the only real difference is my screen being full HD, and I have 6GB RAM instead of 4. I hope you guys can help me with this, I'm coming closer and closer to having no idea what I should do. I'm still searching on Google what could help, if I find something I'll post it here.