5220 Appliance File System errors at Reboot - Check Forced
Hi,
Had a situation last week where our 5220 running 2.5.1 as Master / Media server had file system errors detected at boot time and a check was forced.
The check failed, a message was displayed to run fsck manually and the unit was put into a maintenance mode with a root login prompt, however my normal root password didn't work - it hasn't been changed from the default. The only option on the screen was to enter CONTROL-D to reboot the appliance, after trying this a number of times I booted the unit into single user mode and was able to have a look at the file system. I eventually got the system to boot but it has raised some questions.
The /tmp folder was full of log files, after clearing it out on Friday it is back up to almost 8000 files already, is there a scheduled process to clear down the /tmp folder, my DR appliance which is only used for replication has 146,000 files in /tmp.
What root password is required if the unit is put into maintenance mode ?.
What bootable media could be used to run a file system check with the root file system unmounted.
Would it be possible to make /tmp and /log separate mount points in a future release.
Thanks,
Dec
If you tmp folder was full it is caused by one of two things - either Telemetry data or VMWare snapshot files left behind after failed VMWare backups
Both do the same thing and both have EEB's available so please install than as soon as possible as it will soon fill up again.
Not sure on the root password - i dare say Symantec wouldn't want us to know it anyway!
This is the telemetry patch: http://www.symantec.com/docs/TECH199364
The VMware patch is not on general release - you may need to ask Symantec for that - can't find the ETrack number off hand - maybe see if you have .vmdk file in /tmp - if so call Support
There are also AIR patches if youuse AIR that should be applied - these need to be requested:
http://www.symantec.com/docs/TECH200177
Hope this helps