Re: fsck.ext2: No such file or directory while trying to open /dev/hda3

[cosi <cosi@poczta.onet.pl>]

Dnia 03-11-17 10:51, Użytkownik whateva napisał:

> witam
> mam Debian woody/sarge.
> u=BFywa=B3em j=B1dra bf24 dostarczonego z woodym
> chcia=B3em sobie skompilowa=E6 nowe =BFeby mie=E6 odrazu obs=B3ug=EA d=BC=
> wi=EAku
> wybra=B3em 2.4.22 + low latency patch
> po skompilowaniu jadra metoda debianowa i zainstalowaniu go
> reset komp
> i podczas bootowania zatrzymuje mi sie na komunikacie:
>
> fsck.ext2: No such file or directory while trying to open /dev/hda3
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock:
>     e2fsck -b 8193 <device>
>
>
> i system prosi o podanie hasla dla root'a, loguje sie jako root i=20
> zaczynam robic o co mnie system prosi wiec
>
>
> e2fsck -b 8193 /dev/hda3 to dostaje
>
>
> fsck.ext2: No such file or directory while trying to open /dev/hda3
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock:
>     e2fsck -b 8193 <device>
>
>
> fsck.ext2 /dev/hda3
>
> to otrzymuje
>
> fsck.ext2: No such file or directory while trying to open /dev/hda3
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock:
>     e2fsck -b 8193 <device>
>
> gdzies przeczytalem zeby zrobic
>
> fsck -vy /dev/hda3
>
> ale tez otrzymalem
>
> fsck.ext2: No such file or directory while trying to open /dev/hda3
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock:
>     e2fsck -b 8193 <device>


Proponuję wyłaczyć podczas kompilacji obsługę devfs
pozdrawiam
cosi