Jump to content

vasant910

Members
  • Content Count

    3
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vasant910

  • Rank
    Newbie
  • Birthday 11/10/1946

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If there is no simple solution or answer - can you please guide me to redo bootloader when I am in Sierra OS, so I can multiboot Sierra and Windows 10 on same disk (SSD 250GB). Thanks, Vasant
  2. I had following disk configurations. (see below) Disk 0 has Window 10 came with Dell desktop Computer (1TB hard drive) Disk 1 has Sierra 125 GB partition and Windows 10 124 GB partition (250GB SSD) Disk 2 has MacOS 200GB, data files 800 GB (1TB hard disk) When I reboot, I see multiple icons to boot from but order of boot-icons is MacOS, Sierra, Windows, Windows. So if I restart - it automatically boots macOS instead of Sierra - which is the one I am running all the time. Checked Clover shell command : "bcfg boot dump" amd see only 2 entries - disk1 and disk2 (nothing more) Question 1: I amnot expert in Clover - but all I want is to have Sierra as first wntry - so reboot will boot Sierra. Question 2 : Any easy way to use any other boot loader which I can use instead of Clover? Question 3 : When I click on Windows 10 icon in Clover - it only shows "white rectangle" and hangs. Need to power off to continue. If you know any easy procedure to redo Clover and have way to boot Sierra MacOS and Windows 10 (Multiboot) please let me know. Thanks, Vasant Clover EFI installer log - Tue Apr 30 10:59:13 CDT 2019 Installer version: v2.4k r4920 EFI bootloader ====================================================== /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *1.0 TB disk0 1: Windows_NTFS System Reserved 104.9 MB disk0s1 2: Windows_NTFS 503.7 GB disk0s2 3: 0x27 471.9 MB disk0s4 4: Windows_NTFS Media 495.9 GB disk0s5 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Sierra 124.9 GB disk1s2 3: Apple_Boot Recovery HD 650.0 MB disk1s3 4: Microsoft Basic Data 124.1 GB disk1s4 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_HFS MACOS 199.5 GB disk2s2 3: Apple_Boot Recovery HD 650.0 MB disk2s3 4: Microsoft Basic Data DATA 799.7 GB disk2s4 ====================================================== Backing up EFI files
  3. Won't boot without USB process - can't write MBR on disk Followed procedure documented to boot new MBR on disk drive so I can boot without USB. https://www.tonymacx86.com/threads/os-x-wont-start-without-uni-multibeast-usb-heres-the-solution.152329/ Check what it says under 'NAME' for your uni/multibeast usb (mine is called 'Multibeast') and write: cd /Volumes/Multibeast/usr/standalone/i386 fdisk -f boot0 -u -y /dev/rdisk0 dd if=boot1h of=/dev/rdisk0s1 After entering the last command you should get some feedback saying '2+0 records in, 2+0 records out', or something similar. Write: cp boot /Volumes/EFI/ Gives an error at fidsk command : sh-3.2# cd /Volumes/USB1112/usr/standalone/i386/ sh-3.2# fdisk -f boot0 -u -y /dev/rdisk1 fdisk: could not open MBR file boot0: No such file or directory sh-3.2# fdisk -e /dev/disk1 fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory Enter 'help' for information fdisk: 1> print Disk: /dev/disk1 geometry: 30401/255/63 [488397168 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: EE 1023 254 63 - 1023 254 63 [ 1 - 488397167] <Unknown ID> 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused fdisk: 1> exit Tried to write MBR documents as : fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory Enter 'help' for information fdisk: 1> show Invalid command 'show'. Try 'help'. fdisk: 1> flag 3 Partition 3 marked active. fdisk:*1> write Device could not be accessed exclusively. A reboot will be needed for changes to take effect. OK? [n] y Writing MBR at offset 0. fdisk: 1> exit BUT I still get same error " could not open MBR file boot0: No such file or directory Please help, Vasant
×
×
  • Create New...