Slycat,
Are you still using the setup as described below?
I am trying to do something similar with my PPPro and running into some issues when I reboot and wanted to see if I have set up the same as you. I am trying to figure out what varies about my setup.
Are you booting your PPPro from NAND into ALARM?
Is your rootfs sda1 attached via the SATA connection?
Is the 3TB drive formatted as GPT only or is it hybrid MBR/GPT?
Do you know if the 3TB drive is 4096 physical sectors or 512?
I have searched many of the other threads in this subforum and several threads in the V2 forum regarding the 3TB disks and it seems like the 3TB drive almost certainly requires hybrid MBR but your post seems to indicate that it may not be necessary if booting from NAND.
thanks.
$this->bbcode_second_pass_quote('slycat', 'W')ell, it was too late to study and I was a little anxious with the harddrive in the enclosure that I decided to get it done.
Cracked open the PPPro, cut a slot for the cable, cut a rib to reduce strain, connected the sata-esata cable, and put it all back together. I then used parted to create
5gb root folder
4gb swap partition
Rest for storage partition
I then extracted my latest backup onto the 5gb root partition, connected to sata and powered on.
...And I am stuck at the blinking LED
I am not sure if it is trying to mount one of the other partitions first? Or if I should revert to stock firmware and reinstall ALArm with the oxnas script. The LED blinks at a random rate (first steady, then start to hold for a second, then blinks, then so on).
Any thoughts?
EDIT: Picky son of a b.... Re-did parted exactly as before (gpt, 0tb 3tb, print, etc.), made the partitions (ROOT=ext3!), extracted my backup.gz IN ROOT and not sudo, and presto. False alarm. (hehe, get it?)
Backing up my media now. Hoorah, sata!