Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: kruhm on December 23, 2008, 07:44:28 AM

Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: kruhm on December 23, 2008, 07:44:28 AM

Ran into a somewhat unresponsive server. Had around 20 defunct qpsmtpd's.

Tried to shutdown qpsmtpd. Waited 30 mins. Nothing. qpsmtpd service still up.
Gave signal-event reboot. Waited 30 minutes. Nothing.
Gave the order to manually reboot. Upon reboot: "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY"
Gave order to run: fsck -y  /dev/mapper/main-root
This has been running for 20 hours. Looks like it's throwing all the inodes into lost&found.

Re-install and recover is probably faster. Right? OK, so if I re-install on one drive and slave the second drive. I can/should be able to transfer the data over.

Mysql data is in: /var/lib/mysql/

Is this the best option?

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: kruhm on December 23, 2008, 03:49:59 PM

Well, they booted me via RIPLinux which took me awhile to figure out.

After fumbling around. I figured out the drives were there but not mounted:

Code: [Select]

fdisk -l
Followed the instructions (http://wiki.contribs.org/UpgradeDisk) and accessed the partition to make sure everything is there. Seems OK.

Reinstalling on separate drive. Plan to connect older drive to transfer.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: CharlieBrady on December 23, 2008, 11:21:48 PM

Quote from: kruhm on December 23, 2008, 07:44:28 AM

Gave the order to manually reboot. Upon reboot: "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY"
Gave order to run: fsck -y  /dev/mapper/main-root
This has been running for 20 hours. Looks like it's throwing all the inodes into lost&found.

Re-install and recover is probably faster. Right? OK, so if I re-install on one drive and slave the second drive. I can/should be able to transfer the data over.

If the file system is corrupted, then mirroring it to another drive will still leave you with a corrupted filesystem on the new copy of the old drive.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: kruhm on December 24, 2008, 12:33:44 AM

Quote from: CharlieBrady on December 23, 2008, 11:21:48 PM

If the file system is corrupted, then mirroring it to another drive will still leave you with a corrupted filesystem on the new copy of the old drive.

I'm not going to mirror it. I'm fresh reinstalling on 2 new drives. Connecting the old install. Transferring the data from the old to the new.

Merry Christmas to you.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: CharlieBrady on December 24, 2008, 03:19:56 AM

Quote from: kruhm on December 24, 2008, 12:33:44 AM

I'm not going to mirror it. I'm fresh reinstalling on 2 new drives. Connecting the old install. Transferring the data from the old to the new.

You may or may not be able to do that, depending on what the corruption is.

Quote

Merry Christmas to you.

Thanks. Same to you and all.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: kruhm on December 24, 2008, 08:02:25 AM

Almost everything is fine. Good enough for me.

I lost my picture directory though. All: 1,650,513 pics

Bummer.

Updated some WIKI info: http://wiki.contribs.org/Talk:UpgradeDisk

Still have no idea as to what happened. The logs seem to stop during logrotate.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: pfloor on December 24, 2008, 10:02:34 PM

Quote from: kruhm on December 24, 2008, 08:02:25 AM

Almost everything is fine. Good enough for me.

I lost my picture directory though. All: 1,650,513 pics

Bummer.

Did you attempt to mount both of the old drives and see if that data was recoverable from either of them?

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: kruhm on December 24, 2008, 11:46:45 PM

I only checked the one drive. I'll check the other shortly.

Thanks for the idea.

Title: Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Post by: william_syd on December 25, 2008, 02:52:45 PM

Out of curiosity, whats the difference between

Code: [Select]

fsck -y /dev/main/root
and

Code: [Select]

fsck -y /dev/mapper/main-root
?