How to troubleshoot....
 

Hello everyone. Again, this forum and its people are wonderful and it is amazing so many people are still following/posting.

I am having a problem. I am running a SnapServer 4400 with GOS 5.0.133 SP1. Last night when I was accessing my data via FTP (SnapServer runs in my house, and I was connecting from a machine upstairs) I started getting input/output errors. I would think this is a bad sign from a HDD. However, GOS is reporting as my drives are good. I do not want to randomly replace a drive and let the raid5 rebuild, especially if I pick the wrong one and it breaks everything :cry:

Can anyone offer some advice on what to do?

Thanks a lot
-X

Re: How to troubleshoot....
 

Look through the log, it should id a drive going bad. In/out errors can also be a network problem too.

Re: How to troubleshoot....
 

The logs ... ahh, duh. I am a idiot :D Anyway, I reboot it, I am able to write some files, then it errors out again. Here are the logs from this error....


E - Please umount the filesystem, and rectify the problem(s) kernel 09/12 02:02:26
E - Filesystem "dm-0": Corruption of in-memory data detected. Shutting down filesystem: dm-0 kernel 09/12 02:02:26
E - Filesystem "dm-0": XFS internal error xfs_trans_cancel at line 1031 of file fs/xfs/xfs_trans.c. Caller 0x782265e7 kernel 09/12 02:02:25
E - Filesystem "dm-0": XFS internal error xfs_alloc_read_agf at line 2173 of file fs/xfs/xfs_alloc.c. Caller 0x781cc1fb kernel 09/12 02:02:25
E - 0x0: 58 41 47 46 00 00 00 01 00 00 00 0c 00 6f 5f f0 kernel 09/12 02:02:25

So, it seems something is wrong with the XFS file system install? (this has been running flawless for a long time now (minus a drive going back which is easy to replace/rebuild)) If you can shed any advice on how to recover I would be very very grateful. Thanks in advance!!

Re: How to troubleshoot....
 

I did see this article : http://wiki.procooling.com/index.php...ver_210_XFS_FS

However, I do not have "osshell" command ...


Also, I do have all my GSU files ... all full images and updates and SP from like 4.2 to 5.0.133. Can I reload the GOS to fix this problem? Will I lose my data? I just want to make sure I do not lose any data....

edit - This is a RAID5 setup

Thanks in advance.

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.

Re: How to troubleshoot....
 

Ok thanks. I found the debug commands ... its /sadmin/debug.cgi , not /admin/debug.cgi

I also noticed if I just read data from it, it is ok. It is just when I try and write data.
When I get home from work today I will try reseating everything to see if that helps. I will also try with more RAM in the box

Thanks, I will keep the thread update. I am going to hold off on reinstalling, because it scares me that I might lose my data :)