View Single Post
Unread 09-12-2010, 06:31 PM   #5
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: How to troubleshoot....

To gain root access the SSH must be turned on in Network setup. There was a change in the way you access root between v4 and v5.

I find it easier to use Putty or Terminal (Mac OSX) than using the debug page.
V5 is like this using Putty:
SSH
login as admin/pw
oshell
su root , pw for admin

On OSX
ssh admin@(ipaddress)

Reloading the GOS will not correct your problem. As long as you do not do a clean install your data should be safe for the time.

Now the problem you have indicate a hardware problem. I would power down and re-seat the ram and cards. If your on GOS v5 you should have a min of 1 gig of ram, anything less seams to cause issues.

I'm pretty rusty on my linux cmds. But I thing the GOS checks it file system on boot up and I think it will make repairs too. But this may only be availabe when using the null modem connection on com1.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote