Sponsored Content
Operating Systems Solaris Problem with 280R not booting Post 82567 by 98_1LE on Friday 2nd of September 2005 11:16:23 AM
Old 09-02-2005
Turns out the vendor ran "rm /dev/*" then panicked and rebooted the box. We were able to boot from CD, mount the boot disk, break the SDS mirror, copy /dev & /devices, rebuild path_to_inst, then boot and remirror.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Advanced & Expert Users

Booting Problem

Hai I have installed win 98 o.s in my system after that i have installed Red Hat Linux 7.0,there is a problem in dual booting,by default win98 is being booted, when i insert bootable linux floppy linux is loaded My doubt how to overwrite windows MBR and palce the lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies

3. UNIX for Advanced & Expert Users

Sun Booting problem

I was trying to test run a /bin/bash script i had just written when my monitor suddenly went blank.I had to shut down the machine from the systems main power. I was unable to boot afterwards and soo i went for the interactive boot process by typing boot -a. I succeded in the first stage of the... (1 Reply)
Discussion started by: lealyz
1 Replies

4. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

5. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

6. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

7. Solaris

Sunfire 280R Solaris 5.9 booting

Hi, I have to question: 1) when O/S is booting, i see messages: /dev/rdsk/c1t0d0s5: is logging /dev/rdsk/c1t0d0s3: is logging /dev/rdsk/c1t0d0s7: is logging i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies

8. AIX

AIX Booting problem

Hi, I have IBM RS/6000 44P MODEL 170 server with Aix 5.1 Till the morning server is working fine, i turned off properly but now i tried to start it is showing below error on LED and going down (power off) E051 >>>E0E0 >>>> E0E1>>>> 种种种种 >>>> 40210014 P1-C1-F1 ccccccc >>>> 40210014 >>>>E043... (3 Replies)
Discussion started by: ANAND KURADE
3 Replies

9. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies
BBACKUPD(8)							    Box Backup							       BBACKUPD(8)

NAME
bbackupd - Box Backup client daemon SYNOPSIS
bbackupd [-DFkqvVT] [-c config-file] [-t tag] DESCRIPTION
bbackupd runs on client computers in the background, finding new files to back up. When it is time for a backup, bbackupd will connect to the server (bbstored) to upload the files. A running bbackupd daemon can be controlled with the bbackupctl command, to make it shut down, reload its configuration, or start an immediate backup. bbackupd needs to be configured to tell it which files to back up, how often, and to which server (running bbstored). See the Client Configuration page for more information. For this, you must write a configuration file. You must either place it in the default location, or tell bbackupd where to find it. You can check the default location with the -h option. The default on Unix systems is usually /etc/box/bbackupd.conf. On Windows systems, it is bbackupd.conf in the same directory where bbackupd.exe is located. If bbackupd cannot find or read the configuration file, it will log an error message and exit. bbackupd usually writes log messages to the system logs, using the facility local5, which you can use to filter them to send them to a separate file. It can also write them to the console, see options below. If bbackupd is not doing what you expect, please check the logs first of all. Options -c config-file Use the specified configuration file. If -c is omitted, the last argument is the configuration file. If none is specified, the default is used (see above). -D Debugging mode. Do not fork into the background (do not run as a daemon). Not available on Windows. -F No-fork mode. Same as -D for bbackupd. Not available on Windows. -k Keep console open after fork, keep writing log messages to it. Not available on Windows. -q Run more quietly. Reduce verbosity level by one. Available levels are NOTHING, FATAL, ERROR, WARNING, NOTICE, INFO, TRACE, EVERYTHING. Default level is NOTICE in non-debugging builds. Use once to drop to WARNING level, twice for ERROR level, four times for no logging at all. -v Run more verbosely. Increase verbosity level by one. Use once to raise to INFO level, twice for TRACE level, three times for EVERYTHING (currently the same as TRACE). -V Run at maximum verbosity (EVERYTHING level). -t tag Tag each console message with specified marker. Mainly useful in testing when running multiple daemons on the same console. -T Timestamp each line of console output. FILES
/etc/box/bbackupd.conf SEE ALSO
bbackupd.conf(5), bbackupd-config(8), bbackupctl(8) AUTHORS
Ben Summers Per Thomsen James O'Gorman Box Backup 0.11 10/28/2011 BBACKUPD(8)
All times are GMT -4. The time now is 02:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy