Sponsored Content
Operating Systems Solaris Upgraded BIOS - cannot see Solaris partition?? Post 303004391 by kebabbert on Sunday 1st of October 2017 07:01:20 AM
Old 10-01-2017
Quote:
Originally Posted by hicksd8
Perhaps this is relevant:

x86: Introducing GRUB 2 - Booting and Shutting Down Oracle Solaris 11.1 Systems

Does your new BIOS release notes say anything about which version(s) of GRUB it will work with?

---------- Post updated 28-09-17 at 10:24 AM ---------- Previous update was 27-09-17 at 06:56 PM ----------

I've just looked up your motherboard and found it supports a BIOS/UEFI combo. So the 'BIOS' you've upgraded to is probably using default settings. You should disable 'Secure Boot'.
Thanks for your help. Regarding Secure Boot, it seems my mobo does not support it:
http://www.supermicro.com/support/faqs/faq.cfm?faq=18134

Regarding GRUB, I dont even see the Solaris partition when pressing F11, where I normally choose which partition to boot from. So I can not even reach GRUB.

I booted into Win10 and looked at the disk via "disk manager", and wanted to see if I could mark the Solaris 11 partition as "active", but nope. I dont know what to do. Any suggestions?
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

re-partition disks on solaris

hi all, i was wondering if i have some volume manager and i want to format all partitions/disks and re-create new slices can i use regular format command or what? i think veritas volume manager is already installed. (2 Replies)
Discussion started by: Bashar
2 Replies

2. Solaris

Solaris 8 partition - compression

Hi, Anyone know if I have a mount point /data , can it turn on compression like what the MS Windows does ???? Thanks (2 Replies)
Discussion started by: civic2005
2 Replies

3. Solaris

How to access a solaris partition

Hi, I have the present scenario on a x86 machine. fdisk c0d0p0 Cylinders Partition Status Type Start End Length % 1 Active Solaris2 1 2500 2500 61 2 ... (14 Replies)
Discussion started by: vibhor_agarwali
14 Replies

4. UNIX for Advanced & Expert Users

How to merge solaris partition

I m using solaris 8. I have some free space on my hard disk. I want to merge that space into /export/home. Please tell me complete procedure for doing it. (7 Replies)
Discussion started by: mansoorulhaq
7 Replies

5. Solaris

Problem with Solaris Partition, I cant see it

Hi All, First post, I work as database developer (Oracle) My task is to setup a solaris system on a VMware installation which sits on a x86 server. I have installed the Os, applied patches (I think) and on VMWARE I added new hardware (Disk) which is where my database will be. The... (5 Replies)
Discussion started by: platforminc
5 Replies

6. Solaris

Disabling Solaris 10 active partition

I have a dual boot system with windows xp and solaris 10 running. Solaris 10 is currently in the primary active partision. If it's possible, how do I make the windows partision the primary active one rather than solaris 10? (1 Reply)
Discussion started by: shakarho
1 Replies

7. Solaris

Solaris Filesystem - rename the partition

Hi all i got this filesystem Filesystem size used avail capacity Mounted on /dev/dsk/c0t600A0B80001F350A000033404A5D29D9d0s2 492G 64M 487G 1% /u10 How do i change the name for /dev/dsk/c0t600A0B80001F350A000033404A5D29D9d0s2 to the... (3 Replies)
Discussion started by: SmartAntz
3 Replies

8. Solaris

Dual Booting - Solaris image CD doesn't read in BIOS

I am trying to install solaris 10-x86 as second OS on top of Windows XP. I have downloaded iso image from Oracle website and burned into bootable cd. when I loaded into CD-drive and made changes in BIOS to boot from CD. Its not reading from CD drive. After restarting the system with CD(solaris... (8 Replies)
Discussion started by: SunSolars_admin
8 Replies

9. Solaris

Partition overlaps another partition while creating new parition in solaris

hi all while formatting hard disk i am getting following error. Partition 1 ends at 266338338 It must be between 34 and 143374704. label error: EFI Labels do not support overlapping partitions Partition 8 overlaps partition 1. Warning: error writing EFI. Label failed. I have formatted the... (2 Replies)
Discussion started by: nikhil kasar
2 Replies

10. What is on Your Mind?

Tapatalk Upgraded

Hello, FYI, I upgraded our Tapatalk Version to version 4.8.1 today (from version 4.3.2). All seem to be OK but we never know! Please post in this thread if you see any problems after the upgrade. Thanks! (1 Reply)
Discussion started by: Neo
1 Replies
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD
All times are GMT -4. The time now is 08:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy