Sponsored Content
Full Discussion: Can not open boot
Top Forums UNIX for Advanced & Expert Users Can not open boot Post 27038 by Breen on Tuesday 27th of August 2002 09:57:04 AM
Old 08-27-2002
Sorry RTM, your replay must have come in concurrently with mine.
 

9 More Discussions You Might Find Interesting

1. Solaris

ERROR: Can't open boot-device

Hi i need help pls ... Server type sun fire 3800 I need to install solaris 9 . When i boot the system i recieve the following : System Controller 'sunfire3800': Type 0 for Platform Shell Type 1 for domain A console Type 2 for domain B console Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies

2. Solaris

Can't open boot device

I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies

3. Solaris

Windows / Open Solaris dual boot problem.

Okay, let me sketch the problem. I did have a ubuntu / Windows XP dual boot scenario that ran grub as my boot loader. I decided I wanted to try out solaris, so I popped in the opensolaris CD and hit install and told it to format and install over my linux partition. Of course it did that, and... (2 Replies)
Discussion started by: syndex
2 Replies

4. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

5. Solaris

boot: cannot open kernel/sparcv9/unix

Hi gurus, I'm beginner with all this unix stuff and I'm trying to install a Solaris 8 but I got this error: ok ok ok boot cdrom SC Alert: Host System has Reset Sun Fire V240, No Keyboard Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.13.2, 512 MB memory... (9 Replies)
Discussion started by: knight_mare
9 Replies

6. Solaris

Open Boot PROM - OK Prompt +dd +mount

Greetings friends, I would like to 'clone' the system/root hard disk with dd. (Solaris 10 on SPARC). If I understood correctly, 'OK Prompt' can use dd command? Can it mount drives? (to avoid any possibility of cloning the wrong drive, I'd like to output dd to file) thanks. (3 Replies)
Discussion started by: orange47
3 Replies

7. AIX

IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Hello, I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization. So when booted , it goes into OPEN Firmware I/O Hosting requires a hosting partition boot not permitted exit called > ok Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. Solaris

Can't open boot device

I installed a new hard drive completely blank. sun blade 150 openboot 4.10.6 message: Boot device: disk:a File and args: Bad magic number in disk label Can't open label package Evaluating: Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies

9. Solaris

Can't open boot device..

Hello Forum, I'm really in a fix now, I'm getting this error message now, seems like the boot block is damaged? When I do probe-all the system freezes... Can any one guide me as what to do next? System is Solaris 8 running Open Boot PROM 4 System also does not have a cd/dvd rom drive... ... (17 Replies)
Discussion started by: br1an
17 Replies
SYSTEMD-READAHEAD-REPLAY.SERVICE(8)			 systemd-readahead-replay.service		       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)

NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd- readahead - Disk read ahead logic SYNOPSIS
systemd-readahead-replay.service systemd-readahead-collect.service systemd-readahead-done.service systemd-readahead-done.timer /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE] DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process. systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead. Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot be stored, it might be a good idea to disable systemd-readahead-collect.service. On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it, systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times. OPTIONS
systemd-readahead understands the following options: -h, --help Prints a short help text and exits. --max-files= Maximum number of files to read ahead. Only valid for thes collect command. --file-size-max= Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands. --timeout= Maximum time in microseconds to spend collecting data. Only valid for the collect command. COMMANDS
The following commands are understood by systemd-readahead: collect [DIRECTORY] Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the read-ahead data. replay [DIRECTORY] Perform read-ahead on the specified directory tree. analyze [FILE] Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read ahead by the replay command. SEE ALSO
systemd(1) systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy