This is a discussion on Can't mount root partition in Slack 10.1 setup....bogus sector sizes within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hello, all.. Have a strange problem that I'm sure is something stupid on my part, but not quite sure ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, all.. Have a strange problem that I'm sure is something stupid on my part, but not quite sure how to fix it. Now, I'll caveat this by volunteering the fact that it's been a while since I've done a Linux install, hence the "something stupid" caveat. I am installing Slack 10.1 into an MS Virtual PC setup. I installed from the ISO image, and installation appeared to be going entirely normally, right down to net configuation, extra packages, you name it, very vanilla and uneventful install. Setup tells me it done and happy. When I tried to reboot after the install, the kernel ends up in a panic abort because it cannot mount the root filesystem (after a couple of other efforts failed with "bogus sector sizes", which didn't bother me because they were attempts at FAT file systems, which the root file system isn't). I take a look at fdisk and it shows a single /dev/hda1 partition for the entire drive, type ext2. I thought perhaps something had corrupted the install, so I rebooted into the ISO image installer, logged in, and was able to manually mount the file system with no problem, and the files I looked through looked normal to me. Sorry not to have copies of fdisk output but I'm away from the box at the moment. This is not an absolutely critical problem as it's a new install, so if worse comes to worse, I can just blow it away and start over. But I would like to know what I did wrong.... Thanks for ideas, David ps please reply to group; email here is dead. |
| |||
| intrepid_dw@hotmail.com wrote: > Hello, all.. > > Have a strange problem that I'm sure is something stupid on my part, > but not quite sure how to fix it. Now, I'll caveat this by volunteering > the fact that it's been a while since I've done a Linux install, hence > the "something stupid" caveat. > > I am installing Slack 10.1 into an MS Virtual PC setup. <snip> that may be the problem try a non-virtual installation |
| |||
| On Sat, 03 Sep 2005 03:55:20 -0500, philo wrote: > intrepid_dw@hotmail.com wrote: > >> Hello, all.. >> >> Have a strange problem that I'm sure is something stupid on my part, >> but not quite sure how to fix it. Now, I'll caveat this by volunteering >> the fact that it's been a while since I've done a Linux install, hence >> the "something stupid" caveat. >> >> I am installing Slack 10.1 into an MS Virtual PC setup. > > <snip> > > that may be the problem > > try a non-virtual installation If this is indeed the case (and I cant think what else it could be) try a different virtualiser. I have used slackware on vmware without a problem. ion |
| ||||
| Thanks, all. Turns out I had missed a step when creating my partitions. I blew the existing partisions away, started over, made sure I dotted all my i's and crossed all my t's when I built the partitions, reinstalled, and everything worked perfectly. Slack 10.1 works just fine under MS VPC. I appreciate the help nonetheless. -David ion wrote: > On Sat, 03 Sep 2005 03:55:20 -0500, philo wrote: > > > intrepid_dw@hotmail.com wrote: > > > >> Hello, all.. > >> > >> Have a strange problem that I'm sure is something stupid on my part, > >> but not quite sure how to fix it. Now, I'll caveat this by volunteering > >> the fact that it's been a while since I've done a Linux install, hence > >> the "something stupid" caveat. > >> > >> I am installing Slack 10.1 into an MS Virtual PC setup. > > > > <snip> > > > > that may be the problem > > > > try a non-virtual installation > > If this is indeed the case (and I cant think what else it could be) try a > different virtualiser. I have used slackware on vmware without a problem. > > ion |