1 |
On Tuesday 23 January 2007 18:05, Sigfrido V. Ortiz C. wrote: |
2 |
> Try fsck --help |
3 |
> then select the options related to recovery and repair the system |
4 |
> file at least twice, then reboot your system with "shutdown -b now" |
5 |
> |
6 |
> Based in my experience this occur after shutdown by power fault and |
7 |
> not by command. |
8 |
> The format must be fsck -p -f /dev/partition_name |
9 |
> |
10 |
> the flag -p will repair automatically your system and the flag -f |
11 |
> force the revision even the file system appear like clean. |
12 |
> Good luck!!! |
13 |
> Sigfrido |
14 |
|
15 |
Hi, |
16 |
|
17 |
Please don't top post. If you know the fsck command then you know why I |
18 |
have asked this. |
19 |
|
20 |
I wouldn't advise that the OP follows your advise - from the way he |
21 |
wrote his post it is very likely he doesn't know a whole lot about |
22 |
filesystems and fsck programs. So he will blindly enter your commands, |
23 |
forcing an action to occur and potentially causing further loss without |
24 |
him having much of a clue about what he has just done. |
25 |
|
26 |
The force flag is useful, after you get an output from fsck and you know |
27 |
what it will do and are prepared to accept the loss. jcd isn't in that |
28 |
position. |
29 |
|
30 |
jcd, what you should do is gather information about what happened and |
31 |
try figure it out. If you can't, lots of people here will decrypt it |
32 |
for you (as much as possible) then tell you what to do and explain what |
33 |
will happen as a result. |
34 |
|
35 |
The golden rule: don't ever run a file system checker blindly without |
36 |
some understanding of what it's doing. |
37 |
> |
38 |
> alan@××××××××××××××××.za wrote: |
39 |
> > On Tuesday 23 January 2007 13:11, jcd wrote: |
40 |
> >>Hi. |
41 |
> >>I'm in bad situation. I have two physical disks. First (DiskA) have |
42 |
> >>200GB and second (DiskB) have 160GB capacity. On DiskB I have Linux |
43 |
> >>partitions and some data partitions. On DiskA I had had 40GB NTFS |
44 |
> >>(Windows) and 160GB NTFS partitions (data), but I already deleted |
45 |
> >>Windows partition. So, I copied data from 160GB partition on DiskA |
46 |
> >> to temporary space on DiskB, then I deleted remaining NTFS |
47 |
> >> partition on DiskA and created one 200GB ext3 partition (I think |
48 |
> >> so. In cfdsik I chose partition type '83 Linux') and then |
49 |
> >> formatted it 'mke2fs -j /dev/sdb1'. Then I copied (moved :( ) all |
50 |
> >> the data back to DiskA and everuthing was fine. It was yesterday. |
51 |
> >> Today I started PC and at startup init said "Some local |
52 |
> >> filesystems failed to mount". OK, in /etc/fstab I have "/dev/sdb1 |
53 |
> >> /mnt/zaloha ext3 noatime 0 2" ... it seems to be good. I also |
54 |
> >> tried to change ext2, but with both 'mount -a' says: |
55 |
> >>mount: wrong fs type, bad option, bad superblock on /dev/sdb1, |
56 |
> >> missing codepage or other error |
57 |
> >> In some cases useful info is found in syslog - try |
58 |
> >> dmesg | tail or so. |
59 |
> >>In /var/log/messages I found just "VFS: Can't find ext3 filesystem |
60 |
> >> on dev sdb1" :((. When I try just 'mount /dev/sdb1 /mnt/zaloha', |
61 |
> >> at /mnt/zaloha I have mounted that old Windows partition that I |
62 |
> >> already deleted. Do you know any solution how can I get back my |
63 |
> >> ext3 partition to get back my data please? And what could be cause |
64 |
> >> of this problem or when I can find what is the cause? Thanks very |
65 |
> >> very much. |
66 |
> > |
67 |
> > You've given lots of words, but very very little information, not |
68 |
> > even the commands you used to perform these actions. Without this |
69 |
> > info it becomes very hard to help you out. |
70 |
> > |
71 |
> > Meantime, please provide the output of the following commands: |
72 |
> > |
73 |
> > fdisk -l |
74 |
> > fsck /dev/sdb1 |
75 |
> > mount /dev/sdb1 /some/mount/point |
76 |
> > |
77 |
> > and we'll take it from there |
78 |
> > |
79 |
> > alan |
80 |
-- |
81 |
gentoo-user@g.o mailing list |