J9521A RF Manager Problem - Fail to Login/Fail to Launch

[JiJoMa]

Dear All,

I am facing a problem while booting the RF Manager: I got it out of the box brand new and when I powered it on it takes a while to and I get the below screen:

.

.

.

ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
SELinux: Disabled at runtime.
audit(1403551442.677:2): selinux=0 auid=4294967295 ses=4294967295
INIT: version 2.86 booting
Welcome to CentOS release 5.2 (Final)
Press 'I' to enter interactive startup.
Setting clock (localtime): Mon Jun 23 19:24:07 EDT 2014 [ OK ]
Starting udev: [ OK ]
Setting hostname rfmanager: [ OK ]
No devices found
Setting up Logical Volume Management: /dev/sda8: read failed after 0 of 2048 at 0: Input/output error
No volume groups found
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -f /dev/sda5
/1: 81670/5124480 files (0.6% non-contiguous), 672661/5120710 blocks
[/sbin/fsck.ext3 (1) -- /mnt/storage] fsck.ext3 -a -f LABEL=/mnt/storage
fsck.ext3: Unable to resolve 'LABEL=/mnt/storage'
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a -f /dev/sda3
/boot1: 36/26208 files (11.1% non-contiguous), 18658/104420 blocks
[FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):

I am trying to find some info from the web bur unfortuanately I couldnt find any documentation.

Anyone can help with this??

Thanks.

[Arimo]

The boot log says that there's a file system failure. There's not much to do about it, just call support. If it doesn't boot after Control-D that is.

[JiJoMa]

Thanks Arimo

It actually does reboot after Control-D but it gets back to the same point!

I wonder if I am missing somthing or if this can be solved..

Thanks for the help Arimo.