Erro servidor Centos 7 [RESOLVIDO]

1. Erro servidor Centos 7 [RESOLVIDO]

Leonardo Rodrigues
leonardog50

(usa CentOS)

Enviado em 09/10/2018 - 19:33h

Ao ligar o servidor Centos7 estou tendo a seguinte mensagem:

[2.720255] XFS (sda3): Internal error xlog_clear_stable_blocks(2) at line 135 of file fs/xfs/xfs_log_recover.c. Caller xlog_find_tail+0x33b/0x420 [xfs]
Generating "run/initramfs/rdsosreport.txt"
[26.175065] blk_update_request: I/O error, dev fd0, sector 0
Failed to start default.target: Transaction is destructive

Tanto no sistema normal como modo recovery.
Alguem pode me ajudar como resolver?



  


2. Re: Erro servidor Centos 7 [RESOLVIDO]

Ricardo Lino Olonca
ricardoolonca

(usa Debian)

Enviado em 09/10/2018 - 20:31h

Parece que o teu disco está indo pro espaço.

Tente usar um live cd para testar o disco. Dentro do live cd rode o seguinte comando:

# fsck -y /dev/sda1

OBS: Considerando sda1 como a partição raiz do teu Linux.


3. Re: Erro servidor Centos 7 [RESOLVIDO]

Leonardo Rodrigues
leonardog50

(usa CentOS)

Enviado em 09/10/2018 - 22:10h

ricardoolonca escreveu:

Parece que o teu disco está indo pro espaço.

Tente usar um live cd para testar o disco. Dentro do live cd rode o seguinte comando:

# fsck -y /dev/sda1

OBS: Considerando sda1 como a partição raiz do teu Linux.


Realmente nao deu certo :/



4. Re: Erro servidor Centos 7 [RESOLVIDO]

Patrick Ernandes
patrickernandes

(usa Debian)

Enviado em 09/10/2018 - 22:49h

isso e xfs.. use o link abaixo:

http://fibrevillage.com/storage/666-how-to-repair-a-xfs-filesystem



5. Re: Erro servidor Centos 7 [RESOLVIDO]

Leonardo Rodrigues
leonardog50

(usa CentOS)

Enviado em 10/10/2018 - 16:06h

patrickernandes escreveu:

isso e xfs.. use o link abaixo:

http://fibrevillage.com/storage/666-how-to-repair-a-xfs-filesystem


Boa tarde.
Realmente não funcionou, coloquei um cd de live e o mesmo sequer exibe os arquivos do HD.
Coloquei ele ate em uma gaveta e em outro linux, o mesmo mostra os demais discos, apenas o deste HD que não. Creio que o problema foi o HD mesmo. De toda forma obrigado.



6. Re: Erro servidor Centos 7 [RESOLVIDO]

Leonardo Rodrigues
leonardog50

(usa CentOS)

Enviado em 11/10/2018 - 22:37h

mint ~ # mount /dev/sda3 /tmp
mount: mount /dev/sda3 on /tmp failed: Structure needs cleaning
mint ~ # xfs_repair -n /dev/sda3
Phase 1 - find and verify superblock...mint ~ # mount /dev/sda3 /tmp
mount: mount /dev/sda3 on /tmp failed: Structure needs cleaning
mint ~ # xfs_repair -n /dev/sda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi_freecount 123, counted 97 in ag 2
sb_ifree 512, counted 389
sb_fdblocks 11418644, counted 11364856
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
data fork in regular inode 546552218 claims used block 34159546
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
data fork in ino 546552222 claims free block 34159557
imap claims a free inode 546552223 is in use, would correct imap and clear inode
imap claims a free inode 546552225 is in use, would correct imap and clear inode
imap claims a free inode 546552228 is in use, would correct imap and clear inode
imap claims a free inode 546555839 is in use, would correct imap and clear inode
- agno = 3
data fork in ino 812468052 claims free block 52684183
data fork in ino 812468052 claims free block 52684184
data fork in ino 812468053 claims free block 51279833
data fork in ino 812468053 claims free block 51279834
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
entry "pgstat.stat" in shortform directory 544358976 references free inode 640059257
would have junked entry "pgstat.stat" in directory inode 544358976
data fork in ino 546552209 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552209
bad data fork in inode 546552209
would have cleared inode 546552209
data fork in ino 546552218 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "24778" in shortform directory inode 539008569 points to free inode 546552209
would junk entry
entry "pgstat.stat" in shortform directory inode 544358976 points to free inode 640059257
would junk entry
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 546552222, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
mint ~ # mount /dev/sda3 /tmp
mount: mount /dev/sda3 on /tmp failed: Structure needs cleaning
mint ~ # xfs_repair -n /dev/sda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi_freecount 123, counted 97 in ag 2
sb_ifree 512, counted 389
sb_fdblocks 11418644, counted 11364856
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
data fork in regular inode 546552218 claims used block 34159546
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
data fork in ino 546552222 claims free block 34159557
imap claims a free inode 546552223 is in use, would correct imap and clear inode
imap claims a free inode 546552225 is in use, would correct imap and clear inode
imap claims a free inode 546552228 is in use, would correct imap and clear inode
imap claims a free inode 546555839 is in use, would correct imap and clear inode
- agno = 3
data fork in ino 812468052 claims free block 52684183
data fork in ino 812468052 claims free block 52684184
data fork in ino 812468053 claims free block 51279833
data fork in ino 812468053 claims free block 51279834
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
entry "pgstat.stat" in shortform directory 544358976 references free inode 640059257
would have junked entry "pgstat.stat" in directory inode 544358976
data fork in ino 546552209 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552209
bad data fork in inode 546552209
would have cleared inode 546552209
data fork in ino 546552218 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "24778" in shortform directory inode 539008569 points to free inode 546552209
would junk entry
entry "pgstat.stat" in shortform directory inode 544358976 points to free inode 640059257
would junk entry
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 546552222, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi_freecount 123, counted 97 in ag 2
sb_ifree 512, counted 389
sb_fdblocks 11418644, counted 11364856
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
data fork in regular inode 546552218 claims used block 34159546
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
data fork in ino 546552222 claims free block 34159557
imap claims a free inode 546552223 is in use, would correct imap and clear inode
imap claims a free inode 546552225 is in use, would correct imap and clear inode
imap claims a free inode 546552228 is in use, would correct imap and clear inode
imap claims a free inode 546555839 is in use, would correct imap and clear inode
- agno = 3
data fork in ino 812468052 claims free block 52684183
data fork in ino 812468052 claims free block 52684184
data fork in ino 812468053 claims free block 51279833
data fork in ino 812468053 claims free block 51279834
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
entry "pgstat.stat" in shortform directory 544358976 references free inode 640059257
would have junked entry "pgstat.stat" in directory inode 544358976
data fork in ino 546552209 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552209
bad data fork in inode 546552209
would have cleared inode 546552209
data fork in ino 546552218 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "24778" in shortform directory inode 539008569 points to free inode 546552209
would junk entry
entry "pgstat.stat" in shortform directory inode 544358976 points to free inode 640059257
would junk entry
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 546552222, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
mint ~ # mount /dev/sda3 /tmp
mount: mount /dev/sda3 on /tmp failed: Structure needs cleaning
mint ~ # xfs_repair -n /dev/sda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi_freecount 123, counted 97 in ag 2
sb_ifree 512, counted 389
sb_fdblocks 11418644, counted 11364856
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
data fork in regular inode 546552218 claims used block 34159546
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
data fork in ino 546552222 claims free block 34159557
imap claims a free inode 546552223 is in use, would correct imap and clear inode
imap claims a free inode 546552225 is in use, would correct imap and clear inode
imap claims a free inode 546552228 is in use, would correct imap and clear inode
imap claims a free inode 546555839 is in use, would correct imap and clear inode
- agno = 3
data fork in ino 812468052 claims free block 52684183
data fork in ino 812468052 claims free block 52684184
data fork in ino 812468053 claims free block 51279833
data fork in ino 812468053 claims free block 51279834
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
entry "pgstat.stat" in shortform directory 544358976 references free inode 640059257
would have junked entry "pgstat.stat" in directory inode 544358976
data fork in ino 546552209 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552209
bad data fork in inode 546552209
would have cleared inode 546552209
data fork in ino 546552218 claims dup extent, off - 0, start - 34159546, cnt 1
correcting nextents for inode 546552218
bad data fork in inode 546552218
would have cleared inode 546552218
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "24778" in shortform directory inode 539008569 points to free inode 546552209
would junk entry
entry "pgstat.stat" in shortform directory inode 544358976 points to free inode 640059257
would junk entry
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 546552222, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.