Was the donor Linode running at the time of the clone operation? If so, the filesystem will have some amount of damage on it, especially if the system was pretty busy during the clone.
The URL you pasted is out of date; the
instructions in the Linode Library will get you there more quickly.
Once you're at the finnix prompt, run:
Code:
e2fsck -fnv /dev/xvda | tee /tmp/fsckerrors.txt
... and post the results here. They'll be stored in /tmp/fsckerrors.txt for your convenience. This command invokes the ext2/ext3/ext4 filesystem checker with -f (force fsck even if filesystem is clean), -n (read-only/don't change anything), and -v (verbose output).
Omitting the -fnv and perhaps using -p (preen: assume consent for minor low-risk fixes) or -y (yes: assume consent for any fixes) will actually let it fix stuff, if you want.
If the filesystem is too far gone, another possible solution is to restore a backup of the donor Linode to the target Linode. That avoids the whole spaghetti-filesystem problem by creating a new one based upon a snapshot, but it is still susceptible to the spaghetti-database problem.
_________________
Code:
/* TODO: need to add signature to posts */
FAQ
Search
Members
Register
Login [ Anonymous ]
