[Download Free Power Iso Magic Disk Free
Gildo Santiago
Solaris Sparc has its own disk label, cannot read a PC disk label.
When it gives up to boot from the HDD it continues with a net boot...
I assume you have got a new Sparc box or at least a new HDD?
Do you have a Solaris CD/DVD?
This is same HDD,. At first, the cpu is showing black screen when booting. No beep sound as well. I tried to remove the vga card and clean the contacts, and fortunately, it boots again with this "Bad magic number in disk label' message. We don not have Solaris CD/DVD. What can we do now?
Did it boot from this HDD before? If yes, then the disk got a corruption: the first sectors were changed. The reason is either a broken disk or the consequence from overlapping partitions. (The format utility does not check/warn if overlapping partitions are entered.)
Without a Solaris Sparc DVD or another Sparc box you cannot recover.
With a DVD (or other Sparc box or a working net boot server) it is still questionable if a recovery is possible, but at least a re-installation and recovery from file backup is straight forward.
Depending on the version of Solaris you are using, you may be able to download the media from Oracle without any charge. Whilst you need a license to run Solaris, you don't need a license to download it, as the ISO/etc. itself is a free download. So if the system is running a currently-supported release of Solaris (10 or 11), you can download it, burn it, and try to fix things out with it. You'll need to create an Oracle account and sign in with it, but that itself won't cost you anything.
I downloaded the DVD images and made via copy /b file1 + file2 the needed iso image on Windows XP Pro. Now I cant make a bootable DVD with Nero or Alcohol 120% Can anyone help pse or may advice which...
That's very interesting - the motherboard is definitely that of a Sun Blade 1500, but as has been remarked on, that's definitely not the chassis of a Blade 1500 workstation. It's almost as if someone has transplanted the motherboard and PSU of a Blade 1500 into a generic ATX-compatible PC case at some point in this system's life...which is a bit odd, but not necessarily a problem. The Blade 1500 was basically based on the PC-compatible ATX standard in terms of motherboard form factor and power supply, so I mean, you could do it, it's just a bit of an odd thing to do. But in any case, it doesn't - or shouldn't - pose a problem for what you're trying to do.
The default disk to boot from is stored in the service processor memory and, if that configuration is lost/corrupted, then the system might be trying to boot from somewhere else giving rise to "bad magic number". That would also happen if it's trying to boot from the wrong partition.
I just wonder what happens when one wire in the (parallel-)cable is not connected.You'll get a "data corruption".
So I suggest to check the flat cable. Move the connectors half out and back in, that will clean it from dust or oxyde.
There could be an issue with the CD drive itself, or with the CD which you have burned. But there are still a couple of other possibilities here as well, such as your device aliases not actually matching the current state of the devices (e.g. since this is an IDE/ATAPI-based system, the order of the drives could have changed such that the aliases in NVRAM are no longer correct).
I would like to set my RN424 and RN104 so that they sleep most of the time unless called up by windows explorer, a backup program attempt to access, an rsync routine, a streamer drive share access, or drive maintenance. Dont really use that regularly.
I need it to be reliable especially for my RN424 as it has been relocated to the basement due to the cycling noise the NAS makes with 10TB Ironwolf drives even at idle with no apps installed....some kind of Seagate drive routine I have read. Anyway, dont have easy access to power button.
Well, at the end of the day I have have spin-down enabled on my NAS. I was just giving you my reason, which might not be the same as yours. Which is fine of course, there is room for more than one view on the pros and cons of spindown.
Reading all the input above.....it sounds like when I get my live-NAS to backup-NAS Rsync job setup (the Rsync one-time copy worked great, thanks) I can make sure that they are not spun down during those times so that one NAS to NAS share is copied.
There's no real need to disable spindown when the backups are scheduled. Even the 5-minute spindown is enough to keep the disks spinning while the backups are running. I only turn off spindown on the main NAS when we tend to use it. So media players won't have a big delay when we use them, etc. It's always on in the backup NAS.
It doesn't (and your browser won't trigger it either). You need a utility that sends the WOL "magic packet". So it's a way I can remotely trigger the NAS power-up, but there's nothing automatic about it.
My PC imaging software also runs on a power schedule (and windows has a way for the backup program to wake up the PC). So I coordinate the two schedules on my desktop PCs - setting the NAS to power on at (for example) 12:00, and telling the backup to start the image backup at 12:05.
Both features has it's own Pros and Cons. Both let's you save power if the unit is not in use or idle, they are configured differently but guides are always available online. Both are reliable but at the same time might not work as intended when used or configured improperly or not compatible with your setup.
As noted on the article: Allowing disks to slow or spin down when not being actively used can potentially save power and extend the life of the disks, but this can also slow effective read/write speeds and can make the disks appear to be off-line or cause time outs.
The new Power Timer setting is known as event-based Power Timer. Event-based Power Timer mandates a schedule for your ReadyNAS on when it should power on or off the device. Any time not selected will keep the device in the last known state. This provides a flexibility for between powering on and powering off the device for different days. Additionally, it allows you to keep the device powered off instead of turning back on.
Typically, you would use Wake On LAN (WoL), a special packet sent by another device. Unfortunately, OS6 does not have the ability to send a WoL packet prior to a backup, so doing this from another ReadyNAS is not an option. I believe there is a suggestion in the Idea Exchange to add that, though.
One problem with that, though, is that while a NAS will hold off a power-down for an outgoing backup, I don't believe it will for an incoming one (because it doesn't know it's a backup job). So if you don't know how long it will take, it could either turn off in mid-backup or stay on longer than necessary.
Event means you choose the time that the NAS will power on or off. There will be no event to trigger the NAS to turn on and any time not selected on the grid will keep the device in the last known state.
So for example you have a backup scheduled between 00:00 - 02:00 then you will have to create an event where the NAS will power on before the scheduled backup then turn off after the backup has finished.
I have disk spindown enabled on my all my NAS. On my main NAS, the disk spindown is scheduled for hours when the NAS isn't normally used - that eliminates the spin-up delay during our normal usage hours.
While many claim that disk spindown extends disk life, I've never seen a real study on that topic. Others claim that frequent disk spinups reduce disk life - and I've never seen a real study on that topic either. Since I've never seen any data on how spindown really effects disk life, I ignore that aspect - I enable disk spindown simply to reduce power use. If you are concerned about too-frequent spinup, the simplest solution is to set a longer spindown timer. For instance, if the timer is set to 1 hour, the disks can't spin up more than 24 times a day.
My backup NAS are also on a power schedule (again to reduce power use). The main operational impact is that they need to use "pull" backup jobs (hosted on the backup NAS themselves). This ensures that the backup NAS is fully running then the backup stats, and that it doesn't shut down in the middle of a backup job. Spindown is enabled, because the backups generally all complete within an hour, and there is no need to keep the disks spinning after the backup completes.
My backup NAS also have WoL enabled. That allows me to wake them up from my PC, so I can check their status, upgrade their firmware, etc. That is simply for convenience (particularly when I'm away on a trip).
Other than one backup a week, my use of my NAS is absolutely random and not that frequent (once I have them setup right). They could go a full 7 days without being accessed. So the events-based power timer (which basically operates the way I thought power timer On/off worked anyway, don't see the distinction) doesn't seem to be the 100% solution for me. I can't predict the random times I am using and don't want to just spind down every night.
Reading all the input above.....it sounds like when I get my live-NAS to backup-NAS Rsync job setup (the Rsync one-time copy worked great, thanks) I can make sure that they are not spun down during those times so that one NAS to NAS share is copied. So that might be a forced "on" using the events-based power timer? So "on" during those times and "off" all others unless woken up by WOL. Or is it "off" PLUS disk spin down?
If simply using windows file explorer triggers the WOL, turning on WOL on the NAS units might be good enough for me. If I set the spindown timer to 24, they would stay spundown all day unless a WOL command is sent from say accessing the admin page or windows file explorer? And then they would stay spun up for an hour? Is that right?
795a8134c1