Difference between revisions of "User:Trogod/System0Maintai"

Revision as of 03:29, 4 May 2011

disk repair

3 May 2011

booted from live DVD for mythbuntu

ubuntu@ubuntu:~$ sudo parted -l
Model: ATA SAMSUNG SP0822N (scsi)
Disk /dev/sda: 80.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos  

Number  Start   End     Size    Type     File system     Flags
 1      32.3kB  1287MB  1287MB  primary  ext2            boot
 2      1287MB  10.3GB  9052MB  primary  linux-swap(v1)
 3      10.3GB  26.5GB  16.1GB  primary  ext3
 4      26.5GB  47.9GB  21.5GB  primary  ext3


Model: ATA Hitachi HDT72101 (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  1000GB  1000GB  jfs 
 

Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
Error: /dev/sr0: unrecognised disk label  
 

and then I ran fsck:

ubuntu@ubuntu:~$ sudo fsck.jfs -n /dev/sdb1
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 5/4/2011 3.21.10
The current device is:  /dev/sdb1
Block size in bytes:  4096
Filesystem size in blocks:  244190429
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
**Phase 2 - Count links
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Verify File/Directory Allocation Maps
Errors detected in the Fileset File/Directory Allocation Map control information. (F)
Errors detected in the Fileset File/Directory Allocation Map. (F)
**Phase 8 - Verify Disk Allocation Maps
Incorrect data detected in disk allocation control structures.
976761716 kilobytes total disk space.
   146077 kilobytes in 66698 directories.
964783365 kilobytes in 413547 user files.
       20 kilobytes in extended attributes
   513312 kilobytes reserved for system use.
 11611096 kilobytes are available for use.
File system checked READ ONLY.
Filesystem is dirty.
Filesystem is dirty but is marked clean.  In its present state,
the results of accessing /dev/sdb1 (except by this utility) are undefined.
ubuntu@ubuntu:~$