RE: [expert] kernel panic, can not mount root fs

2001-03-10 Thread Daryl Johnson

One bizarre option you might try - if you just want to recover data and it
is vital - try finding an Amiga, plug your hd in to it and run... oh drat my
mind is a blank, there is a file system on aminet that allows you to mount
unix/linux partitions and read from them.  Last time I used this 8 months
ago there was another version that reads AND writes.

Does anyone know what the file system is that I'm thinking of?  I'll check
my old notes and see if I still have the name somewhere.

Just a suggestion...

Daryl Johnson
Proplan Associates

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Elice Wu
> Sent: 10 March 2001 06:22
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kernel panic, can not mount root fs
>
>
> (I'm not saying that you necessarily have to re-install, but I have no
> further suggestions as to how to recover your linux data)
>
> There's no need to add any extra partitions between Windows and Linux
> partitions. You just need to make sure that when you do your install,
> that you install Windows first. It is not necessary to partition your
> drive first, but you can. I've done it both ways: partitioning before,
> and after windows install, and both were successful.
>
> After you do the install, make sure you've defragged the disk in
> windows, and then you can partition during your linux install.
>
> I strongly recommend, after you install linux, that you reboot back
> into windows to make sure that it has properly recognised the space you
> allocated to it in its partition. That's the only problem with Windows,
> is that it may not recognise the partitions. It took over a year before
> windows would recognise the new partitions when it happened to me. go
> figure.
>
>
> > well i agree windows has screwed up your partitions,
> > you may be able to use partition commander to repair the damage, but
> as for salvaging your data, most likely only windows data can be
> salvaged, im unsure how to salvage data from linux partitions, the
> cause seems to be that when windows was writing to a partition it
> misread the data table and over extended the partition it was writing
> to ontop of another partition which happens to be your /root partition.
> > maybe you should add a small extended partition between your linux
> and windows partitions. that way you may have a small buffer of
> protection against windows write errors like the one you encountered,
> another thought is using vmware, however if you intend to log online
> with windows using a virtual machine such as vmware would be a bad idea.
> >
> > have fun!
> > [EMAIL PROTECTED] wrote:
> > >
> > > Sounds to me like Windows didnt recognise your partitions properly,
> and
> > > installed over the root partition of Linux.
> > >
> > > I've had this happen to me before. The only solution that I found
> was to
> > > re-install the whole lot, both OS's, making sure that windows
> recognised
> > > the partitions that were allocated to it.
> > >
> > >
> > >
>
>
>  --
>   Elice Wu | Telphone: +61 2 8219 5400|  _--_|\
>   241 Commonwealth St  | Fascimile: +61 2 8219 5499   | /  \
>   Surry Hills NSW 2010 | Extension: 465   | \_.--._*
>   Australia| Web: http://www.viator.com   |   v
>
>
>
>





Re: [expert] kernel panic, can not mount root fs

2001-03-09 Thread Elice Wu

(I'm not saying that you necessarily have to re-install, but I have no 
further suggestions as to how to recover your linux data)

There's no need to add any extra partitions between Windows and Linux 
partitions. You just need to make sure that when you do your install, 
that you install Windows first. It is not necessary to partition your 
drive first, but you can. I've done it both ways: partitioning before, 
and after windows install, and both were successful.

After you do the install, make sure you've defragged the disk in 
windows, and then you can partition during your linux install.

I strongly recommend, after you install linux, that you reboot back 
into windows to make sure that it has properly recognised the space you 
allocated to it in its partition. That's the only problem with Windows, 
is that it may not recognise the partitions. It took over a year before 
windows would recognise the new partitions when it happened to me. go 
figure.


> well i agree windows has screwed up your partitions,
> you may be able to use partition commander to repair the damage, but 
as for salvaging your data, most likely only windows data can be 
salvaged, im unsure how to salvage data from linux partitions, the 
cause seems to be that when windows was writing to a partition it 
misread the data table and over extended the partition it was writing 
to ontop of another partition which happens to be your /root partition.
> maybe you should add a small extended partition between your linux 
and windows partitions. that way you may have a small buffer of 
protection against windows write errors like the one you encountered, 
another thought is using vmware, however if you intend to log online 
with windows using a virtual machine such as vmware would be a bad idea.
> 
> have fun! 
> [EMAIL PROTECTED] wrote:
> >
> > Sounds to me like Windows didnt recognise your partitions properly, 
and
> > installed over the root partition of Linux.
> > 
> > I've had this happen to me before. The only solution that I found 
was to
> > re-install the whole lot, both OS's, making sure that windows 
recognised
> > the partitions that were allocated to it.
> > 
> > 
> > 


 -- 
  Elice Wu | Telphone: +61 2 8219 5400|  _--_|\
  241 Commonwealth St  | Fascimile: +61 2 8219 5499   | /  \
  Surry Hills NSW 2010 | Extension: 465   | \_.--._*
  Australia| Web: http://www.viator.com   |   v






Re: [expert] kernel panic, can not mount root fs

2001-03-09 Thread Gerry

Of course # of primary partitions is not os-dependent. What i'm talking
about is that windows screw up 2nd, 3rd and 4th primary partitions if it
finds any.

> What are you talking about.
> Windows has nothing to do with the # of primary partitions which can be
> used.
> Any drive can contain up to 4 primary partitions.
> The 1 limitation is for logical (extended) partitions and this also is
> not dependent
> upon the OS being used.
>
>Charles  (-:
>
> Forever never goes beyond tomorrow.




RE: [expert] kernel panic, can not mount root fs

2001-03-09 Thread Charles A Edwards




> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Gerry
> Sent: Friday, March 09, 2001 9:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kernel panic, can not mount root fs
>
>

>
> The problem could also be that you have more than one primary
> partition.
> Windows only supports one (visible) primary partition, all
> the rest needs to
> be extended partitions, if not they're toast.


What are you talking about.
Windows has nothing to do with the # of primary partitions which can be
used.
Any drive can contain up to 4 primary partitions.
The 1 limitation is for logical (extended) partitions and this also is not
dependent
upon the OS being used.

   Charles  (-:

Forever never goes beyond tomorrow.





Re: [expert] kernel panic, can not mount root fs

2001-03-09 Thread mwinold

well i agree windows has screwed up your partitions,
you may be able to use partition commander to repair the damage, but as for salvaging 
your data, most likely only windows data can be salvaged, im unsure how to salvage 
data from linux partitions, the cause seems to be that when windows was writing to a 
partition it misread the data table and over extended the partition it was writing to 
ontop of another partition which happens to be your /root partition.
maybe you should add a small extended partition between your linux and windows 
partitions. that way you may have a small buffer of protection against windows write 
errors like the one you encountered, another thought is using vmware, however if you 
intend to log online with windows using a virtual machine such as vmware would be a 
bad idea.

have fun! 
[EMAIL PROTECTED] wrote:
>
> Sounds to me like Windows didnt recognise your partitions properly, and
> installed over the root partition of Linux.
> 
> I've had this happen to me before. The only solution that I found was to
> re-install the whole lot, both OS's, making sure that windows recognised
> the partitions that were allocated to it.
> 
> 
> 
> "Ingo P. Korndoerfer" wrote:
> > 
> > dear mandrake community,
> > 
> > i am utterly at loss with my laptop :
> > 
> > - prehistory : installed some new softare on my windows partition.
> >   (yeah, yeah .. i don't want to hear about it,
> >    but the linux version of the program
> >    gave me a segmentation fault)
> >    maybe the disk got a little too full there. not sure.
> >    abandonned this, logged out.
> > 
> > - problem : can't get into my linux partition now anymore :
> > 
> >    partition check hda1 hda2 <>
> >    VFS : Cannot open root device 03:05
> >    Kernel Panic : VFS : Unable to mount root fs on 03:05
> > 
> > what could be the problem ?
> > 
> > - all the device drivers should be there since i have been working
> >    with this laptop
> >    under linux for some three months now.
> > - the mbr should be ok, since the boot process starts but gets hung later.
> > 
> > - partition table ? i figured out how to get into rescue mode.
> >   here is the output of gpart -vvd /dev/hda1
> >   doesn't that look unsuspicious ? i have no clue.
> > 
> > dev(/dev/hda1) mss(512) chs(202/240/63)(LBA) #s(3054240) size(1491mb)
> > Primary partition(1)
> >    type: 104(0x68)(UNKNOWN)
> >    size: 904228mb #s(1851859059) s(1936028272-3787887330)
> >    chs:  (116/100/32)-(288/101/46)d (128044/47/32)-(250521/155/46)r
> >    hex:  6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E
> > 
> > Primary partition(2)
> >    type: 121(0x79)(UNKNOWN)
> >    size: 263172mb #s(538976288) s(1330184192-1869160479)
> >    chs:  (357/32/43)-(0/13/10)d (87975/34/51)-(123621/173/61)r
> >    hex:  79 20 6B 65 79 0D 0A 00 00 00 49 4F 20 20 20 20
> > 
> > Primary partition(3)
> >    type: 083(0x53)(UNKNOWN)
> >    size: 682794mb #s(1398362912) s(538989391-1937352302)
> >    chs:  (345/32/19)-(324/77/19)d (35647/107/11)-(128131/183/54)r
> >    hex:  20 20 53 59 53 4D 53 44 4F 53 20 20 20 53 59 53
> > 
> > Primary partition(4)
> >    type: 073(0x49)(UNKNOWN)
> >    size: 10mb #s(21337) s(1394627663-1394648999)
> >    chs:  (87/1/0)-(335/78/2)d (92237/67/3)-(92238/165/45)r
> >    hex:  7E 01 00 57 49 4E 42 4F 4F 54 20 53 59 53 00 00
> > 
> > the output of the same for /dev/hda is more suspicious :
> > 
> > ** Error: invalid extended ptbl found at sector(3069360).
> > 
> > dev(/dev/hda) mss(512) chs(776/240/63)(LBA) #s(11733120) size(5729mb)
> > Primary partition(1)
> >    type: 011(0x0B)(DOS or Windows 95 with 32 bit FAT) (BOOT)
> >    size: 1498mb #s(3069297) s(63-3069359)
> >    chs:  (0/1/1)-(202/239/63)d (0/1/1)-(202/239/63)r
> >    hex:  80 01 01 00 0B EF 3F CA 3F 00 00 00 71 D5 2E 00
> > 
> > Primary partition(2)
> >    type: 133(0x85)(Extended Linux)
> >    size: 4230mb #s(8663760) s(3069360-11733119)
> >    chs:  (203/0/1)-(775/239/63)d (203/0/1)-(775/239/63)r
> >    hex:  00 00 01 CB 85 EF FF 07 B0 D5 2E 00 D0 32 84 00
> > 
> >    Logical partition
> >       type: 036(0x24)(NEC MS-DOS 3.x)
> >       size: 953967mb #s(1953724755) s(945901090-2899625844)
> >       chs:  (370/83/52)-(370/113/49)d (62559/143/2)-(191774/47/4)r
> >       hex:  68 53 74 72 24 71 71 72 72 78 32 38 53 79 73 74
> > 
> > Primary partition(3)
> >    type: 000(0x00)(unused)
> >    size: 0mb #s(0) s(0-0)
> >    chs:  (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
> >    hex:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 
> > Primary partition(4)
> >    type: 000(0x00)(unused)
> >    size: 0mb #s(0) s(0-0)
> >    chs:  (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
> >    hex:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 
> > do i have hopes set to high, when i think everyhing should be still there ?
> > how can i mount my linux partitioon again ? how can i fix this ?
> > i'd really like to rescue my data.
> > 
> > 1000 thanks in advance for all hints !
> > 
> >                            ingo
> > 
> > --
> >

Re: [expert] kernel panic, can not mount root fs

2001-03-09 Thread Gerry

[Elice Wu]
> Sounds to me like Windows didnt recognise your partitions properly, and
> installed over the root partition of Linux.
>
> I've had this happen to me before. The only solution that I found was to
> re-install the whole lot, both OS's, making sure that windows recognised
> the partitions that were allocated to it.

The problem could also be that you have more than one primary partition. 
Windows only supports one (visible) primary partition, all the rest needs to 
be extended partitions, if not they're toast.




Re: [expert] kernel panic, can not mount root fs

2001-03-08 Thread Elice Wu

Sounds to me like Windows didnt recognise your partitions properly, and
installed over the root partition of Linux.

I've had this happen to me before. The only solution that I found was to
re-install the whole lot, both OS's, making sure that windows recognised
the partitions that were allocated to it.



"Ingo P. Korndoerfer" wrote:
> 
> dear mandrake community,
> 
> i am utterly at loss with my laptop :
> 
> - prehistory : installed some new softare on my windows partition.
>   (yeah, yeah .. i don't want to hear about it,
>but the linux version of the program
>gave me a segmentation fault)
>maybe the disk got a little too full there. not sure.
>abandonned this, logged out.
> 
> - problem : can't get into my linux partition now anymore :
> 
>partition check hda1 hda2 <>
>VFS : Cannot open root device 03:05
>Kernel Panic : VFS : Unable to mount root fs on 03:05
> 
> what could be the problem ?
> 
> - all the device drivers should be there since i have been working
>with this laptop
>under linux for some three months now.
> - the mbr should be ok, since the boot process starts but gets hung later.
> 
> - partition table ? i figured out how to get into rescue mode.
>   here is the output of gpart -vvd /dev/hda1
>   doesn't that look unsuspicious ? i have no clue.
> 
> dev(/dev/hda1) mss(512) chs(202/240/63)(LBA) #s(3054240) size(1491mb)
> Primary partition(1)
>type: 104(0x68)(UNKNOWN)
>size: 904228mb #s(1851859059) s(1936028272-3787887330)
>chs:  (116/100/32)-(288/101/46)d (128044/47/32)-(250521/155/46)r
>hex:  6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E
> 
> Primary partition(2)
>type: 121(0x79)(UNKNOWN)
>size: 263172mb #s(538976288) s(1330184192-1869160479)
>chs:  (357/32/43)-(0/13/10)d (87975/34/51)-(123621/173/61)r
>hex:  79 20 6B 65 79 0D 0A 00 00 00 49 4F 20 20 20 20
> 
> Primary partition(3)
>type: 083(0x53)(UNKNOWN)
>size: 682794mb #s(1398362912) s(538989391-1937352302)
>chs:  (345/32/19)-(324/77/19)d (35647/107/11)-(128131/183/54)r
>hex:  20 20 53 59 53 4D 53 44 4F 53 20 20 20 53 59 53
> 
> Primary partition(4)
>type: 073(0x49)(UNKNOWN)
>size: 10mb #s(21337) s(1394627663-1394648999)
>chs:  (87/1/0)-(335/78/2)d (92237/67/3)-(92238/165/45)r
>hex:  7E 01 00 57 49 4E 42 4F 4F 54 20 53 59 53 00 00
> 
> the output of the same for /dev/hda is more suspicious :
> 
> ** Error: invalid extended ptbl found at sector(3069360).
> 
> dev(/dev/hda) mss(512) chs(776/240/63)(LBA) #s(11733120) size(5729mb)
> Primary partition(1)
>type: 011(0x0B)(DOS or Windows 95 with 32 bit FAT) (BOOT)
>size: 1498mb #s(3069297) s(63-3069359)
>chs:  (0/1/1)-(202/239/63)d (0/1/1)-(202/239/63)r
>hex:  80 01 01 00 0B EF 3F CA 3F 00 00 00 71 D5 2E 00
> 
> Primary partition(2)
>type: 133(0x85)(Extended Linux)
>size: 4230mb #s(8663760) s(3069360-11733119)
>chs:  (203/0/1)-(775/239/63)d (203/0/1)-(775/239/63)r
>hex:  00 00 01 CB 85 EF FF 07 B0 D5 2E 00 D0 32 84 00
> 
>Logical partition
>   type: 036(0x24)(NEC MS-DOS 3.x)
>   size: 953967mb #s(1953724755) s(945901090-2899625844)
>   chs:  (370/83/52)-(370/113/49)d (62559/143/2)-(191774/47/4)r
>   hex:  68 53 74 72 24 71 71 72 72 78 32 38 53 79 73 74
> 
> Primary partition(3)
>type: 000(0x00)(unused)
>size: 0mb #s(0) s(0-0)
>chs:  (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
>hex:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> Primary partition(4)
>type: 000(0x00)(unused)
>size: 0mb #s(0) s(0-0)
>chs:  (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
>hex:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> do i have hopes set to high, when i think everyhing should be still there ?
> how can i mount my linux partitioon again ? how can i fix this ?
> i'd really like to rescue my data.
> 
> 1000 thanks in advance for all hints !
> 
>ingo
> 
> --
> 
> 
> 
> Ingo P. Korndoerfer
> Dept. of Biological Chemistry
> Technische Universitaet Muenchen
> An der Saatzucht 5
> D-85350 Freising Weihenstephan
> 
> phone  : +49 (8161) 71-3255 (desk)
>  +49 (8161) 71-5167 (computing)
> fax: +49 (8161) 71-4352
> e-mail : [EMAIL PROTECTED]
> 

-- 
 Elice Wu | Telphone: +61 2 8219 5400|  _--_|\
 241 Commonwealth St  | Fascimile: +61 2 8219 5499   | /  \
 Surry Hills NSW 2010 | Extension: 465   | \_.--._*
 Australia| Web: http://www.viator.com   |   v