SHOW:
|
|
- or go back to the newest paste.
| 1 | - | ┌({1.72})─[~/Desktop]─
|
| 1 | + | └(21:35:18)-(firewall@firewall) $ sudo fsck -n /dev/sdc |
| 2 | - | └(21:18:30)-(firewall@firewall) $ sudo fsck -a /dev/sdc1 |
| 2 | + | |
| 3 | e2fsck 1.42 (29-Nov-2011) | |
| 4 | - | dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN |
| 4 | + | fsck.ext2: Superblock invalid, trying backup blocks... |
| 5 | - | Free cluster summary uninitialized (should be 976991) |
| 5 | + | fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc |
| 6 | - | Auto-setting. |
| 6 | + | |
| 7 | - | Performing changes. |
| 7 | + | The superblock could not be read or does not describe a correct ext2 |
| 8 | - | /dev/sdc1: 0 files, 1/976992 clusters |
| 8 | + | filesystem. If the device is valid and it really contains an ext2 |
| 9 | - | Writing 8 bytes at 1000 failed: Operation not permitted |
| 9 | + | filesystem (and not swap or ufs or something else), then the superblock |
| 10 | is corrupt, and you might try running e2fsck with an alternate superblock: | |
| 11 | e2fsck -b 8193 <device> |
