RootForum Community

Hallo, habe schon diverse Foren durchsucht , aber leider keinen passenden Beitrag gefunden. Kann mir einer von Euch helfen??
Es muß irgendein Fehler mit Plesk sein. habe die Datei misc.frm auch gesucht, aber leider nicht gefunden.

ERROR: PleskMainDBException
MySQL query failed: Can't find file: './psa/misc.frm' (errno: 5)

0: /usr/local/psa/admin/plib/common_func.php3:216
db_query(string 'select param, val from misc')
1: /usr/local/psa/admin/plib/common_func.php3:513
get_param(string 'mysql41_compatible')
2: /usr/local/psa/admin/plib/common_func.php3:410
db_set_names()
3: /usr/local/psa/admin/plib/common_func.php3:389
db_connect_real(string 'localhost', string 'admin', string '********', string 'psa')
4: /usr/local/psa/admin/plib/common_func.php3:369
db_connect()
5: /usr/local/psa/admin/auto_prepend/auth.php3:87

Habe auch schon versucht, über den Autoinstaller Plesk neu zu installieren. Klappt auch nicht.

Starting installation of packages
Installing the package libgcc-4.0.2-8.fc4.i386
rpmdb: /var/lib/rpm/__db.001: Input/output error
error: db4 error(5) from dbenv->open: Input/output error
error: cannot open Packages index using db3 - Input/output error (5)
error: cannot open Packages database in /var/lib/rpm
warning: /usr/local/Plesk/PSA_8.0.0/update-rpm-FedoraCore-4-i386/libgcc-4.0.2-8.fc4.i386.rpm: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
rpmdb: /var/lib/rpm/__db.001: Input/output error
error: db4 error(5) from dbenv->open: Input/output error
error: cannot open Packages database in /var/lib/rpm
rpmdb: /var/lib/rpm/__db.001: Input/output error
error: db4 error(5) from dbenv->open: Input/output error
error: cannot open Packages database in /var/lib/rpm
ERROR: Unable to install the requested packages because of package dependency problems.

Vielen Dank im voraus

Jetzt habe ich grad festgestellt, das folgende Verzeichnisse nicht funktionieren:
var und lib können nicht gelesen werden
[root@p15110737 lib]# ls -l
ls: reading directory .: Input/output error
total 0
[root@p15110737 lib]# cd ..
[root@p15110737 var]# ls -l
ls: reading directory .: Input/output error
total 0
hat die festplatte vielleicht einen weg?

gordy wrote:hat die festplatte vielleicht einen weg?

Ja. Was sagt denn `dmesg`?

Linux version 2.6.16-rc6-060427a (root@buildd-i386) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Thu Apr 27 10:38:19 CEST 2006


Probing IDE interface ide0...
hda: IC35L040AVVN07-0, ATA DISK drive
hda: IRQ probe failed (0xfffffcfe)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 80418240 sectors (41174 MB) w/1863KiB Cache, CHS=65535/16/63, UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 hda4 < hda5 hda6 hda7 >
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
Adaptec aacraid driver (1.1-4 Apr 27 2006 10:37:42)
3ware Storage Controller device driver for Linux v1.26.02.001.
3ware 9000 Storage Controller device driver for Linux v2.26.02.005.
libata version 1.20 loaded.
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
ip_conntrack version 2.4 (1983 buckets, 15864 max) - 216 bytes per conntrack
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: hda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 279
ext3_orphan_cleanup: deleting unreferenced inode 278
ext3_orphan_cleanup: deleting unreferenced inode 277
ext3_orphan_cleanup: deleting unreferenced inode 276
EXT3-fs: hda1: 4 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 208k freed
floppy0: no floppy controllers found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
EXT3 FS on hda1, internal journal
XFS mounting filesystem hda5
Starting XFS recovery on filesystem: hda5 (logdev: internal)
Ending XFS recovery on filesystem: hda5 (logdev: internal)
XFS mounting filesystem hda7
Starting XFS recovery on filesystem: hda7 (logdev: internal)
Ending XFS recovery on filesystem: hda7 (logdev: internal)
XFS mounting filesystem hda6
Ending clean XFS mount for filesystem: hda6
Adding 2048248k swap on /dev/hda2. Priority:-1 extents:1 across:2048248k
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
0x0: 00 00 00 00 00 e8 0e b0 00 00 00 00 00 00 00 00
Filesystem "hda7": XFS internal error xfs_da_do_buf(2) at line 2221 of file fs/xfs/xfs_da_btree.c. Caller 0xc01fdca8

[<c0164fe0>] do_filp_open+0x40/0x60
[<c0165371>] do_sys_open+0x51/0xa0
[<c01653e7>] sys_open+0x27/0x30
[<c0102edf>] sysenter_past_esp+0x54/0x75
Filesystem "hda7": XFS internal error xfs_trans_cancel at line 1031 of file fs/xfs/xfs_trans.c. Caller 0xc0237b00

[<c0165371>] do_sys_open+0x51/0xa0
[<c01653e7>] sys_open+0x27/0x30
[<c0102edf>] sysenter_past_esp+0x54/0x75
xfs_force_shutdown(hda7,0x8) called from line 1032 of file fs/xfs/xfs_trans.c. Return address = 0xc024856b
Filesystem "hda7": Corruption of in-memory data detected. Shutting down filesystem: hda7
Please umount the filesystem, and rectify the problem(s)
[root@p15110737 ~]#

ich habe es etwas gekürzt.
Sieht wohl so aus, als ob hda7 kaputt ist oder?

Zumindest das Dateisystem auf hda7 ist kaputt. Am besten du bootest den Server im Rescue-System, falls der Provider so etwas anbietet, und überprüfst /dev/hda7 mit xfs_check (und wenn du dabei bist auch alle anderen Partitionen). Und ein neuer Kernel wäre auch mal wieder angebracht.

geht auch e2fsck? oder kann man dann noch mehr kaputt machen?

rescue:~# xfs_check /dev/hda7/
/dev/hda7/: Not a directory

fatal error -- couldn't initialize XFS library
rescue:~#

??? stehe momentan aufm schlauch.

gordy wrote:geht auch e2fsck? oder kann man dann noch mehr kaputt machen?

Falsches Dateisystem...

gordy wrote:rescue:~# xfs_check /dev/hda7/
/dev/hda7/: Not a directory

Lass das letzte Slash weg.

lol
es ist schon spät :-)


rescue:~# xfs_check /dev/hda7
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_check. If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
rescue:~#
das kommt dabei raus. wie wär es mit xfs_repair?

Lies einfach mal die Meldung, die dir xfs_check ausgegeben hat und handle entsprechend...

So, habe jetzt folgendes gemacht:
rescue:~# xfs_repair /dev/hda7
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

Habe danach das gemacht:

# xfs_repair -L /dev/hda7
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
Killed

in einem anderen beitrag stand noch "xfs_repair -n /dev/hda7
was bewirkt das?

So, jetzt wirft mir Check was raus

rescue:/# xfs_check /dev/hda7
dir 100666427 block 0 entry 41943arn bad inode number 1768843048
dir 117446325 entry bad offset 0
block 12/52517 type unknown not expected
block 12/52518 type unknown not expected
link count mismatch for inode 0 (name ?), nlink 0, counted 2
link count mismatch for inode 16998623 (name ?), nlink 4, counted 5
link count mismatch for inode 25401057 (name ?), nlink 2, counted 3
link count mismatch for inode 50331904 (name ?), nlink 0, counted 1
link count mismatch for inode 75550784 (name ?), nlink 1, counted 2
link count mismatch for inode 83925028 (name ?), nlink 3, counted 4
link count mismatch for inode 83925665 (name ?), nlink 1, counted 2
link count mismatch for inode 92423538 (name ?), nlink 1, counted 2
link count mismatch for inode 100663296 (name ?), nlink 0, counted 1
disconnected inode 100828092, nlink 1
disconnected inode 101459619, nlink 1
disconnected inode 100833640, nlink 1
disconnected inode 100833651, nlink 1
disconnected inode 100833691, nlink 1
disconnected inode 101439471, nlink 1
disconnected inode 100833889, nlink 1
disconnected inode 100833892, nlink 1
disconnected inode 100833898, nlink 1
disconnected inode 100833902, nlink 1
disconnected inode 120332760, nlink 1
sb_ifree 452171, counted 452190
sb_fdblocks 4055197, counted 4055291
user quota id 48, have/exp bc 1823/1821

was tun? habe keine ahnung mehr

hier noch der check von den anderen partitionen:

rescue:~# xfs_check /dev/hda5
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_check. If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

rescue:~# xfs_check /dev/hda4
xfs_check: unexpected XFS SB magic number 0x00000000
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
/usr/sbin/xfs_check: line 35: 1481 Segmentation fault xfs_db$DBOPTS -i -p xfs_check -c "check$OPTS" $1

rescue:~# xfs_check /dev/hda2
xfs_check: unexpected XFS SB magic number 0x01010101
xfs_check: size check failed
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
/usr/sbin/xfs_check: line 35: 1485 Segmentation fault xfs_db$DBOPTS -i -p xfs_check -c "check$OPTS" $1

rescue:~# xfs_check /dev/hda1
xfs_check: unexpected XFS SB magic number 0x01010101
xfs_check: size check failed
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
/usr/sbin/xfs_check: line 35: 1487 Segmentation fault xfs_db$DBOPTS -i -p xfs_check -c "check$OPTS" $1

habe bei hda5 "xfs_repair -L " durchgeführt.

also der 1und1 Support hat gesagt, das die festplatte ok ist. hat noch einer ne idee?

Auf hda[124] ist offensichtlich kein XFS Dateisystem. Lies bitte endlich die zugehörigen Manpages zu xfs_repair, xfs_check und fsck.

so, habe jetzt gelesen, hoffe ich habe es auch etwas verstanden. habe alle platten gemountet und dann wieder umountet. bei hda5 und hda6 ging alles problemlos. liefen beide durch bis "done" kam. Nur bei der hda7 ging es nicht.
rescue:/# xfs_repair -v /dev/hda7
damit habe ich die 3 durchlaufen lassen. Nachdem hda7 damit nicht ging, habe ich dann nochmal das i-net durchsucht und dann diesen angewendet:
rescue:/# xfs_repair -L /dev/hda7

Bei allen Beiträge hatte es damit funktioniert. Bei mir allerdings nicht.

Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
Killed

bis dahin und weiter gehts nicht.