From: Daniel47@teranews.com   
      
   Daniel47@teranews.com wrote:   
   > Daniel47@teranews.com wrote:   
   >> On this HP 6730b Laptop, I multi-boot Win7/MD2009.1/MD2010.1/MD2012/MG2   
   >> and have my Home in a separate mount (SD8) so that all the linux's can   
   >> use it!   
   >>   
   >> By default it boots into MD2009.1 but a couple of days ago, MD2009.1   
   >> died (which is why I'm posting this using Win7). Today I finally have   
   >> time to check things out. Sure enough, MD2009.1 wouldn't boot, so I   
   >> re-installed it, but it still would not boot, nor any of the Linux's.   
   >>   
   >> This time, though, I actually looked at what the system was telling me!!   
   >> Lots of lines of no real interest, I hope, then.....   
   >>   
   >> (from the screen)   
   >> Checking filesystem   
   >> /dev/sd8 contains a file system with errors check forced (gets to approx   
   >> 32%)   
   >> Inode that were part of a corrupted orphan linked list found.   
   >> /dev/sd8: UNEXPECTED INCONSISTENCIES; RUN fsck MANUALLY   
   >> (i.e. without -a and -p options)   
   >>   
   >> I've tried booting to the MD2009.1 DVD, but I cannot see anything there   
   >> that will fix my Home mount. I've tried to run "fsck" but I expect I'm   
   >> not getting the correct syntact.   
   >>   
   >> Can anyone give me a workable plan to help me re-claim my Home mount??   
   >> (Treat me gentle!!)   
   >>   
   >> TIA   
   >>   
   >> Daniel   
   >   
   > O.K., reading one of the threads in the a.o.l.mageia group has given me   
   > the format of the fsck command, so I'll use my MD2009.1 DVD to get me to   
   > a terminal, then I'll issue fsck /dev/sa8 and see if that fixes things!!   
   >   
   > Daniel   
      
   All better ... at least for now!   
      
   Was a bit worried when I got to a terminal and entered the "fsck   
   /dev/sa8" and nothing happened ... well, nothing good.   
      
   I looked around for other things to try, but, finding nothing, entered   
   fsck /dev/sa8 again and still nothing happened. Then I looked at what I   
   had entered and figured it might work better if I typed fsck /dev/sda8   
   (note the d) an away it went.   
      
   A couple of Block Bitmap Differences, a couple of incorrect Freeblock   
   Counts, all fixed and I'm away.   
      
   Just to check, I then entered fsck /dev/sda8 again, and it came through   
   without a problem.   
      
   Now, just in case the HD is dying, I'd better dd this drive to my spare,   
   as suggested by others.   
      
   Daniel   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)