Sponsored Content
Operating Systems Solaris Boot block corrupted then how can i solve that Post 302433893 by sivajerripothul on Wednesday 30th of June 2010 11:15:06 PM
Old 07-01-2010
Boot block corrupted then how can i solve that

HI every one,

i need some information that is if any boot block is corrupted den we have to go to ok prompt then boot from cdrom or network if ok prompt also not working at dat time wat i have to do .please any one can help me .

Thanking for reply
 

10 More Discussions You Might Find Interesting

1. SCO

kernerl corrupted

hi , how do i get boot on sco5.04 if it has a kernel corruption . and no kernel backup . is there any option on the boot : before i hit enter ? thx art :) (3 Replies)
Discussion started by: art_malabanan
3 Replies

2. AIX

LV corrupted

I'm getting the following error after we replaced a failed disk in a mirrored logical volume. We cleared the device entry in ODM before adding the new disk but when we create the mirror we get the following error after running lslv. 0516-022 lslv: Illegal parameter or structure value.... (1 Reply)
Discussion started by: Alfredo Jimenez
1 Replies

3. Red Hat

Its regarding boot block

I install Redhat linux9 on my local desktop pc on which windoxs XP OS is installed earlier.I made half disk empty and then install Redhat linux9 on my pc and make the system in dual boot. As I install linux latter,the grub boot block(of linux)save on the hard disk.But now I wants to delete the... (3 Replies)
Discussion started by: sameerghogre
3 Replies

4. HP-UX

Could be a corrupted file?

Hello! Do you know the meaning of... "crw-rw---- 1 informix informix 64 0x020001 Jan 21 2004 rifxroot" I don't know what the first "c" means. Furthermor, if I try to copy this file (rifxroot) it appears a message: "cp: cannot open rifxroot: No such device or address" I don't... (1 Reply)
Discussion started by: kaugrs
1 Replies

5. Emergency UNIX and Linux Support

/etc/name_to_sysnum corrupted

Hi all , i have an issue in netra 20 server when i boot the system its getting rebooting and it is giving tha" /etc/name_to_sysnum " file not found i done OK> boot -ar then also not solved please can any body send the answer ASAP regards (3 Replies)
Discussion started by: wkbn86
3 Replies

6. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

7. Shell Programming and Scripting

cronjob corrupted

dear all , i was trying to run a cron as root , something happened because it displayed "/tmp/crontabC5a4lB" 14 lines, 495 characters cron may not be running - call your system administrator does anyone knows the problems? thanks ---------- Post updated at 01:05 PM... (2 Replies)
Discussion started by: semaan
2 Replies

8. News, Links, Events and Announcements

MS to block linux boot

Microsoft to stop Linux, older Windows, from running on Windows 8 PCs | ZDNet isn't that deserve an anti trust investigation? MS monopoly is transfer into the hardware. (1 Reply)
Discussion started by: programAngel
1 Replies

9. Solaris

Verification of the Boot Block

Guys, I have a rusty question that I need help with. It has been a while since I supoprted Solaris boxes. I have several hundred solaris systems running Sol 8 and Sol 10. I built the original 250 but they have added several hundred more and I am seeing issues with these boxes that I need to... (2 Replies)
Discussion started by: scottzx7rr
2 Replies

10. Solaris

How to cross check created boot block in second disk

Hi All, I have copied a existing root file system from c0t0d0 to c0t1d0 in SUN Fire 6800 by using the below command, ufsdump 0ucf - / | (cd /new.root ; ufsrestore -rf - ) and later on I created a boot block on c0t1d0s0 by using the below command installboot /usr/platform/`uname... (1 Reply)
Discussion started by: dammaharasba
1 Replies
rcS(5)							   Debian Administrator's Manual						    rcS(5)

NAME
rcS - variables that affect the behavior of boot scripts DESCRIPTION
The /etc/default/rcS file contains variable settings in POSIX format: VAR=VAL Only one assignment is allowed per line. Comments (starting with '#') are also allowed. OPTIONS
The following variables can be set. TMPTIME On boot the files in /tmp will be deleted if their modification time, file status time and access time are all at least TMPTIME days ago. A value of 0 means that files are removed regardless of age. If you don't want the system to clean /tmp then set TMPTIME to a negative value (e.g., -1) or to the word infinite. SULOGIN Setting this to yes causes init to spawn a sulogin on the console early in the boot process. If the administrator does not login then the sulogin session will time out after 30 seconds and the boot process will continue. DELAYLOGIN Normally the system will not let non-root users log in until the boot process is complete and the system has finished switching to the default runlevel (usually level 2). However, in theory it is safe to log in a bit earlier, namely, as soon as inetd has started. Setting the variable to no allows earlier login; setting the variable to yes prevents it. Some details: The DELAYLOGIN variable controls whether or not the file /var/lib/initscripts/nologin is created during the boot process and deleted at the end of it. /etc/nologin is normally a symbolic link to the latter location, and the login(1) program refuses to allow non-root logins so long as (the target of) /etc/nologin exists. If you set the variable to no then it is advisable to ensure that /var/lib/initscripts/nologin does not exist. VERBOSE Setting this option to no (in lower case) will make the boot process a bit less verbose. Setting this option to yes will make the boot process a bit more verbose. FSCKFIX When the root and all other file systems are checked, fsck is invoked with the -a option which means "autorepair". If there are major inconsistencies then the fsck process will bail out. The system will print a message asking the administrator to repair the file system manually and will present a root shell prompt (actually a sulogin prompt) on the console. Setting this option to yes causes the fsck commands to be run with the -y option instead of the -a option. This will tell fsck always to repair the file sys- tems without asking for permission. ASYNCMOUNTNFS Set this to 'no' to disable asynchronous mounting of network drives when the network interfaces are mounted, and instead do it only once when the machine boots. The default is 'yes'. It is useful to disable this on machines where the root file system is NFS, until ifup from ifupdown works properly in such setup. NOTE
The EDITMOTD, RAMRUN and UTC variables are no longer used. The RAMLOCK, RAMSHM and RAMTMP variables have been moved to /etc/default/tmpfs; RAMSHM and RAMTMP settings in rcS are used (if set) for backward compatibility, but will be overridden by settings enabled in /etc/default/tmpfs. See tmpfs(5) for further details. The settings are not automatically migrated to /etc/default/tmpfs. Please update /etc/default/tmpfs appropriately. The UTC setting is replaced by the UTC or LOCAL setting in /etc/adjtime, and should have been migrated automatically. See hwclock(5) and hwclock(8) for further details on configuring the system clock. AUTHOR
Miquel van Smoorenburg <miquels@cistron.nl> Roger Leigh <rleigh@debian.org> SEE ALSO
hwclock(5), hwclock(8), inetd(8), init(8), inittab(5), login(1), tmpfs(5). 21 May 2012 rcS(5)
All times are GMT -4. The time now is 12:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy