PP E02 - won't boot with 2TB HDD

[rino]

Hello all:
I had my PP E02 with 250GB HDD running for past few months without any issues, however, I was running out of space, so I decided to upgrade my HDD to a 2TB.

I labelled the 2TB HDD exactly same as the 250GB HDD, and then connected both of them - mounted the 2TB manually and copied all the data from 250GB over to 2TB. Then I unplugged the 250GB HDD. Resetted the swapfile, so that it reads from the 2TB with the correct swapfile.

As I copied the files over, I ensured that the directory structure was exactly the same. So, aside from extra space, the PP E02 should not feel any difference configuration wise.

I mount my HDD from FSTAB & SWAP file is also loaded via FSTAB.

I am running Samba & miniDLNA on it. Both these services are set to run on startup.

When I rebooted the device, it wouldn't load up. So, I disconnected the 2TB drive, and then rebooted. After reboot was complete, I plugged the 2TB into the device, and within few seconds the drive comes up fine. I can access my files on Samba, and miniDLNA just fine, however, the device doesn't boot up with the 2TB drive connected. I have to connect the drive manually after the device boots up.

Any suggestions on why it doesn't boot with with the drive connected, and what can I do to remedy this situation?

BTW, the drive is ext3 formatted.

Thanks in advance for any replies and looking forward to a solution soon

[moonman]

how did you copy? you need to be root (i.e. sudo su) and copy preserving the symlinks (i.e cp -a)

[rino]

I was logged in as root, and copied using:
$this->bbcode_second_pass_code('', 'cp -ar /media/usb/* /media/2tb/')

[Geoff]

Are you using an MBR partition table? I don't suppose uboot is set up to use GPT.

[rino]

No, I am not using MBR (actually, I don't know what it is )

Is it because PP E02 doesn't like HDD larger than a certain size, and I am using 2TB HDD?

I am not using any automounts - I mount my HDD using FSTAB.

If it is due to MBR, then how do I set it up? I am a noob, so step by step instructions would be greatly appreciated. Also, I have lots of data on the HDD already ... will I have to wipe it, or can I still get MBR without impacting the data on the drive?

Also, my alARM is on a separate USB flash drive - the 2TB HDD is purely for data storage.

Could it be because of the sequence things are loaded/booted up, and my FSTAB is causing issues with the boot sequence? If so, how do I change the boot sequence, and what should be the optimal sequence for things to boot up?

Any insight or help would be greatly appreciated. Thanks.

[WarheadsSE]

Much more sense made now:
$this->bbcode_second_pass_quote('', 'l')so, my alARM is on a separate USB flash drive - the 2TB HDD is purely for data storage.

[rino]

$this->bbcode_second_pass_quote('', 'L')ooks like scan-order race condition.

[WarheadsSE]

It is actually out of your control

[rino]

So, the only solution is to boot the PP EO2 without the HDD attached, and then attach it after it boots up, like I have been doing?

[moonman]

If you haven't already plugged in the drive with rootfs into back bottom port, try that first. That one should get initialized first. There's another trick, you can use initrd and specify root partition by label. But it involves modifying uboot variable