NomadOfNorad
Are you serious with this question ? That's exactly what have we been telling you to do this whole thread ?
Are we talking to a brick wall here ? Do you know what boot to CD means ??????
Yes. Obviously, to boot the rescue CD (which I've done multiple times) I am booting the CD.
Please configure the BIOS on your server to allow the system to start up (ie boot) from a CD.
Get yourself a copy of the SME 7.5.1 CD and place it in the drive, then restart the server.
Select to boot to CD.
Then when you see the appropriate screen, press a key, you will be then given the opportunity to start up in Rescue mode, which will allow a broken server to start up.
Select the appropriate option F key or Type
sme rescue
Follow the on screen prompts to mount the system ie something like
/mnt/sysimage
Yes, I have done all that. Launching into Rescue Mode, it tells me at the end that it has in fact mounted /mnt/sysimage
Or do I need to do that a second time, manually, at the
-/bin/sh3-3.00# prompt? i.e. type:
chroot /mnt/sysimage
...at the prompt?
(Comes back to this part of my post) Oh, that's what I do to get into Root.
Log in as root and you will be able to do any command line stuff
eg to run the admin console type
console
then select to do an immediate backup to a connected USB (formatted ext3).
Okay, so I need the thumbdrive to be formatted specially for *nix, rather than using the default Fat32 it comes preformatted in. I did not know that part of it.
In this mode the server should be network accessible as per its configuration, just like it would be if you booted normally.
The web interface doesn't seem to be running. I can ping the machine via the IP address I gave it, but pinging it as Server (the machine-name I configured it to have on the LAN originally) doesn't work. I'm guessing that means some part of SME Server is not launching properly.
That is why, earlier, when you said that running rescue mode means that SME Server on the HDD is also running... and it looked, in the times that I was in rescue mode, as if that was NOT happening... I came away thinking either that it only
looked to me as if you were saying that that was what it was supposed to be doing, and that therefore I must be misreading that into it, and you were really saying something else, or else that you were unwittingly leaving out a step that seemed really obvious but that in fact
wasn't really obvious.
Do you understand this or is it still a mystery to you ?
Please try this procedure out on a test server BEFORE you try fixing your broken server.
You seem to be very unfamiliar with the process, so practice first on a test system.
Just do a basic install of SME to a test server, and then try to boot up to it using the install CD, and then try doing the commands mentioned above.
When you are comfortable with it, then try the same thing on the broken system.
Unfortunately, I do not have another hard drive to image this drive onto or to simply install another instance of SME Server onto, or another spare machine to mount it in.
I am now looking at the post you've just posted while I was composing the above...
I do not have a USB thumbdrive formatted for ext3, I only have ones formatted for Windows FAT32 or the like.
typing df -h yields:
Filesystem Size Used Avail Use% Mounted on
rootfs 6.0M 5.0M 660K 89% /
/dev/root.old 6.0M 5.0M 660K 89% /
/tmp/loop0 174M 174M 0 100% /mnt/runtime
/dev/vg_primary/lv_root
113G 20G 87G 19% /mnt/sysimage
/tmp/md1 99M 13M 81M 14% /mnt/sysimage/boot
/dev/root.old 6.0M 5.0M 660K 89% /mnt/sysimage/devRedoing this as root, typing df -h yields:
Filesystem Size Used Avail Use% Mounted on
/dev/vg_primary/lv_root
113G 20G 87G 19% /
/dev/md1 99M 13M 81M 14% /boottyping top -i yields:
top - 05:16:49 up 15 min, 0 users, load average: 0.00, 0.00, 0.01
Tasks: 29 total, 1 running, 27 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.3% us, 0.7% sy, 0.0% ni, 99.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 190792k total, 161528k used, 29264k free, 23268k buffers
Swap: 524280k total, 0k used, 524280k free, 114660k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
653 root 16 0 2676 968 784 R 0.7 0.5 0:03.48 topI try to invoke
config setprop smartd status enabled and it tells me:
sh: config: command not found...so it doesn't look like I'd be able to do the others.
---addendum:
Just as an extra test, I went back and restarted the CD in rescue mode, and this time set the address to 192.168.0.9 and was able to ping it at that address, so clearly the network connection is running, I just can't get to the web interface, and still pinging it by the name Server doesn't work. Am I right in understanding you would want this aspect of the issue (the matter of network-related access stuff) to be moved to its own thread?
42 Replies
9393 Views