2 příspěvky / 0 new
Poslední
Obrázek uživatele Eda01
Offline
Naposledy viděn: 15 let 5 měsíců zpět
Připojen: 23.09.2008 - 10:04
Nejde nastartovat systém po nekorektním vypnutí počítače - chyba souborového systému-vyřešeno

Dobrý den,
potřebuji poradit. Po samovolném zatuhnutí počítače a násleném restartu pomocí zapínacího tlačítka se poškodil file systém ext 3-home na disku sda7.
Při následném startu se po automatické kontrole napíše něco jako /dev/sda7 unexcepted inconsistency run fsck manualy (i.e. without -a or -p options).
Mohu se následně přihlásit jako root a spustit si i grafické prostředí pomocí startx.
Zkoušel jsem opravu pomocí instalačního cd a také se to nepovedlo opravit.
Hledal jsem na googlu, ale nikde jsem nenašel jednoduché řešení, jak problém vyřešit.
Zkoušel jsem disk sda7 odpojit a následně zadat e2fsck/dev/sda7
Systém mi napsal něco jako no such file or directory.
Díky moc:-)

Obrázek uživatele JirkaZ
Offline
Naposledy viděn: 6 let 5 měsíců zpět
Připojen: 17.10.2006 - 19:12
A příkaz

e2fsck jste spouštěl jako root? Máte nainstalovaný balíček e2fsprogs?

JirkaZ

Obrázek uživatele Eda01
Offline
Naposledy viděn: 15 let 5 měsíců zpět
Připojen: 23.09.2008 - 10:04
Děkuji všem za odpovědi a

Děkuji všem za odpovědi a náměty pro další řešení.
Včera jsem počítač zapnul, opět proběhl na začátku test s chybami ( dev/sda7 unexcepted inconsistency run fsck manualy (i.e. without -a or -p options)a následně jsem se přihlásil jako ROOT. Pak jsem si spustil grafické prostředí pomocí startx.
V konzoli jsem zkoušel příkazy:
(none):~ # e2fsck /dev/sda7
e2fsck 1.40.8 (13-Mar-2008)
e2fsck: Device or resource busy while trying to open /dev/sda7
Filesystem mounted or opened exclusively by another program?
(none):~ # e2fsck -a /dev/sda7
e2fsck: Device or resource busy while trying to open /dev/sda7
Filesystem mounted or opened exclusively by another program?
(none):~ # umount/dev/sda7
bash: umount/dev/sda7: No such file or directory
(none):~ # fsck /dev/sda7
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
fsck.ext3: Device or resource busy while trying to open /dev/disk/by-id/scsi-SATA_WDC_WD3200AAJS-_WD-WMAT10537192-part7
Filesystem mounted or opened exclusively by another program?
(none):~ #
(none):~ # umount/mnt/sda7
bash: umount/mnt/sda7: No such file or directory
(none):~ # e2fsck/dev/sda7
bash: e2fsck/dev/sda7: No such file or directory
(none):~ #
(none):~ #
Možná se to někomu zdá jednoduché,ale mě se to ještě nepovedlo vyřešit.
Jestli zkusíte z výpisu zjistit, v čem by mohl být problém:-)
Nemám to třeba zkusit bez grafického prostředí? Jinak mě nic nenapadá, díky moc:-)

Obrázek uživatele Eda01
Offline
Naposledy viděn: 15 let 5 měsíců zpět
Připojen: 23.09.2008 - 10:04
Už je to v pořádku:-)

Zadal jsem: (none):~ # e2fsck -f -y -v /dev/sda7 (Důležité jsou uvedené mezery v příkazu!!!!).
e2fsck 1.40.8 (13-Mar-2008)
Pass 1: Checking inodes, blocks, and sizes

Pak se pár minut nic nedělo, chce to čekat:-)
Nakonec se file systém opravil a stačilo zrestartovat.
Díky za pomoc při řešení problému, už je to v pořádku a SUSE zase splehlivě funguje:-)
----------------------------------------------------------------------
Nebyl jsem doma, když se stala ta věc, že počítač zatuhl. Domnívám se, že se jednalo o problém aktualizace systému spolu s náhodným zatuhnutím Firefoxu.
Při použití tlačítka restart se stalo, co se stalo:-)
Hlavně, že už je vše v pořádku. Jinak se mi nikdy nestalo ani to použití tlačítka restart, že by systém nenastartoval.

Můžete se podívat na výpis z konzole, jak oprava úspěšně proběhla!!!!
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 9593240: 38404423 38404432
Multiply-claimed block(s) in inode 9601025: 38404423
Multiply-claimed block(s) in inode 9601026: 38404432
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 3 inodes containing multiply-claimed blocks.)

File ... (inode #9593240, mod time Sun Oct 19 18:56:11 2008)
has 2 multiply-claimed block(s), shared with 2 file(s):
/amalka/FOTOGRAFIE/FOTOGRAFIE 2008_new/Domov Lounovice_DVD_07-08/Domov Lounovice_DVD_08 (inode #9601026, mod time Tue Oct 21 20:27:16 2008)
/amalka/FOTOGRAFIE/FOTOGRAFIE 2008_new/Domov Lounovice_DVD_07-08/Domov Lounovice_DVD_07 (inode #9601025, mod time Tue Oct 21 20:27:16 2008)
Clone multiply-claimed blocks? yes

File /amalka/FOTOGRAFIE/FOTOGRAFIE 2008_new/Domov Lounovice_DVD_07-08/Domov Lounovice_DVD_07 (inode #9601025, mod time Tue Oct 21 20:27:16 2008)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #9593240, mod time Sun Oct 19 18:56:11 2008)
Multiply-claimed blocks already reassigned or cloned.

File /amalka/FOTOGRAFIE/FOTOGRAFIE 2008_new/Domov Lounovice_DVD_07-08/Domov Lounovice_DVD_08 (inode #9601026, mod time Tue Oct 21 20:27:16 2008)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #9593240, mod time Sun Oct 19 18:56:11 2008)
Multiply-claimed blocks already reassigned or cloned.

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 7554382
Connect to /lost+found? yes

Inode 7554382 ref count is 2, should be 1. Fix? yes

Unattached inode 9592847
Connect to /lost+found? yes

Inode 9592847 ref count is 2, should be 1. Fix? yes

Unattached inode 9592851
Connect to /lost+found? yes

Inode 9592851 ref count is 2, should be 1. Fix? yes

Unattached inode 9592853
Connect to /lost+found? yes

Inode 9592853 ref count is 2, should be 1. Fix? yes

Unattached inode 9592856
Connect to /lost+found? yes

Inode 9592856 ref count is 2, should be 1. Fix? yes

Unattached inode 9592859
Connect to /lost+found? yes

Inode 9592859 ref count is 2, should be 1. Fix? yes

Unattached inode 9592872
Connect to /lost+found? yes

Inode 9592872 ref count is 2, should be 1. Fix? yes

Unattached inode 9592881
Connect to /lost+found? yes

Inode 9592881 ref count is 2, should be 1. Fix? yes

Unattached inode 9592887
Connect to /lost+found? yes

Inode 9592887 ref count is 2, should be 1. Fix? yes

Unattached inode 9592890
Connect to /lost+found? yes

Inode 9592890 ref count is 2, should be 1. Fix? yes

Unattached inode 9592891
Connect to /lost+found? yes

Inode 9592891 ref count is 2, should be 1. Fix? yes

Unattached inode 9592904
Connect to /lost+found? yes

Inode 9592904 ref count is 2, should be 1. Fix? yes

Unattached inode 9592907
Connect to /lost+found? yes

Inode 9592907 ref count is 2, should be 1. Fix? yes

Unattached inode 9592909
Connect to /lost+found? yes

Inode 9592909 ref count is 2, should be 1. Fix? yes

Unattached inode 9592917
Connect to /lost+found? yes

Inode 9592917 ref count is 2, should be 1. Fix? yes

Unattached inode 9592919
Connect to /lost+found? yes

Inode 9592919 ref count is 2, should be 1. Fix? yes

Unattached inode 9592922
Connect to /lost+found? yes

Inode 9592922 ref count is 2, should be 1. Fix? yes

Unattached inode 9592930
Connect to /lost+found? yes

Inode 9592930 ref count is 2, should be 1. Fix? yes

Unattached inode 9592932
Connect to /lost+found? yes

Inode 9592932 ref count is 2, should be 1. Fix? yes

Unattached inode 9592938
Connect to /lost+found? yes

Inode 9592938 ref count is 2, should be 1. Fix? yes

Unattached inode 9592941
Connect to /lost+found? yes

Inode 9592941 ref count is 2, should be 1. Fix? yes

Unattached inode 9592942
Connect to /lost+found? yes

Inode 9592942 ref count is 2, should be 1. Fix? yes

Unattached inode 9592943
Connect to /lost+found? yes

Inode 9592943 ref count is 2, should be 1. Fix? yes

Unattached inode 9592944
Connect to /lost+found? yes

Inode 9592944 ref count is 2, should be 1. Fix? yes

Unattached inode 9592945
Connect to /lost+found? yes

Inode 9592945 ref count is 2, should be 1. Fix? yes

Unattached inode 9592955
Connect to /lost+found? yes

Inode 9592955 ref count is 2, should be 1. Fix? yes

Unattached inode 9592957
Connect to /lost+found? yes

Inode 9592957 ref count is 2, should be 1. Fix? yes

Unattached inode 9592963
Connect to /lost+found? yes

Inode 9592963 ref count is 2, should be 1. Fix? yes

Unattached inode 9592964
Connect to /lost+found? yes

Inode 9592964 ref count is 2, should be 1. Fix? yes

Unattached inode 9592965
Connect to /lost+found? yes

Inode 9592965 ref count is 2, should be 1. Fix? yes

Unattached inode 9592969
Connect to /lost+found? yes

Inode 9592969 ref count is 2, should be 1. Fix? yes

Unattached inode 9592970
Connect to /lost+found? yes

Inode 9592970 ref count is 2, should be 1. Fix? yes

Unattached inode 9592981
Connect to /lost+found? yes

Inode 9592981 ref count is 2, should be 1. Fix? yes

Unattached inode 9592988
Connect to /lost+found? yes

Inode 9592988 ref count is 2, should be 1. Fix? yes

Unattached inode 9592992
Connect to /lost+found? yes

Inode 9592992 ref count is 2, should be 1. Fix? yes

Unattached inode 9592993
Connect to /lost+found? yes

Inode 9592993 ref count is 2, should be 1. Fix? yes

Unattached inode 9593003
Connect to /lost+found? yes

Inode 9593003 ref count is 2, should be 1. Fix? yes

Unattached inode 9593007
Connect to /lost+found? yes

Inode 9593007 ref count is 2, should be 1. Fix? yes

Unattached inode 9593008
Connect to /lost+found? yes

Inode 9593008 ref count is 2, should be 1. Fix? yes

Unattached inode 9593009
Connect to /lost+found? yes

Inode 9593009 ref count is 2, should be 1. Fix? yes

Unattached inode 9593010
Connect to /lost+found? yes

Inode 9593010 ref count is 2, should be 1. Fix? yes

Unattached inode 9593012
Connect to /lost+found? yes

Inode 9593012 ref count is 2, should be 1. Fix? yes

Unattached inode 9593021
Connect to /lost+found? yes

Inode 9593021 ref count is 2, should be 1. Fix? yes

Unattached inode 9593026
Connect to /lost+found? yes

Inode 9593026 ref count is 2, should be 1. Fix? yes

Unattached inode 9593028
Connect to /lost+found? yes

Inode 9593028 ref count is 2, should be 1. Fix? yes

Unattached inode 9593042
Connect to /lost+found? yes

Inode 9593042 ref count is 2, should be 1. Fix? yes

Unattached inode 9593045
Connect to /lost+found? yes

Inode 9593045 ref count is 2, should be 1. Fix? yes

Unattached inode 9593051
Connect to /lost+found? yes

Inode 9593051 ref count is 2, should be 1. Fix? yes

Unattached inode 9593053
Connect to /lost+found? yes

Inode 9593053 ref count is 2, should be 1. Fix? yes

Unattached inode 9593055
Connect to /lost+found? yes

Inode 9593055 ref count is 2, should be 1. Fix? yes

Unattached inode 9593060
Connect to /lost+found? yes

Inode 9593060 ref count is 2, should be 1. Fix? yes

Unattached inode 9593062
Connect to /lost+found? yes

Inode 9593062 ref count is 2, should be 1. Fix? yes

Unattached inode 9593065
Connect to /lost+found? yes

Inode 9593065 ref count is 2, should be 1. Fix? yes

Unattached inode 9593068
Connect to /lost+found? yes

Inode 9593068 ref count is 2, should be 1. Fix? yes

Unattached inode 9593069
Connect to /lost+found? yes

Inode 9593069 ref count is 2, should be 1. Fix? yes

Unattached inode 9593080
Connect to /lost+found? yes

Inode 9593080 ref count is 2, should be 1. Fix? yes

Unattached inode 9593086
Connect to /lost+found? yes

Inode 9593086 ref count is 2, should be 1. Fix? yes

Unattached inode 9593087
Connect to /lost+found? yes

Inode 9593087 ref count is 2, should be 1. Fix? yes

Unattached inode 9593088
Connect to /lost+found? yes

Inode 9593088 ref count is 2, should be 1. Fix? yes

Unattached inode 9593089
Connect to /lost+found? yes

Inode 9593089 ref count is 2, should be 1. Fix? yes

Unattached inode 9593092
Connect to /lost+found? yes

Inode 9593092 ref count is 2, should be 1. Fix? yes

Unattached inode 9593094
Connect to /lost+found? yes

Inode 9593094 ref count is 2, should be 1. Fix? yes

Unattached inode 9593099
Connect to /lost+found? yes

Inode 9593099 ref count is 2, should be 1. Fix? yes

Unattached inode 9593102
Connect to /lost+found? yes

Inode 9593102 ref count is 2, should be 1. Fix? yes

Unattached inode 9593105
Connect to /lost+found? yes

Inode 9593105 ref count is 2, should be 1. Fix? yes

Unattached inode 9593107
Connect to /lost+found? yes

Inode 9593107 ref count is 2, should be 1. Fix? yes

Unattached inode 9593108
Connect to /lost+found? yes

Inode 9593108 ref count is 2, should be 1. Fix? yes

Unattached inode 9593109
Connect to /lost+found? yes

Inode 9593109 ref count is 2, should be 1. Fix? yes

Unattached inode 9593111
Connect to /lost+found? yes

Inode 9593111 ref count is 2, should be 1. Fix? yes

Unattached inode 9593112
Connect to /lost+found? yes

Inode 9593112 ref count is 2, should be 1. Fix? yes

Unattached inode 9593119
Connect to /lost+found? yes

Inode 9593119 ref count is 2, should be 1. Fix? yes

Unattached inode 9593122
Connect to /lost+found? yes

Inode 9593122 ref count is 2, should be 1. Fix? yes

Unattached inode 9593127
Connect to /lost+found? yes

Inode 9593127 ref count is 2, should be 1. Fix? yes

Unattached inode 9593129
Connect to /lost+found? yes

Inode 9593129 ref count is 2, should be 1. Fix? yes

Unattached inode 9593130
Connect to /lost+found? yes

Inode 9593130 ref count is 2, should be 1. Fix? yes

Unattached inode 9593131
Connect to /lost+found? yes

Inode 9593131 ref count is 2, should be 1. Fix? yes

Unattached inode 9593137
Connect to /lost+found? yes

Inode 9593137 ref count is 2, should be 1. Fix? yes

Unattached inode 9593138
Connect to /lost+found? yes

Inode 9593138 ref count is 2, should be 1. Fix? yes

Unattached inode 9593139
Connect to /lost+found? yes

Inode 9593139 ref count is 2, should be 1. Fix? yes

Unattached inode 9593140
Connect to /lost+found? yes

Inode 9593140 ref count is 2, should be 1. Fix? yes

Unattached inode 9593143
Connect to /lost+found? yes

Inode 9593143 ref count is 2, should be 1. Fix? yes

Unattached inode 9593150
Connect to /lost+found? yes

Inode 9593150 ref count is 2, should be 1. Fix? yes

Unattached inode 9593153
Connect to /lost+found? yes

Inode 9593153 ref count is 2, should be 1. Fix? yes

Unattached inode 9593155
Connect to /lost+found? yes

Inode 9593155 ref count is 2, should be 1. Fix? yes

Unattached inode 9593157
Connect to /lost+found? yes

Inode 9593157 ref count is 2, should be 1. Fix? yes

Unattached inode 9593159
Connect to /lost+found? yes

Inode 9593159 ref count is 2, should be 1. Fix? yes

Unattached inode 9593164
Connect to /lost+found? yes

Inode 9593164 ref count is 2, should be 1. Fix? yes

Unattached inode 9593167
Connect to /lost+found? yes

Inode 9593167 ref count is 2, should be 1. Fix? yes

Unattached inode 9593176
Connect to /lost+found? yes

Inode 9593176 ref count is 2, should be 1. Fix? yes

Unattached inode 9593182
Connect to /lost+found? yes

Inode 9593182 ref count is 2, should be 1. Fix? yes

Unattached inode 9593189
Connect to /lost+found? yes

Inode 9593189 ref count is 2, should be 1. Fix? yes

Unattached inode 9593202
Connect to /lost+found? yes

Inode 9593202 ref count is 2, should be 1. Fix? yes

Unattached inode 9593203
Connect to /lost+found? yes

Inode 9593203 ref count is 2, should be 1. Fix? yes

Unattached inode 9593204
Connect to /lost+found? yes

Inode 9593204 ref count is 2, should be 1. Fix? yes

Unattached inode 9593205
Connect to /lost+found? yes

Inode 9593205 ref count is 2, should be 1. Fix? yes

Unattached inode 9593207
Connect to /lost+found? yes

Inode 9593207 ref count is 2, should be 1. Fix? yes

Unattached inode 9593208
Connect to /lost+found? yes

Inode 9593208 ref count is 2, should be 1. Fix? yes

Unattached inode 9593210
Connect to /lost+found? yes

Inode 9593210 ref count is 2, should be 1. Fix? yes

Unattached inode 9593211
Connect to /lost+found? yes

Inode 9593211 ref count is 2, should be 1. Fix? yes

Unattached inode 9593212
Connect to /lost+found? yes

Inode 9593212 ref count is 2, should be 1. Fix? yes

Unattached inode 9593213
Connect to /lost+found? yes

Inode 9593213 ref count is 2, should be 1. Fix? yes

Unattached inode 9593215
Connect to /lost+found? yes

Inode 9593215 ref count is 2, should be 1. Fix? yes

Unattached inode 9593218
Connect to /lost+found? yes

Inode 9593218 ref count is 2, should be 1. Fix? yes

Unattached inode 9593219
Connect to /lost+found? yes

Inode 9593219 ref count is 2, should be 1. Fix? yes

Unattached inode 9593220
Connect to /lost+found? yes

Inode 9593220 ref count is 2, should be 1. Fix? yes

Unattached inode 9593221
Connect to /lost+found? yes

Inode 9593221 ref count is 2, should be 1. Fix? yes

Unattached inode 9593223
Connect to /lost+found? yes

Inode 9593223 ref count is 2, should be 1. Fix? yes

Unattached inode 9593226
Connect to /lost+found? yes

Inode 9593226 ref count is 2, should be 1. Fix? yes

Unattached inode 9593228
Connect to /lost+found? yes

Inode 9593228 ref count is 2, should be 1. Fix? yes

Unattached inode 9593230
Connect to /lost+found? yes

Inode 9593230 ref count is 2, should be 1. Fix? yes

Unattached inode 9593231
Connect to /lost+found? yes

Inode 9593231 ref count is 2, should be 1. Fix? yes

Unattached inode 9593232
Connect to /lost+found? yes

Inode 9593232 ref count is 2, should be 1. Fix? yes

Unattached inode 9593233
Connect to /lost+found? yes

Inode 9593233 ref count is 2, should be 1. Fix? yes

Unattached inode 9593234
Connect to /lost+found? yes

Inode 9593234 ref count is 2, should be 1. Fix? yes

Unattached inode 9593235
Connect to /lost+found? yes

Inode 9593235 ref count is 2, should be 1. Fix? yes

Unattached inode 9593237
Connect to /lost+found? yes

Inode 9593237 ref count is 2, should be 1. Fix? yes

Unattached inode 9593238
Connect to /lost+found? yes

Inode 9593238 ref count is 2, should be 1. Fix? yes

Unattached inode 9593239
Connect to /lost+found? yes

Inode 9593239 ref count is 2, should be 1. Fix? yes

Unattached inode 9593240
Connect to /lost+found? yes

Inode 9593240 ref count is 2, should be 1. Fix? yes

Unattached inode 9593241
Connect to /lost+found? yes

Inode 9593241 ref count is 2, should be 1. Fix? yes

Unattached inode 9593242
Connect to /lost+found? yes

Inode 9593242 ref count is 2, should be 1. Fix? yes

Unattached inode 9593247
Connect to /lost+found? yes

Inode 9593247 ref count is 2, should be 1. Fix? yes

Pass 5: Checking group summary information
Block bitmap differences: +30213011 +(30239004--30239005) +(30239180--30239181) -(30239182--30239183) +30239192 +(38400256--38400260) +(38401395--38401399) +(38401775--38401805) +(38402789--38402790) +(38403252--38403670) +(38404047--38404095) +(38404424--38404431) +(38404433--38404509)
Fix? yes

Free blocks count wrong for group #1 (30160, counted=30158).
Fix? yes

Free blocks count wrong for group #922 (10481, counted=10477).
Fix? yes

Free blocks count wrong for group #1171 (25717, counted=25206).
Fix? yes

Free blocks count wrong for group #1172 (32508, counted=32354).
Fix? yes

Free blocks count wrong (38643579, counted=38642908).
Fix? yes

Inode bitmap differences: +7554382 +(9593194--9593248)
Fix? yes

Free inodes count wrong for group #922 (6777, counted=6776).
Fix? yes

Free inodes count wrong for group #1171 (7831, counted=7776).
Fix? yes

Free inodes count wrong (12037480, counted=12037424).
Fix? yes

/dev/sda7: ***** FILE SYSTEM WAS MODIFIED *****

45776 inodes used (0.38%)
2738 non-contiguous inodes (6.0%)
# of inodes with ind/dind/tind blocks: 33535/1763/0
9664539 blocks used (20.01%)
0 bad blocks
1 large file

43012 regular files
2716 directories
0 character device files
0 block device files
0 fifos
0 links
38 symbolic links (37 fast symbolic links)
1 socket
--------
45645 files

Obrázek uživatele yeti
Offline
Naposledy viděn: 12 let 6 měsíců zpět
Připojen: 09.10.2006 - 21:54
:o))

Doufám, že jsi sem ten výpis přepisoval ručně :o)))

Obrázek uživatele JirkaZ
Offline
Naposledy viděn: 6 let 5 měsíců zpět
Připojen: 17.10.2006 - 19:12
Trochu bych se zklidnil

ohledně tvrzení "Už mi dva dny nejde systém a nějaký úplný začátečník by skončil a vrátil se zpět k Windows"...

Před časem známý zápasil s opakovaně se hroutící/nespolehlivou RAM na dual bootu (nejspíš studený spoj na DPS paměti) a pokud si dobře vzpomínám, tak tohle ukrutné zacházení podstatně lépe ustálo SUSE, než WXP.

Jinak ale samozřejmě nekorektní vypnutí a případně i horší věci (problémy s HW) nepatří do standardního zacházení s PC. Jejich řešení může být klidně záležitost pro znalého admina. Pokud Vám chybí trpělivost a ochota se učit, tak zvažte, zda je pro Vás Linux to pravé. S Windows můžete zůstat u falešného dojmu, že to Velký bratr vyřešil za Vás (a pro Vás užitečně) ;-)

JirkaZ