Ask Linux.com: Theft recovery, skeleton files, and boot-looping Eees
08-17-2008 06:00 AM
This week in our parade through the wide world of the Linux.com forums, what to do with a stolen-then-recovered laptop, how to rescue an Eee PC netbook stuck in an endless boot loop, and how make Likewise Open and /etc/skel play nice together. Plus, competitive bash scripting, unanswered questions, and a world of bad Olympic puns.
Tl;dr Solaris 11.4 won't boot on 2 machines because of what I believe is network issues. Need to know where I can find more info to troubleshoot.
I have two Solaris 11.4 systems running on VMware ESXi 6.5u2, which have suddenly (and seemingly for no reason) started boot-looping.
Both of... (2 Replies)
The situation: i try to boot centos in new environement(the vg name is changed) i edit the menu.lst of grub,did grub-install,then mkinitrd `uname -r`.img `uname -r` but when i reboot the new vg is not find and i obtain only a kernel panic :( (0 Replies)
I'm preparing to recover a Oracle Fire X4170 server in a disaster recovery test at a different location than in prod. I have some questions about fdisk partitions. I'm using Solaris 10 update 10.
On my prod server, the boot disk has 2 partitions, diagnostic and solaris. Is the diagnostic... (1 Reply)
Hi all,
Is it possible to boot from SMS menu boot devices into TS3200 FC tape library in case of an mksysb recovery on system p550 - 520 power6.
please note the library is fibre channel (1 Reply)
Hello,
I have my backup disks here because my server got hacked and we didn't like how liquidweb made the things. So we ask them to ship us the disk. They ran photorec and they got lots of .gz files from it. All accounts I would say. But 50% of them the .tar.gz files came corrupt. And is lefting... (2 Replies)
hi,
i figured why i need to boot in MMB,some of which are missing or corrupt LABEL (LIF labeL ,i guess) on the boot disk.
To explicitly corrupt this entry i think a simple dd will work.
ok let me elaborate this issue:
i need to check this functionality.
so i have one LVM boot disk
and one... (0 Replies)
my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot.
The machine come up to grub prompt.
I tried the following from grub prompt
root (hd0, then press tab key
partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
RESCUE(8) BSD System Manager's Manual RESCUE(8)NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become
non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM
(e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh,
/bin/ls, and other standard utilities, try rebooting back into the standard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a
FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin
and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of
/usr/lib in such an environment.
In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO crunchgen(1), crash(8)HISTORY
The rescue utilities first appeared in FreeBSD 5.2.
AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by
Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD July 23, 2003 BSD