search

Drive-Trust-Alliance / sedutil

DTA sedutil Self encrypting drive software
610 stars 236 forks source link

RESCUE64-1.15 not (fully) booting on MacBook Pro Late 2008 (Apple Order No: MB470LL/A) #165

Open Baarten opened 7 years ago

Baarten commented 7 years ago

Dear developers,

it's great that you are giving this tool for free to the public!

Unfortunately I'm unable to boot the RESCUE image mentioned in the title. I'm following the steps in the Test the Rescue system wiki page. I'm able to get the image on a USB flash drive and boot from it, as I did following the Test the PBA wiki page. The PBA correctly identifies my Samsung 850 Pro (Model: MZ-7KE512), which I swapped with the original hard drive in my Mac.

With the RESCUE image I put it on the USB flash drive the same way. I use the 64bit one, because the 32bit one doesn't get recognised and seems the best choice for my Mac. The PBA I used was also 64bit. I'm able to see the USB in the boot menu and I'm able to select and try to boot it, but sometimes it keeps hanging on the boot menu indefinitely and other times it seems to do something. In the latter the screen turns black and then a (sometimes blinking) _ (underscore) appears. This continues for a minute or so and the system reboots.

Can you help me get the RESCUE to boot?

Thanks in advance

Note: I'm using Apple Order No in the title for Mac model identification, because Apple uses the model number of my Mac for multiple Mac models :\

r0m30 commented 7 years ago

Are you using the most recent versions of the rescue and PBA images? In V1.15 the only difference between them is the /etc/issue file and S99PBA.sh only exists in the PBA. If one boots the other should too. That's why I changed the rescue system to use buildroot. If you are I would suggest re-downloading and gunzipping the RESCUE64 image and trying again.

Baarten commented 7 years ago

I was (most likely) using V1.12 for the PBA as V1.15 wasn't out back when I was testing the PBA. I will test PBA V1.15 and RESCUE V1.12. See what works. If V1.12 works, is it safe to stay at that version?

r0m30 commented 7 years ago

You can use any version that works with your machine, but if you have issues the first thing I'm going to suggest is use the current version. The V1.15 PBA will run and not reboot if you use "debug" as the password so it is easier to see the test results. If you look at the new encrypting page you can see how this works. The pba code will run on the rescue system and the PBA images are included as well, allowing you to test AND install from the rescue image.

Baarten commented 7 years ago

Ah, I didn't see the new encrypting page. Looks handy!

I followed it, but I'm unable boot to V1.15 RESCUE64 still. Redowloaded it and specifically used gunzip to unpack it, instead of double clicking the file. BTW, I'm now doing this under Mac OS X. Used dd to put it on the USB this time. The RESCUE kinda boots, showing an underscore ("_") that flashed a few times and then stays. After one minute the system reboots. The V1.15 UEFI64 actually boots fine and I'm able to do the steps in Test the PBA.

I also tried the following: V1.12 Rescue: can't see it in boot menu. Is it 32 bit BIOS? I don't see different versions in exec repo for V1.12. V1.12 UEFI64 Release: It booted once. Entered debug for passphrase. Rebooted and refused to boot afterwards. Tried a couple of times. Also with a 20-30 second brake in between where the system was powered off. Kept hanging on Mac boot menu after selecting the USB to boot. V1.12 UEFI64 Debug: It doesn't have the opal statuses like in V1.15 PBA but boots fine. Also text is kinda scattered across the screen until the login prompt.

Didn't test the V1.12 LINUX PBAs, assuming those are 32 bit BIOS.

r0m30 commented 7 years ago

I'm going to focus on the v1.15 images. I can't understand why the RESCUE64 fails when the UEFI64 boots. They are the same except /etc/issue is different and the S99PBA.sh is removed from the RESCUE64.

When you try the RESCUE64 you don't see the bzImage loading and the root file system being unzipped? Again I can think of no reason for the difference. When you dd the image can you mount it and look at the file structure? It should be an ESP partition with /EFI/boot/bootx64.efi, bzImage, extlinux.cfg and rootfs.cpio.gz. Is that what you see?

Baarten commented 7 years ago

RESCUE64 gives me no indication of what it's doing. No text is shown on the screen. I will check if the dd'd USB has those files and if the partition is ESP.

Baarten commented 7 years ago

I see the following files in /EFI/boot: bootx64.efi bzImage ldlinux.e64 rootfs.cpio.xz syslinux.cfg Partition type is EFI.

Baarten commented 7 years ago

UEFI64 also has the same files as I mentioned. They're somewhat similar to what you mentioned. Any idea what went wrong? Am I supposed to see the files you mentioned or did you mention files of an other version or something? I also see you put V1.15.1 in de exec repo. I will give that a go.

Baarten commented 7 years ago

Same problem with V1.15.1 RESCUE64, although the non-blinking _ stayed longer on screen before reboot.

r0m30 commented 7 years ago

Are you booting in UEFI mode? The only way I get a failure like that is when I try to boot in CSM/legacy mode instead of UEFI mode.

ghost commented 6 years ago

I haven't found the reason for this but the V1.15.1 RESCUE64 seems to be booting correctly on my MacBook Pro (I have a mid 2012 model, 9,2) but I believe the screen actually stays blank.

I can login with root then type reboot, which reboots the system, so I'm assuming I'm at some sort of prompt.

I'm going through the files on the USB key to see if I can figure something out...

watsonbox commented 1 year ago

In case this helps anyone else encountering the same problem, I recently got the same on a 2012 Mac Mini.

It turns out these older Macs simply don't support UEFI, so it is in fact necessary to use the RESCUE32 image.