1 |
В сообщении от Thursday 20 November 2008 23:04:18 Joshua Murphy написал(а): |
2 |
> On Thu, Nov 20, 2008 at 12:17 PM, Юрий Дмитришин <admin@××××××××××.ua> |
3 |
wrote: |
4 |
> > Hi. |
5 |
> > |
6 |
> > I've resized my /home (/dev/sda7) with gparted and now I can't mount it. |
7 |
> > The filesystem was ext3. |
8 |
> > |
9 |
> > The output of `mount -t ext3 /dev/sda7 /home` or `mount -t |
10 |
> > ext2 /dev/sda7 /home`is: |
11 |
> > wrong fs type, bad option, bad superblock on /dev/sda7. |
12 |
> > |
13 |
> > The output of `fsck -y /dev/sda7` is: |
14 |
> > fsck 1.41.2 (02-Oct-2008) |
15 |
> > e2fsck 1.41.2 (02-Oct-2008) |
16 |
> > fsck.ext3: Group descriptors look bad... trying backup blocks... |
17 |
> > Superblock has an invalid ext3 journal (inode 8). |
18 |
> > Clear? yes |
19 |
> > |
20 |
> > *** ext3 journal has been deleted - filesystem is now ext2 only *** |
21 |
> > |
22 |
> > Corruption found in superblock. (inodes_count = 0). |
23 |
> > |
24 |
> > The superblock could not be read or does not describe a correct ext2 |
25 |
> > filesystem. If the device is valid and it really contains an ext2 |
26 |
> > filesystem (and not swap or ufs or something else), then the superblock |
27 |
> > is corrupt, and you might try running e2fsck with an alternate |
28 |
> > superblock: e2fsck -b 32768 <device> |
29 |
> > |
30 |
> > The ouput of `dumpe2fs /dev/sda7` is: |
31 |
> > dumpe2fs 1.41.2 (02-Oct-2008) |
32 |
> > Filesystem volume name: <none> |
33 |
> > Last mounted on: <not available> |
34 |
> > Filesystem UUID: 72c8beda-d12e-41d3-91f9-ed97c9c6486d |
35 |
> > Filesystem magic number: 0xEF53 |
36 |
> > Filesystem revision #: 1 (dynamic) |
37 |
> > Filesystem features: has_journal dir_index filetype sparse_super |
38 |
> > large_file |
39 |
> > Filesystem flags: signed_directory_hash |
40 |
> > Default mount options: (none) |
41 |
> > Filesystem state: clean with errors |
42 |
> > Errors behavior: Continue |
43 |
> > Filesystem OS type: Linux |
44 |
> > Inode count: 8241152 |
45 |
> > Block count: 16472641 |
46 |
> > Reserved block count: 824289 |
47 |
> > Free blocks: 3285006 |
48 |
> > Free inodes: 6202803 |
49 |
> > First block: 0 |
50 |
> > Block size: 4096 |
51 |
> > Fragment size: 4096 |
52 |
> > Blocks per group: 32768 |
53 |
> > Fragments per group: 32768 |
54 |
> > Inodes per group: 16384 |
55 |
> > Inode blocks per group: 512 |
56 |
> > Filesystem created: Tue Feb 19 15:48:22 2008 |
57 |
> > Last mount time: Wed Nov 19 21:15:08 2008 |
58 |
> > Last write time: Thu Nov 20 19:15:07 2008 |
59 |
> > Mount count: 7 |
60 |
> > Maximum mount count: 35 |
61 |
> > Last checked: Wed Nov 19 15:47:53 2008 |
62 |
> > Check interval: 15552000 (6 months) |
63 |
> > Next check after: Mon May 18 16:47:53 2009 |
64 |
> > Reserved blocks uid: 0 (user root) |
65 |
> > Reserved blocks gid: 0 (group root) |
66 |
> > First inode: 11 |
67 |
> > Inode size: 128 |
68 |
> > Journal inode: 8 |
69 |
> > Default directory hash: tea |
70 |
> > Directory Hash Seed: 2c2a57d9-9804-450f-8db8-e7c0c706b975 |
71 |
> > Journal backup: inode blocks |
72 |
> > dumpe2fs: A block group is missing an inode table while reading journal |
73 |
> > inode |
74 |
> > |
75 |
> > Thanks for your help. |
76 |
> > |
77 |
> > -- |
78 |
> > Best, Yuriy A. Dmitrishin. |
79 |
> |
80 |
> Just a quick guess off the top of my head... when you resized... did |
81 |
> you add or remove space, and did you make the change at the start or |
82 |
> end of the partition? |
83 |
|
84 |
My old disk scheme: |
85 |
sda1(/boot) sda2(/) <sda4(swap) sda5(/var) sda6(/usr) sda7(home)> |
86 |
My new disk scheme: |
87 |
sda1(/boot) sda2(/) <sda4(swap) sda5(/var) sda6(/usr) sda8(new |
88 |
partition) sda7(home)> |
89 |
|
90 |
So, I've made my sda6 smaller, added sda8 and filled all avaible space with |
91 |
sda7. |
92 |
|
93 |
-- |
94 |
Best, Yuriy A. Dmitrishin. |