Solaris 8 boot block

I have a Solaris 8 machine that was having a hard drive issue. I shut the system down and then it will not boot.
I booted off a CD and ran fsck /dev/rdsk/c0t0d0s0 and it came back with a superblock error and I typed yes to fix it. I then tried to boot again and it still would not boot.
I then tried to reinstall the boot block but that did not seem to help. # installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
Where is the boot block suppose to go? Does it always go on slice 0 of the boot drive or does it go where the root partition is located. The root partition is actually on slice 4 c0t0d0s4.
# df -k | grep dev
/dev/dsk/c0t0d0s4 8256660 3799018 4375076 47% /
I have been fighting this issue all day. I am almost to the point of restoring the whole system. Thanks in advance.

987258 wrote:
When I do a printenv boot-device I get boot device = disk:b. What does disk:b refer to? You system is set to boot from Slice #1 of whatever your system's hardware defaults to for the first disk location.
If you were seeing "disk:a" then it would refer to the zero slice of the drive (S0).
If you saw "disk:c" then it would boot from the third slice (S3).
Perhaps the following two old OBP reference manuals can be of help.
Save them as bookmarks in your browser.
OBP 3.x Command Reference Manual
http://docs.oracle.com/cd/E19253-01/806-1377-10/
OBP 4.x Command Reference Manual
http://docs.oracle.com/cd/E19253-01/816-1177-10/

Similar Messages

Solaris 8 boot problems

I'm new to Unix so please bear with me.
We had a Ultra 10 running solaris 8 and the motherboard went. So we bought a replacement on ebay. Exact same hardware. Swapped out the drives with our old drives and booted. The new system was set up to boot off disk1 and our boot was on disk0. So at the ok prompt I typed "boot disk0" and up came the system. I should have stopped there since I know very little about Unix but I wanted to make it so that when the system rebooted it didn't first fail with disk1 and need the user to type "boot disk0". So after a little googling I found the "setenv boot-device disk0" command. I ran this command and then a reset and started to get a "The file just loaded does not appear to be executable." error. I then followed the directions here to reload the boot block.
(http://72.14.209.104/search?q=cache:8Jkk36RiNOwJ:sunsolve.sun.com/search/document.do%3Fassetkey%3D1-25-16778+The+file+just+loaded+does+not+appear+to+be+executable&hl=en&ct=clnk&cd=8&gl=us)
When I got to the "# fsck -F ufs -y /dev/rdsk/c1t0d0s0" command it started clearing sectors that it said unfixable and now I think I really messed up the drive. After that command I can't find any files on the drive. How can I retrieve the data off the drive and restore the system?
Thanks
Jason

looks like your kernel path is corrupt. You will need to rebuild the os

Zfs boot block size and ufs boot block size

Hi,
In Solaris UFS file system , boot block resides in 1 to 15 sectors, and each sector is 512 bytes total makes 7680 bytes
bash-3.2# pwd
/usr/platform/SUNW,SPARC-Enterprise-T5220/lib/fs/ufs
bash-3.2# ls -ltr
total 16
-r--r--r-- 1 root sys 7680 Sep 21 2008 bootblk
for zfs file system the boot block size is
bash-3.2# pwd
/usr/platform/SUNW,SPARC-Enterprise-T5220/lib/fs/zfs
bash-3.2# ls -ltr
total 32
-r--r--r-- 1 root sys 15872 Jan 11 2013 bootblk
when we install zfs bootblk on disk using the install boot command ,how many sectors it will use to write the bootblk?
Thanks,
SriKanth Muvva

Thanks for your reply.
my query is when zfs boot block size is 16K, and on disk 1 to 15 sectors(here boot block going to be installed) make around 8K,
it mean in the 16K,it writes only 8K on the disk
if you don't mid will you please explain me in depth
I m referring the doc for UFS, page no 108 ,kernel bootstrap and initialization (its old and its for Solaris 8)
http://books.google.co.in/books?id=r_cecYD4AKkC&printsec=frontcover&source=gbs_ge_summary_r&cad=0#v=onepage&q&f=false
please help me to find a doc for kernel bootstrap and initialization for Solaris 10 with zfs and boot archive
Thanks in advance .
Srikanth

Bad sector in Boot block

Solaris 8 on a sparcstation 20 to an external disk drive bay
This system was installed and working. I needed to do a fresh install and I started having problems. The install appearrs to work fine. It get s to the point of reboot. Then it fails to come up with an error or Can't find boot sector in boot block.
Any ideas what might be going on? Or what I might do to get this fixed and get my system installed and running again?
I have verified that the disk is fine and has no hardware problems. This has been installed 2 times before and I never saw this issue.

You can try either running a disk check through Windows and setting it to automatically fix errors (which will mark bad sectors) or you can try reformatting the iPod disk (a full format, not quick). A full format should also mark bad sectors. Once a sector is marked "bad" no data will be written to it.

Installed the latest Java update today on my older iMac and now it won't boot up at all. 2007 model worked fine this morning, now disk first aid say boot blocks f'ed.

I am using an older mid 2007 imac 24 inch running snow leopard 10.6.8
I normally accept software update recs, and today when installing the security update to java, all went fine till restart, when I got the universal "NO" sign, the circle with the line through it and just spinning gray bars underneath.
Booted from system disks, ran first aid, said the boot block partitions or something like that needed updating but disk appears to be ok. Still not working.
Do you think Alsoft Disk Warrior will fix? I am running off external back up drive now.
Thanks for any help or advice. Apple as usual is as useless as tits on a bull, or a screen door on a submarine, pick your simile...

If your backup's up to date it might be less hassle to erase the internal and clone back from the backup. Don't allow the update next time it appears - you're not the only one having problems it would seem.
Note; the message "updating boot partitions" is a standard message that appears after a repair run. It won't go away and should be ignored.
Provided the message "The volume Macintosh HD Seems to be OK" in green has appeared, your disc fle system is fine.
Message was edited by: noondaywitch

Invalid bs_jmpboot in boot block

Hi I'm riiiic a new mac user
After a year of discussion, my brother conviced me to but a MacBook Pro 13" and here I am
The notebook (hardaware) is beautiful, superb, marvellous but the software part makes me unhappy.
Hundred of people told me, forgot any error message using a mac, and here we are:
This is an errore message from disk utility:
Verifying volume “disk0s3”
** /dev/disk0s3
Invalid BS_jmpBoot in boot block: 616e67
Errore: this disk must be repaired
Verify e repair volume “disk0s3”
** /dev/disk0s3
Invalid BS_jmpBoot in boot block: 616e67
Disk utility is unable to repair the disk....
How did I get this error ?!?! Like thounsand of new MAC users I got this error trying install win7-64 bit on the boot camp partition.
I'll now describe my movements:
- 1. creationof a partition using boot camp
- 2. installation of WIN7 64bit
- 3. unable to detect the win partition on finder.
- 4. boot with pressed alt and selected to boot from windows, anything was great, windows work perfectly (with boot camp drivers) and I'm able to detect and read files from macHD.
- 5. trayed to find a solution and installed MACfuse e NTFS-3G (it didn't work)
- 6. opened disk utility and found that "disk0s3" was unmounted and un reperable, the same disk from who I can perfectly boot win7.
Does anyone know how to fix the unbelievable error?
Thank u
ric

I have exactly the same problem. Although I can boot into windows 7 bootcamp partition, I cannot mount this partition on the mac os X. Have you found any solution yet?

Could not read boot block (input/output errror) powerbook g4

Hello
My friend gave me a powerbook g4 and a copy of osx lion, I would like to install it but the internal hardive is not available within the "select Destination" area of the installation process. I tried to repair the disk which is labelled Disk0s1, but shortly after it is underway i recieve this message.
**/dev/disk0s1 could not read boot block (input/output error) Error: The underlying task reported failure on exit. 1 non HFS volume checked, 1 volume could not be repaired because of an error.
Within disk utilities the Disk01s is grey, I can try to repair it but the above error occurs. Do you know what the problem is and how I can fix it?

Since you are going to install system fresh, it sounds like, you should erase the drive. Boot from the installer disc, then select the language but do not start the installer. From the menu bar, you should have either an Applications or an Installer menu. From one of the menus, you can then start Disk Utility.
From the drives and volumes pane, select the internal drive hardware listing.
This will now allow you to partition or erase the disc. Now click the Erase tab and select Mac OS Extended (Journaled) as the format and then click the "Erase" button. You can name the volume that will actually be created, like for instance "MacintoshHD" or whatever you want.)
Once the erase has completed, you need to check the information for the hard drive at the bottom of the window. Be sure that the partition scheme is Apple Partition Map. If for some reason it is something else, like GUID, you won't be able to install MacOS on it. You will need to click the Partition tab, click the "Options..." button and select Apple Partition Map, then click the "Partition" button.
Once this is done, then you can quit Disk Utility and you should be able to install Tiger on that HD.

Can Solaris 10 boot from USB devices like USB thumb?

1. Any live CD build for Solaris 10? That's the one which can boot up from CD and run immediately.
No installation requirement.
2. Can Solaris 10 boot from USB devices like USB thumb?

You can find "live" CD and DVD images at OpenSolaris site: www.genunix.org/distributions/belenix_site. This OSolaris version is booted from CD/DVD drive and can be permanently installed on HD drive. Moreover You can find at this site suitable script for USB thumb preparation. However You should remember that the number of read/writes on USB thumb is limited (ca 400 and slightly more in more expensive versions).
Good luck.

Boot block recovery

Hello,
Well, this one isn't as desperate as my last post. Basically, I need to know where to go to get a boot block recovery cd. Is it downloadable from here? If so, where? Otherwise, how else do I get one? How do I get a backup disk in case this happens again?

hello
i can lead you to the correct download section if you could provide your model number for your BIOS update
Message Edited by samavedam_vijay on 04-04-2009 11:37 PM
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Solaris 8 Boot Problems, random messages [/etc/rcS: /etc/dfs/sharetab:]

Hello All,
I have all of a sudden developed issues with booting up one of my Solaris 8 [V240] Servers. Upon a routine reboot, I was faced with the following errors:
Feb 1 07:56:44 sco1-au-tci scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0):
Feb 1 07:56:44 sco1-au-tci Error for Command: read(10) Error Level: Retryable
Feb 1 07:56:44 sco1-au-tci scsi: Requested Block: 114007888 Error Block: 114007903
Feb 1 07:56:44 sco1-au-tci scsi: Vendor: SEAGATE Serial Number: 053532DN34
Feb 1 07:56:44 sco1-au-tci scsi: Sense Key: Media Error
Feb 1 07:56:44 sco1-au-tci scsi: ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xf
Feb 1 07:56:45 sco1-au-tci scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0):
Feb 1 07:56:45 sco1-au-tci Error for Command: read(10) Error Level: Fatal
Feb 1 07:56:45 sco1-au-tci scsi: Requested Block: 114007888 Error Block: 114007903
Feb 1 07:56:45 sco1-au-tci scsi: Vendor: SEAGATE Serial Number: 053532DN34
Feb 1 07:56:45 sco1-au-tci scsi: Sense Key: Media Error
Feb 1 07:56:45 sco1-au-tci scsi: ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xf
So I figured, Oh crap...the disk is messed up. However, on running a few scans, i.e. 'iostat -En' showed ALL errors to be '0'. In addition, I ran the format -> analyze -> read test which ran for about 10 or so hours and came back saying 0 errors found to be repaired. So it appears nothing particularly is wrong with my hardware. After the 2nd reboot, I didn't get the errors above anymore but now I can't seem to get past the single-user mode. I get the following errors.
mount: the state of /dev/dsk/c1t0d0s0 is not okay
and it was attempted to be mounted read/write
mount: Please run fsck and try again
/sbin/rcS: /etc/dfs/sharetab: cannot create
failed to open /etc/coreadm.confsyseventd: Unable to open daemon lock file '/etc/sysevent/syseventd_lock': 'Read-only file system'
INIT: Cannot create /var/adm/utmpx
INIT: failed write of utmpx entry:" "
INIT: failed write of utmpx entry:" "
INIT: SINGLE USER MODE
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
I have read a whole bunch of stuff as I found on google, like /var being full (it's not), the WWN being wrong as compared between vfstab, /dev, and /devices directory etc. I don't know what is wrong and I don't know what to do to fix this. Any ideas as to why this happened and what I can do?
PLEASE HELP!!!

Hi Darren,
thanks again for the response. Ok, so the question that I have right now is how do I fix my original issue pasted below:
mount: the state of /dev/dsk/c1t0d0s0 is not okay
and it was attempted to be mounted read/write
mount: Please run fsck and try again
/sbin/rcS: /etc/dfs/sharetab: cannot create
failed to open /etc/coreadm.confsyseventd: Unable to open daemon lock file '/etc/sysevent/syseventd_lock': 'Read-only file system'
INIT: Cannot create /var/adm/utmpx
INIT: failed write of utmpx entry:" "
INIT: failed write of utmpx entry:" "
INIT: SINGLE USER MODEWill running fsck fix this too? This is a critical machine and I need to bring it up during worktime in the eastern part of the world. This server has worked totally fine for over 180 days with the invalid filesystem and the inability to run fsck. Any ideas on how to fix the errors above?
Also
Yes. It needs to be at least the size of the filesystem, which you've reported to be 143349312 sectors. There's no easy way to shrink a UFS filesystem.Does this mean that that I have to re-create the partitions/layout of the disk and reinstall the OS and applications? Is there any way to re-layout without destroying the data?
Thanks
\R

Error 3 upon solaris 10 boot

Hi,
I installed solaris 10 (sol-10-u7-ga-x86) on an external USB drive of a pc. Upon boot I've got this error :
module /platform/archive/boot-archive
error 3 : bad or corrupt data while decompressing file
- press any key-
If I press any key 5 to 10 times it starts normaly.
Here the partitionning I made :
Part Tag Flag Cylinders Size Blocks
0 root wm 1309 - 2614 10.00GB (1306/0/0) 20980890
1 swap wu 3 - 1308 10.00GB (1306/0/0) 20980890
2 backup wm 0 - 30397 232.86GB (30398/0/0) 488343870
3 var wm 2615 - 5225 20.00GB (2611/0/0) 41945715
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 5226 - 27785 172.82GB (22560/0/0) 362426400 (/files)
6 unassigned wm 27786 - 29091 10.00GB (1306/0/0) 20980890
7 unassigned wm 29092 - 30397 10.00GB (1306/0/0) 20980890 (/export)
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 alternates wu 1 - 2 15.69MB (2/0/0) 32130
Do yoou know what's wrong ?
Thanks

What's confusing to me is that the second disk in this mirrored root pool shows c0t1d0s0 in one output and c0t1d0s8 is another output. I hope this is a typo. Otherwise, you need to find out why this device path changed. Its look like the primary disk is faulted. FMA will tell you if the disk is faulted and whether the second disk's device path changed. You will have to boot from media or an install server.
Thanks, Cindy

Solaris install/ boot problems please help

recently had to use solaris at work and liked it. So thought of getting it solaris 10 on intel box at home to learn it. I have never worked on a unix based OS before. When I installed the OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem i had to reinstall OS, installation went fine and but when i reboot i get this errror.
cannot find mis/krtld
boot error loading interpreter(misc/krtld)
elf32 read error
load error read of "platform/i86pc/kernel/unix failed.
boot path /pci@0,0/pci-ide@1f,1/ide0/cmdk@0,0:a
i have been trying to reinstall with many option like formatting with windows fdisk, linux installer everything as I saw somehwre that disk needs low level format.
I have googled but could not find any reason.
When I try to format disk using windows this is the information gatherd
Partition1 (solarisboot) 12 MB
partition2 unknown 152610
Hardware
pentium4 2.4 GHZ
1Gb DDR memor
Intel Original mother board.
140 Gb hard disk
Installation
install type 3 (tried all options)
entire disk for boot and solaris
accepted almost all parameters.
downloaded again , burned a DVD still same.
Any help will be highly apreciated, as I have been trying out everything I could find, also I really want to learn to use solaris

Looks like a boot disk problem.Try doing a lowlevel format with the respective tools.(Ex.If seagate harddisk download seatools) No try to install the OS.If you are facing the same problem try installing windows and see.The error looks like a bad blocks in the disk.

New to Solaris - dual boot question

I have been using OpenSolaris on my ThinkPad T400s, dual booting with Windows 7. I want to give Solaris 10 a try. I've had it running in Virtual Box under OS X for a while, and I think I'm comfortable enough to try it out on my ThinkPad. Here is my question: will the Solaris Interactive installer let me install Solaris 10 in my existing OpenSolaris partition? And if it does, will it modify the bootloader so that I can still dual boot with Windows 7? I dont want to have to destroy partitions and re-install Windows. Once its on my hard drive, I can add myself as a user, install the Intel 5300 wireless driver, etc... Anyone have any other issues with Solaris 10 on a T400s?

Okay, well as usually happens, when I resort to help I end up solving my own problem.
In this case however, I still don't have a good grasp of what is going on.
I deleted the partition table with sgdisk --zap-all /dev/sda and then used gdisk to recreate it, specifically setting the code for /dev/sda1 to ef00.
I then reformatted the FAT partition, leaving the other one alone. After mounting /dev/sda1 to /boot and reinstalling linux and grub, I ran:
grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=arch_grub --recheck
as described in the wiki, and
grub-mkconfig -o /boot/grub/grub.cfg
And it worked, including automatically detecting Windows on the other drive. Not sure what went wrong the first time but I'm glad to get it working.
Last edited by egan (2014-12-09 19:46:58)

Xp/solaris dual boot bug

Hello
I have a 80gb hard disk set up with win xp pro along
with a 25gb unformated partition. Recently I installed
solaris 10 x86 to the 25gb partition from sun's
website. the installation setup automatically selected
the 25 gb space. all seemed to be working fine. the
only problem was after installation solaris boot
manager selected solaris automatically if no selection
of win xp was made within 30 seconds. since i needed
xp pro as a default i used the utility OSBS (boot.exe
and osbs135). as instructed i have entered the saved
solaris.bin from mbr to xp root and have entered
corresponding entry in win.ini file. the new boot
manager enables xp selection by default, xp pro boots
all fine but if i select solaris nothing happens
except a blinking cursor.
It seems to me that solaris partition is all fine and
healthy as I added few packages from solaris
installation cd few days back. Only problem is i m
unable to boot from it with the OSBS boot manager.
Is this a known problem?? or is there any better boot
manager?
Any advice/suggestion will be highly appreciated.
Many thanks

Hi, I am not sure if this would work but it might. First of all do you know if you delete the solaris partition then wouldn't it go back to booting to Windows? Just wondering about that. Well anyways here is my proposed solution that enables booting Solaris from Windows XP boot menu. Actually wait do you have a floppy drive on your laptop or a portable one. Because this solution requires that. Reply if you have one.

Solaris 10 boot error 15 file not found

During a reboot to one of our solaris 10 servers when it reboots it comes up with this error message
Findroot (pool_rpool,0,a)
     Filesystem type is zfs, partition type 0xbf
kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS
loading '/platform/i86pc/multiboot -B $ZFS-BootFS' ....
Error 15: File not found
press any key to continue...
The grub file menu.lst content is as follows
#pragma ident   "@(#)menu.lst   1.2     10/06/11 SMI"
default 0
timeout 10
# Uncomment the following line to enable GRUB splashimage on console
splashimage /boot/grub/splash.xpm.gz
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Oracle Solaris 10 1/13 s10x_u11wos_24a X86
findroot (pool_rpool,0,a)
kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS
module /platform/i86pc/boot_archive
#---------------------END BOOTADM--------------------
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris failsafe
findroot (pool_rpool,0,a)
kernel /boot/multiboot -s
module /boot/amd64/x86.miniroot-safe
#---------------------END BOOTADM--------------------
During a shell session using a recovery disk i mount the rpool to /a , if I do a zpool status it comes back that rpool mirror-0 with both disks are online
rpool          ONLINE
mirror-0      ONLINE
c0t0d0s0      ONLINE
c0t1d0s0      ONLINE
However if I do a zpool import it shows
rpool          UNAVAIL     insufficient replicas
mirror-0     UNAVAIL     insufficient replicas
     c0t0d0s0 FAULTED   corrupted data
     c0t1d0s8 UNAVAIL    corrupted data
This is highly confusing
Any help would be much appreciated

What's confusing to me is that the second disk in this mirrored root pool shows c0t1d0s0 in one output and c0t1d0s8 is another output. I hope this is a typo. Otherwise, you need to find out why this device path changed. Its look like the primary disk is faulted. FMA will tell you if the disk is faulted and whether the second disk's device path changed. You will have to boot from media or an install server.
Thanks, Cindy

Solaris 8 boot block

Similar Messages

Maybe you are looking for