[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [TEKNIK] Sluk modemet og få kernel panik!



On Sat, Apr 29, 2000 at 11:21:00 +0200, Thomas Bartvig wrote:
......

> Jeg har så siden været inde med en rescue disk for at 
> lokalisere og rette fejlen, og det er her jeg har brug 
> for lidt hjælp. 
> Jeg har kørt e2fsck på de linux-partitioner jeg har, men
> da jeg kørte e2fsck på /dev/hda5 (mountes som /) fik jeg
> at vide, at superblocken var corrupt. Hvordan retter jeg 
> det? Jeg prøvede, som e2fsck foreslog, at køre kommandoen 
> e2fsck -b 8193 /dev/hda5, men det resulterer bare i samme
> fejlmeddelelse.

Er du sikker på 8193, det er ikke 8192 ?

> Og hvis der er nogen der kan forklare hvordan i al verden
> modemet (apmd?) kan få disken til gå agurk på den måde, så 
> vil jeg meget gerne høre om det.

Måske strøm-spikes, manglende jording og lignende ?

....
> # ifup ppp0	<tænder modem>
> apmd[255]: Standby Resume (-1% unknown) AC Power
> 
> <læser post, mm.>
> # ifdown ppp0	<slukker modem>
> # <tænder modem> <slukker modem> hda: lost interrupt
> hda: status error: status=0x50 {DriveReady SeekComplete}
> hda: no DRQ after issuing write

IDE driver/harsdware mistede interrupt i forbindelse med modem-sluk,
måske for interrupt rutinen til serielport/modem havde fejl
eller måske noget hardware-powerdown der blev sat i værk via
powersave funktioner i bios ?


Du kunne jo forsøge at køre "badblocks" i read-mode på disken,
og få checket fejlene.
(husk "badblocks -w ...." i write mode sletter indhold!!)


-- 
mvh Frank Damgaard  | http://home3.inet.tele.dk/frda/



 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 21:38 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *