GuardianOS default root pw? XFS repair?

[ariendj]

Hi there! I've been reading the SnapServer forums here and I have found it to be a great resource

I'm currently working to restore a RAID5 on a Snap 520 running GuardianOS 4.4.

The RAID can't be mounted so I'd like to check the XFS file system. I have reset the unit to factory default settings. After logging in via SSH I enter the command "osshell" to get to a Linux shell and su root to become root. From here I'd like to run xfs_check and/or xfs_repair.

The problem I have right now is that I don't know the default password for the root account. Does anyone here know the default root password?

As I'm rather new to the linux shell and snapservers, can anyone give me a hint on what the correct procedure is to repair my XFS md0 RAID5? The RAID got corrupted due to power(supply) failure and can't be mounted ATM.

Thanks, Arien

[blue68f100]

Look in the Admin Manual for the def PW.

I would use Spinrite on the HD's. Hacking blindlessly with limited knowledge will not have a good outcome. Beside the units does a check on boot. If repairing is going on the server can be down for hours depending on how much data is on the unit.

So Now you see the purpose of routine backups even when running a raid system.

[ariendj]

Originally Posted by blue68f100

If repairing is going on the server can be down for hours depending on how much data is on the unit.

How can I check wether repairing is going on? Should the web interface tell me this? Right now my RAID and the volume are reported as intact, just not mounted. The machine has been running some 18 hours now. Is this an indication of repair going on? If so I'd rather let it run before I plug the drives into another machine for spinrite recovery.

Originally Posted by blue68f100

So Now you see the purpose of routine backups even when running a raid system.

There is a tape backup as RAIDs are never totally fail safe. I just want to use this opportunity to learn about the snapserver as my company has quite a lot of them deployed. I'd rather learn how to get it going again _before_ anything serious happens.

[blue68f100]

To know what is going on during the boot process you need to use a null modem cable connected to the serial port and MS Terminal. If you have GUI access look in the system log. If not connect a monitor and see if it's loading the GOS.

I would invest in SpinRite. It takes time to shut down a server and do check on all HD's . But you would be surprised on how well it works. If it hangs in the 4-5% area the Hd is probably toast. This seams to be area where all of the tables are located at. I use SpinRite on all new HD's and atleast once a year, normaly twice. MFG no longer check the media for faults. They rely on the SMART system to do it. It's fine on a desk top pc, but on a RAID systems it greatly impacts the timing and performace. This is why we recommend using interprise HD's, there design for this type of service.

There have been several reports that Adaptes patch to bring up system is not complete and leaves pointers pointing to never never land. If the server had the AV and/or other addon process runing this just makes the recover harder. Most end up wipping every thing out and starting over. I would boot into the recovery console and do a clean install if you have the GSU (GOS file).