> On Fri, 07 Sep 2012 08:52:46 +0200
> Mateusz Marzantowicz <mmarzantow...@osdf.com.pl> wrote:
<snip>
> Now, that you have working USB drive, check it with fsck.ext4 to
> see/repair any file system inconsistencies that might have occurred
> during this "violent" unplug action. Some people might also recommend
> doing image of valuable data partition (using dd) before running fsck.
Thank you for the advice. It must take some time to check 1T HD on a
celeron with 512 ram. I will probably do that at night.
I guess, the drive should not be mounted when I check. My USB drive is
mounted in /media, and the file manager has to options
a. Mount
b. Eject <-- is it enough
Could you help with the correct syntax ? Do I need some of emergency
switches below?
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock
list -f Force checking even if filesystem is marked
clean -v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
--
nomnex <nom...@gmail.com>
Freenode: nomnex
Registered Linux user #505281. Be counted at: http://linuxcounter.net
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
