ZFS boot record creating problem....

Hi
I m using zfs as a root file system and mirrored it an other disk using Solaris 10 on SPARC T3-1 machine and
when i m trying to write the boot record on zfs root mirror drive (2nd drive) by using this command:-
installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c0t1d0s0
but i m getting this message:
/usr/platform/uname -i/lib/fs/zfs/bootblk: File not found
any good suggestions??????????

Revised somewhat...
I copied and pasted your syntax and applied to one of my spare disks and it completed without error.
The error message is somewhat alarming if the /usr/platform/`uname -i`/lib/fs/zfs/bootblk file
is missing on your system.
On another Solaris 10 system, you might determine which pkg provides this file or whether a symlink
is missing.
# pkgchk -l -p /usr/platform/`uname -i`/lib/fs/zfs/bootblk
Thanks,
Cindy
Edited by: cindys on May 8, 2012 10:13 AM

Similar Messages

How do I install Lion on an MBP with Snow Leopard 10.6.8, Boot Camp'd XP and a Master Boot Record?

I think this is called "a pickle."
The machine is a 13" MacBook Pro, 2.66 GHz Core 2 Duo w/ 4 GB RAM and a 500 GB HDD.
The HDD has a Snow Leopard 10.6.8 partition, and a Windows XP partition, via Boot Camp. Its Partition Map Scheme, sadly, is a Master Boot Record. I need to reformat it to a GUID Partition Table scheme to install Lion, but when I attempt to boot it from the Snow Leopard 10.6.0 DVD to wipe the drive, it grey-screens. Dead end.
From what I can gather on the forums, I can't boot a 10.6.8 machine using a Snow Leopard 10.6.0 DVD. I can't find my grey DVDs for this machine – still looking for those – but I expect those won't work either, being Leopard-generation?
The machine works fine, for the most part, including the optical drive. Has occassional display and wake glitches. Its HDD is backed up on a Drobo via Time Machine. I also have a 15" MBP Core i7 (with the exact same problem: 10.6.8, XP, MBR) which I can use for Target Disk Mode via FireWire. If I try to wipe the HDD on the 13", using Disk Utility on the 15" via Target Disk Mode, will the 13" then boot successfully from the Snow Leopard 10.6.0 DVD?
I just want to wipe the 13" machine, reinstall a fresh copy of Snow Leopard, then update it to Lion and restore from Time Machine, and never touch anything Windows-related ever again. (And then do the same for my 15", for which I've found my 10.6.3 grey disc. Not sure if that's any more promising.)
Any help appreciated!

Sounds like something is wrong with your disk. Have you tried cleaning it?
The Snow Leopard 10.6.0 DVD is fine – it mounts on both my 13" and 15", and I successfully created an image of it on my 15". I also tried my wife's Snow Leopard 10.6.0 DVD, also clean, which produced the same grey screen result.
Have you tried to use boot camp to erase the Windows partition?
Yep, this is supposed to be the proper way to remove a Windows XP partition from Boot Camp, so this was the first thing I tried. I get the same error as everyone with a Master Boot Record scheme appears to get:
The startup disk cannot be partitioned or restored to a single partition.
Back up the disk and use Disk Utility to format it as a single Mac OS X Extended (Journaled) volume. Restore your information to the disk and try using Boot Camp Assistant again.
So, if I can't launch the Disk Utility from the Snow Leopard DVD, my next best guess is wiping it from my 15" over Target Disk Mode. However, if I try that, and still can't get it to boot from the Snow Leopard 10.6.0 DVD, then I'm stuck with an MBP without an OS.
My conclusion – that 10.6.0 DVDs can't boot to 10.6.8 machines – was based on forum posts about downgrading from Lion. I was wondering if there's a way to create a "10.6.8 restore DVD," and try booting from that. Shot in the dark perhaps.

ZFS boot partition?

Hi All,
I'm currently being asked to look creating a number of servers with mirroring. Ideally the whole server will use ZFS which would mean it would also need to boot from ZFS.
Looking at the OpenSolaris website:
http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/
It looks like it's possible to do this. My problem is that I need to use vanilla Solaris on SPARC, and some bits and pieces from those instructions don't work.
Is this even possible? If it's not, what's the best I can hope for?
I'm currently testing on x86 (in VMWare), I'll be deploying on SPARC.
Thanks for any help.....

Darren_Dunham wrote:
Boot procedures on x86 and SPARC are still quite different. So your testing on one doesn't necessarily help on the other. You'll note that the link you show is only for x86.
A new boot method for SPARC is being developed that will work with ZFS, but it hasn't been released the way the x86 side has. So you can't boot from ZFS on SPARC just yet.
DarrenI've also had issues with ZFS root in the X86 world. I won't go into the details as I'm not 100% certain whether it was the Nevada Build I was using (76) or if it was user error.
The current roadmap has ZFS boot for mainline Solaris as coming in either U5 or U6 according to a briefing we had recently. That puts it out anywhere from mid to very late 2008.
Dev Express will likely have it sooner, but we're back to "Is this production"? If it is, I would wait for it to be solid and stable and in main-line Solaris.
Cheers,

Cannot find boot record of WD Raptor on KT4

Hello forum, this is my first post.
I have been searching Google for a solution of my problem and found this forum. However, after searching this forum and reading quite a few threads I still could not find the solution. Here's my problem:
I have a brand new WD Raptor 74 GB connected to serial 1 as a single drive. The mainboard is KT4 Ultra BSR. I have built an array by pressing ctrl-f at bootup. The only option was stripe and I have set the array (array 1) as bootable. I went into BIOS and set the array as first in boot order. Conclusion, the BIOS seems to detect my array and so far so good.
I booted Win XP installation CD and pressed F6 to install the Promise drivers. I used the newest drivers which were downloaded from MSI yesterday. Installation detected my array so I created a new partition, formatted it and the installation program copied files to that partition. When copying was finished, the computer had to be restarted and it was supposed to boot from my harddrive where it copied the files. Now to the point of my problem: BIOS has detected my array and tried to boot, but it says that boot record could not be found! I don't know whether Windows installation has failed to create a boot record or BIOS could not detect the boot record.
I have checked the contents of C: by booting Win XP installation CD and gone into recovery mode. I would access C: and found the common files used for Windows bootup: boot.ini, ntldr, etc.
So the required files are in place, but either the boot record does not exist or BIOS cannot find it. I wonder if anyone could give me any suggestion about how to solve this problem. I want to make my SATA drive bootable.
Thanks in advance

Quote
Originally posted by Wonkanoby
have you removed any other form of storage drives
ive evan seen xp write the mbr to a card reader rather than the target raid drive
I have a DVD and DVD-RW connected to IDE2. I had a Hitachi HDD connected to IDE1, but it was removed before I ran Windows installation. The reason is because I want my SATA drive to have C: while having a HDD connected would mean the partions on that drive would occupy the C and D partition letters. I planned to attach the Hitachi after Windows installation has completed. BIOS has no problem detected my array, but when trying to boot from the array, the boot record cannot be found eventhough I have run the Windows installation which I thought would create the MBR automatically.
Is there any way to make my array bootable? It has been boot-enabled in the SATA settings.

LiveUpgrade - Booting from created disk without luactivate first?

Was thinking of using one of the spare disks on my system to backup before I perform an application upgrade.
i.e. creating partitions identical to source disk (prtvtoc disk0 | fmthard - -s disk1 etc) and then using lucreate to copy onto new disk. e.g. lucreate -n newdisk -m ...........
Was then going to perform the upgrade on the original disk, leaving the newly created one alone, and only switching to it in the event of failure.
If I did this, and decided I wanted to rollback and boot from my copy, would I need to just:-
lucativate newdisk.
Or could I just boot from PROM to new disk? (i.e. boot disk1)
Does the lucreate of a system disk to another one create the necessary boot records or does luactivate need to be run to do this?

I think you are saying that you want to create a second boot disk for application upgrades.
Keep in my that Live Upgrade only upgrades system related file systems.
I think our recommendations would be to:
1. Create a new BE for your application upgrades and roll back to the original BE if
something goes wrong rather than create a second boot disk.
2. Use your second disk to mirror your root pool (if you haven't done this already),
if you are using ZFS and hopefully something similar if you are using UFS.
You can create a second root pool for a ZFS BE by following the steps below. I don't know
how similar steps are done for a UFS BE. And yes, you have to luactivate the new boot disk
first, but the lucreate operation seems to apply the boot blocks.
Thanks,
Cindy
1. Create a second root pool with an SMI (VTOC) labeled disk slice.
# zpool create rpool2 c1t1d0s2
2. # lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
s10BE yes yes yes no -
# lucreate -n s10BE2 -p rpool2
3. Set the bootfs property on the second root pool.
# zpool set bootfs=rpool2/ROOT/s10BE2 rpool2
4. Activate and boot the new BE.
# luactivate s10BE2
# init 6
5. Confirm that you are booted from the second disk:
sparc# prtconf -vp | grep bootpath
bootpath: '/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w2100002037ff9c9b,0:a'
x86# prtconf -v|sed -n '/bootpath/,/value/p'

GTA 4 on windows 7 BOOT camp texture problem, macbook pro 13 january 2011 help .

GTA 4 on windows 7 BOOT camp texture problem, macbook pro 13 january 2011 help .
any
my problem looks like this
http://www.youtube.com/watch?v=PGzgS57THMo
gta 4 steam !

If GTA IV believes the system is under specification even though the computer is powerful enough to run the game with higher settings, the following will fix this problem.
This will work if your problem looks like this: "resource usage 230/60" and you can't change any other setting
Just follow the steps:
Step 1: Create a text file named ‘commandline.txt’ (without the " ")
Step 2: Put the following statement inside it:
i5 users: -availablevidmem 18.0 (with the -)
i7 users: -availablevidmem 22.0 (with the -)
Step 3: Open the main GTAIV folder (C/ program files (86)/ rockstar games/ GTA IV) and copy the commandline.txt file into it.
Step 4: locate the file "GTAIV.exe" (in GTA main folder)
Right click the file and select Properties
Under the shortcut tab, you will see an area that says Target
Modify the Target adding the command line after the last quotation mark (just add the statement you added in commandline.txt)
(remember, i5 users: -availablevidmem 18.0 / i7 users: -availablevidmem 22.0)
It should look something like this:
Make sure to add space between " and -"
I hope This helps, although late cx

Creating of incoming invoice automatically when documen info record created

Hi all,
I apologize because I am asking many questions on this forum during the last few weeks, but I have some problems which I can't solve by myself in one project.
So, this time the question is about incoming invoices.
Here is the situation:
When our customer receives incoming invoice (in paper form) we scan it and send it to one Document management system. In that system we verify the invoice and approve it. After that step the document is released to SAP (only the document info record is created and that info record points to the original document (pdf file) in that DMS).
Now the question is:
Is it possible to automatically create incoming invoice (parked) when the document is released to SAP (it+s document info record created) and to create link between these two SAP objects? Basically it means that at the moment when doc. info record is created, the incoming invoice is created (only with mandatory data) and saved (parked).
We need this functionality because our client wants to have the access to original document (pdf file) when he is about to finish the incoming invoice.
So, is it possible to set up some parameters so that incoming invoice is created automatically after the document info record is created, and linked to that document info record?

I was not aware that u have already done coding to create DIR in SAP. In that case u don't need to rely on status triggering, u may create the invoice prior to DIR creation and then link it to the DIR.It can be done in the way u have mentioned. I.e. linking at the time of DIR with BAPI_DOCUMENT_CREATE.
I doubt we have any direct link to Incoming Invoice from DIR. One of the options i can think of is linking DIR to EKPO(Purchase Order Item) which is mentioned in Invoice.
Else u may need to add another object with object table "RBKP"
Following link will help u in creating new Object for development of new screens [http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/1c31a243c711d1893e0000e8323c4f/frameset.htm]
BAPI_DOCUMENT_CREATE2 is the latest BAPI instead of BAPI_DOCUMENT_CREATE.
Points Appreciated.

Master Boot Record is greyed out, so how to use?

How do I use Master Boot Record (in Mountain Lion, to partition an external Seagate Backup+ hard drive) when it is greyed out and I can't choose it? I tried turning off Time Machine, but that didn't do anything. I also tried installing various Seagate software (like HFS4Win.exe) because what I really want to do is use one partition on the drive as back up when I'm using the Mac OS, and the second partition as back up when I'm in Windows 7 (with maybe a third partition for storage for either/both - it's 3tb). I've spent a few days at the Seagate page and nothing suggested there works, but re-formatting the drive with Master Boot Recorded sounds promising, and it won't let me!
If anyone has a solution please let me know! I'm reasonably adept!
Songsterr

Hi Lee,
If "Manage Catalog" option is greyed-out, it may be possible that you are in the "eLive" room. As in "eLive", most of the File option are displayed.
Switch to "Media" room, the option "Manage Catalog" will be enabled.
Then, please follow the steps mentioned in the article to convert the catalog Elements Organizer Help | Creating and editing catalogs.
Please let me know if you need any other assistance.
Thanks,
Swapnil

Lost my Master Boot Record

Hello to all... hoping someone can help.
I was trying to install Bootcamp and the windows installation wouldn't complete (ie. never restarted under XP to go through the last steps of the install). Now I appear to have no boot record that the MAC recognizes.
I have restarted with the "X" key - nothing
I have restarted with the Option key - nothing
I have now restarted with my orig. install discs in the hopes I could use disk utility to correct the problem.
I can see both partitions but I cannot click on "Verify disk" or "repair disk" they do not become active.
Does anyone have any ideas how I can get my machine to recognize the start up disc again? Thanks!

Hi MtlJoe,
You will probably get a quicker response in the boot camp forum located here:
http://discussions.apple.com/forum.jspa?forumID=1165

How to back up a ZFS boot disk ?

Hello all,
I have just installed Solaris 10 update 6 (10/08) on a Sparc machine (an Ultra 45 workstation) using ZFS for the boot disk.
Now I want to port a custom UFS boot disk backup script to ZFS.
Basically, this script copies the boot disk to a secondary disk and makes the secondary disk bootable.
With UFS, I had to play with the vfstab a bit to allow booting off the secondary disk, but this is not necessary with ZFS.
How can I perform such a backup of my ZFS boot disk ?
I tried the following (source disk: c1t0d0, target disk: c1t1d0):
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 110G 118G 94K /rpool
rpool/ROOT 4.58G 118G 18K legacy
rpool/ROOT/root 4.58G 25.4G 4.50G /
rpool/ROOT/root/var 79.2M 4.92G 79.2M /var
rpool/dump 16.0G 118G 16.0G -
rpool/export 73.3G 63.7G 73.3G /export
rpool/homelocal 21.9M 20.0G 21.9M /homelocal
rpool/swap 16G 134G 16K -
# zfs snapshot -r rpool@today
# zpool create -f -R /mnt rbackup c1t1d0
# zfs send -R rpool@today | zfs receive -F -d rbackup <- This one fails (see below)
# installboot /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t1d0s0
The send/receive command fails after transfering the "/" filesystem (4.5 GB) with the following error message:
cannot mount '/mnt': directory is not empty
There may be some kind of unwanted recursion here (trying to back up the backup or something) but I cannot figure it out.
I tried a workaround: creating the mount point outside the snapshot:
zfs snapshot -r rpool@today
mkdir /var/tmp/mnt
zpool create -f -R /var/tmp/mnt rbackup c1t1d0
zfs send -R rpool@today | zfs receive -F -d rbackup
But it still fails, this time with mounting "/var/tmp/mnt".
So how does one back up the ZFS boot disk to a secondary disk in a live environment ?

OK, this post requires some clarification.
First, thanks to robert.cohen and rogerfujii for giving some elements.
The objective is to make a backup of the boot disk on another disk of the same machine. The backup must be bootable just like the original disk.
The reason for doing this instead of (or, even better, in addition to) mirroring the boot disk is to be able to quickly recover a stable operating system in case anything gets corrupted on the boot disk. Corruption includes hardware failures, but also any software corruption which could be caused by a virus, an attacker or an operator mistake (rm -rf ...).
After doing lots of experiments, I found two potential solutions to this need.
Solution 1 looks like what rogerfujii suggested, albeit with a few practical additions.
It consists in using ZFS mirroring and breaking up the mirror after resilvering:
 - Configure the backup disk as a mirror of the boot disk :
 zpool attach -f rpool <boot disk>s0 <backup disk>s0
 - Copy the boot block to the backup disk:
 installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/<backup disk>s0
 - Monitor the mirror resilvering:
 zpool status rpool
 - Wait until the "action" field disappears (this can be scripted).
 - Prevent any further resilvering:
 zpool offline rpool <backup disk>s0
 Note: this step is mandatory because detaching the disk without offlining it first results in a non bootable backup disk.
 - Detach the backup disk from the mirror:
 zpool detach rpool <backup disk>s0
 POST-OPERATIONS:
 After booting on the backup disk, assuming the main boot disk is unreachable:
 - Log in as super-user.
 - Detach the main boot disk from the mirror
 zpool detach rpool <boot disk>s0
This solution has many advantages, including simplicity and using no dirty tricks. However, it has two major drawbacks:
- When booting on the backup disk, if the main boot disk is online, it will be resilvered with the old data.
- There is no easy way to access the backup disk data without rebooting.
So if you accidentally lose one file on the boot disk, you cannot easily recover it from the backup.
This is because the pool name is the same on both disks, therefore effectively preventing any pool import.
Here is now solution 2, which I favor.
It is more complex and dependent on the disk layout and ZFS implementation changes, but overall offers more flexibility.
It may need some additions if there are other disks than the boot disk with ZFS pools (I have not tested that case yet).
***** HOW TO BACKUP A ZFS BOOT DISK TO ANOTHER DISK *****
1. Backup disk partitioning
- Clean up ZFS information from the backup disk:
The first and last megabyte of the backup disk, which hold ZFS information (plus other stuff) are erased:
dd if=/dev/zero seek=<backup disk #blocks minus 2048> count=2048 of=/dev/rdsk/<backup disk>s2
dd if=/dev/zero count=2048 of=/dev/rdsk/<backup disk>s2
- Label and partition the backup disk in SMI :
format -e <backup disk>
 label
 0 -> SMI label
 y
 (If more questions asked: press Enter 3 times.)
 partition
 (Create a single parition, number 0, filling the whole disk)
 label
 0
 y
 quit
 quit
2. Data copy
- Create the target ZFS pool:
zpool create -f -o failmode=continue -R /mnt -m legacy rbackup <backup disk>s0
Note: the chosen pool name is here "rbackup".
- Create a snapshot of the source pool :
zfs snapshot -r rpool@today
- Copy the data :
zfs send -R rpool@today | zfs receive -F -d rbackup
- Remove the snapshot, plus its copy on the backup disk :
zfs destroy -r rbackup@today
zfs destroy -r rpool@today
3. Backup pool reconfiguration
- Edit the following files:
/mnt/etc/vfstab
/mnt/etc/power.conf
/mnt/etc/dumpadm.conf
In these files, replace the source pool name "rpool" with the backup pool name "rbackup".
- Remove the ZFS mount list:
rm /mnt/etc/zfs/zpool.cache
4. Making the backup disk bootable
- Note the name of the current boot filesystem:
df -k /
E.g.:
# df -k /
Filesystem kbytes used avail capacity Mounted on
rpool/ROOT/root 31457280 4726390 26646966 16% /
- Configure the boot filesystem on the backup pool:
zpool set bootfs=rbackup/ROOT/root rbackup
Note: "rbackup/ROOT/root" is derived from the main boot filesystem name "rpool/ROOT/root".
- Copy the ZFS boot block to the backup disk:
installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/<backup disk>s0
5. Cleaning up
- Detach the target pool:
zpool export rbackup
I hope this howto will be useful to those like me who need to change all their habits while migrating to ZFS.
Regards.
HL

ZFS and flar create

Hello.
So am I missing something, or does flar create totally ignore data ZFS file systems? I'm using Solaris 10-10/08 ...
Thanks.

No, you are right, Flash archives is not suported for a zfs boot environment.
But I could advise you to take a look in this blog which allow to use zfs snapshot as a way to
make a zfs flash-install :
http://blogs.sun.com/scottdickson/entry/flashless_system_cloning_with_zfs
Groucho_fr

LSO: Duplicated Records Created For Each Person During Booking For Course

Dear All,
Since 2 months ago, I've been hitting the following issue.
When I book an employee to a course through ESS, duplicated course participation records are created in the system.
The duplicated records are having different booking priorities.
And I aware that, this happened to the course which has workflow tagged to it.
Sometimes, instead of having duplicated records created, it hit dump with the following message:
"The ABAP/4 Open SQL array insert results in duplicate database records."
Does anyone know what problem is this?
Thanks.

Did you solve this problem, Im facing the same problem.
My HRP1001 table is increasing.

Possible to edit recording created through LSMW?

I created a Batch Input Recording through LSMW. In the recording, a node has got created which doesn't have an OKCode. As a result, when I process the recording, the transaction halts in between due to lack of OKCode (I have pasted a part of the recording at the bottom. The node in Bold Italic is the problem.)
In order to overcome this issue, I have to edit the recording & remove the node completely. OR I could create an OKCode entry (for an ENTER press) in the node. But I am not able to edit the recording. I am only able to add & delete Screen fields. OKCode not being a Screen field is not available for addition.
Does LSMW not give the functionality to edit recordings at all? If it so, how can I use an edited recording created through SHDB in LSMW?
A partial view of the recording follows:
>>>SAPLOIRB_APP03 321
BDC_CURSOR ROIRB0320-VALID_FROM
 BDC_OKCODE =ENTE
 ROIRB0320-STATUS
 ROIRB0320-VALID_FROM
>>>SAPMOIFA 0165
BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
 BDC_SUBSCR SAPMOIFA
>>>SAPMOIFA 0165
BDC_OKCODE =SAVE
 BDC_SUBSCR SAPMOIFA
 BDC_CURSOR OIFSPBL-PBLNR

I went ahead & completed remaining all the LSMW steps. Then I processed the created session in foreground & tracked the OKCode on each screen.
It ran perfectly upto the screen prior to the problematic node. When it got to processing the problematic node, the OKCode command dialog box remained empty. This is perfectly understandable since in the recording itself there is no line item for OKCode. Unfortunately, it did not skip processing and move onto the next node which had a 'SAVE' OKCode.
This is where the transaction halted & manual intervention was required.
Coming back to square one, I have to somehow get rid of the node or find a way to insert a OKCode line item into the recording.
Did SAP tell you that it not possible to edit an LSMW recording? It is not possible to use an SHDB recording in LSMW either?

Sony D-50 "boot-up loop" problem

I have a Sony D-50 portable recorder barely three months old that did something totally strange. Has anyone else had this problem?
During a shoot yesterday, I noticed that the Sony D50 I bought back in August would not turn OFF.
When I moved the power switch to the OFF position, the machine went into a "boot up loop," that is:
I'd turn it OFF after recording.
Screen goes black.
I get the "See you!" message.
Screen lights up again.
The word "SONY" appears as though it's gonna boot up,
Then the whole process starts over again
Screen goes black.
I get the "See you!" message.
Screen lights up.
The word "SONY" appears as though it's gonna boot up....
So, same thing late last night.
I get up this morning and turn it ON; it works fine until I turn it off, then it goes back into the "boot loop" thing again.
I tried everything I could think of, even searching for a "RESET" on the machine and in the Menu. I finally had to take the batteries out of it to shut it down.
Then, I did something that apparently---so far---fixed it.
This is so strange---right out of the Twilight Zone:
I put the batteries back in it, then it starts the loop again.
Since it won't turn OFF, I take the batteries out of it in the OFF position. I wait five minutes and put the batteries back in it with it in the OFF position.
Same problem---the "boot up loop" thing.
I take the batteries back out of it again in the OFF position and wait fifteen minutes. I put the batteries back in it while it's still in the OFF position. Guess what?
Problem solved: It's doesn't start the "boot up loop" thing.
So, I turn it back ON. Machine boots up fine and is ready to record.
OK, I turn it OFF.
Back to the exact same problem---It shuts down and goes into the "boot up loop" again.
I go back through the same process of removing and installing the batteries with the machine in the OFF position.
Nothing changes.
Then, I have an idea.
With the machine in the OFF position and going through the "boot up loop" thing, I remove the batteries.
I then move the power switch to the ON position before I put the batteries back in it---had not tried that before: reinstalling the batteries with it in the ON position. I install the batteries with the machine in the ON position.
Machine boots up fine and is ready for recording.
Now, I turn it OFF.
The machine shuts down fine with no "boot up loop" problem.
Putting the batteries back in the machine with it in the ON position instead of the OFF position apparently solved the problem.
So, I turn it back ON and then OFF several times.
Same thing: No "boot up loop" problem.
Do-do-Do-do....
The machine now works fine.
Anyone ever had this happen to a Sony D-50?
I'm wondering if I should send it to back to Sony before it does this again. For God's sake, it's only three months old!
I bought it after rave reviews in the "recorder" community, and I haven't found anyone else who has had this problem with one..

Sorry to see that you were having this issue with your PCM-D50 Linear PCM Recorder - if you continue having the issue the unit may need service - give Sony Business and Professional team a call and they will be happy to assist:
http://pro.sony.com/bbsc/ssr/services.s ... port.shtml

Missing partition boot record

I'm a computer professional and am trying to install Solaris 7 (intel) on a Celeron 400 PC. The installation was okay (a few problems with an Elsa Quickstep 1000 ISA PNP card) except for the error 'Missing partition boot record.'
The installation messages didn't show any errors; so, I'm wondering what does this error mean. If anyone can help me, I would greatly appreciate it.
Thank you.
Jasper

Just my 2 cents worth from someone who's had similar pain!
I discovered by trial and error that my Compaq Deskpro seems to want a 2MB partition described by fdisk as 'DIAGNOSTIC' in addition to the 'SOLARIS' ACTIVE partition. This doesn't appear, or have anything to do with slice layout. I believe this may be used for the VTOC and written to by root...
Just FYI - the Sun docs say that Slice 2 is by default used for 'overlap' i.e. used to describe the whole logical disk.
Slice 0 and 1 are usually for your / and swap partitions respectively.
I believe slice 4 and 5 are used normaly by /usr and /opt with slice 6 or 7 for /export/home
Colin

ZFS boot record creating problem....

Similar Messages

Maybe you are looking for