SERVER DOWN, anyone can help?

sng

Verified User
Joined
Oct 11, 2006
Messages
33
My server is down, the Datacenter said it have to do with some software on the server... The only software i have is Direct Admin... Right now its in rescue mode and i have no clue what to do... :confused:

Can anyone help me?
 
yea i can ping the server and SSH in... Its in rescue mode Fedora 5
 
7ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1161301452.232:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NTFS driver 2.1.27 [Flags: R/W DEBUG].
JFS: nTxBlock = 7943, nTxLock = 63551
SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
PCI: Bypassing VIA 8237 APIC De-Assert Message
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
floppy0: no floppy controllers found
RAMDISK: wrong blocksize 150000, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 150000K size 1024 blocksize
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ReiserFS: sda3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sda3
VFS: Can't find ext3 filesystem on dev sda3.
VFS: Can't find an ext2 filesystem on dev sda3.
cramfs: wrong magic
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda3.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda3.
Unable to identify CD-ROM format.
hfs: unable to find HFS+ superblock
HPFS: Bad magic ... probably not HPFS
NTFS-fs error (device sda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs error (device sda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without tryin
g to recover.
NTFS-fs error (device sda3): ntfs_fill_super(): Not an NTFS volume.
UFSD (fs/ufs/super.c, 612): ufs_fill_super:ENTER
UFSD (fs/ufs/super.c, 620): ufs_fill_super:flag 0
UFSD (fs/ufs/super.c, 306): ufs_parse_options:ENTER
You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
UFSD (fs/ufs/super.c, 707): ufs_fill_super:ufstype=old
ufstype=old is supported read-only
ufs_read_super: bad magic number
UFSD (fs/ufs/super.c, 1045): ufs_fill_super:EXIT (FAILED)
VFS: Can't find a romfs filesystem on dev sda3.
UDF-fs: No VRS found
Mount JFS Failure: -22
jfs_mount failed w/return code = -22
 
doesnt work

# fsck
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
/dev/root is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

fsck.ext2: No such file or directory while trying to open /dev/root

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
 
You should ask the datacenter to look at it. Most datacenters will fix problems like that. If not then find a datacenter that actually cares to help you.
 
Its unmanaged service :(

already had a tech check the server and they said nothing is wrong with the hardware, they said some software is causing the server not to load correctly... But i have no clue where to start...

Anyone else have any suggestions or can help me SSH in my box to check... I wont mind paying for some help...
 
thanks guys im going to have the data center reload the OS to CentOS...
 
Back
Top