Hard Drive Lock during InstallForum: HD Install Topic: Hard Drive Lock during Install started by: Klashe Posted by Klashe on Feb. 20 2004,21:27
Okay, I'm on a IBM 560X Lappy with only floppy. 233Mhz MMX, 4 gig HD, 32 Megs of RAM. HD partitioned in 3 : /dev/hda1 Ext2 - 3.5 Gigs for apps/work directories etc (this is set to boot), /dev/hda2 Ext2 - 300 Megs (for DSL Boot), /dev/hda3 100 Megs for Linux Swap. I boot with the floppy fine. I get into knoppix (stored on the /dev/hda1), and then I do a DSL-hdinstall.... I say "Yes I have a partition for DSL" "/dev/hda2" "yes, wipe it out" It says "Okay, it'll be two to 10 minutes." It shows the little ascii timer...goes (working on HD) for about a minute, and then stops. No activity on the Hard Drive LED, but the ascii timer keeps going until i mouse the mouse or type on the keyboard, and then it freezes. I let it run the entire night, but its still frozen in the morning. I tried booting to runlevel 2 (i.e. boot: knoppix 2 ) but the same problem occurs. Couple of things that might be wrong but I'm not sure: does /dev/hda2 need to be set as boot? right now /dev/hda1 is. I'm not sure that that's my CURRENT problem, but I think it might be a problem in the future. My linux swap might not be set correctly. cfdisk recognizes it as a linux swap, and i ran mkswap on it, but I'm not sure if it took. Anything else I need to do to get it to recognize it as a swap? Any ideas? I know the disclaimer that DSL-hdinstall is a work in progress, but I'd really like some guidance. Posted by donkey wrestler on Feb. 20 2004,22:00
klashe, i have the same freezing problems you are having. But i have a pentium/75 mhz with 16 mb ram, 9 gb hdd. I thought my problems were related to my low memory, but know im not so sure...anyway, the only help i can provide sbout swap stuff is to check your swap usage: cat /proc/swaps and cat /proc/meminfo im pretty sure that if cfdisk recognizes the id as swap, then the kernel will recognize as such on boot, but those commands will tell you little more. JP also, i saw a thread in this topic that said the disk you are installing to should not be mounted prior to running the dsl-hdinstall script, but i cant find it now. Posted by Klashe on Feb. 21 2004,06:18
Well, just trying to copy all the files over to the partition (so /dev/hda1 to /dev/hda2 ) with just the same copy command as in the dsl-hdinstall script "cp -va * /dev/hda2" produces the freeze. It locks up after a random amount of files. I tried it twice and once it locked up on a file in X11R6 and another time it locked up on a /lib/ shared object.Perhaps the hard drive doesn't have enough to keep up with the amount of writes. So I'm going to write a script that copies all the files over and then sleeps between each file. hopefully this will stop the freezes. I'll let you guys know. And if you think that this isn't the problem, please let me know. Thanks! Posted by Klashe on Feb. 24 2004,04:10
Alright, that didn't work either. It still frickin locked on me.Anyone have any ideas? Posted by alloydog on Oct. 06 2004,18:36
I get the same thing when I try to install to the harddrive as well.I don`t think it`s a memory problem, because I have 320 MB of the stuff ! It for DSL/Knoppix 2.78 (kernel 2.4.26) and the PC specs are: Processor: AMD K6-2 450 MHz Mainboard: MSI MS-5169 ver2.1, ver 3.1 BIOS RAM: 320 MB PC100 (2x 128 + 1 x64) Harddrive: see below: 1. Maxtor 80 GB HDD partitioned to: -- hda1: 1 GB Linux -- hda2: 1 GB Swap -- hda3: 32 GB Linux -- hda5: 32 GB Linux -- hda6: 14 GB LInux 2. Seagate 1.2 GB HDD partitioned to: -- hda1: 1 GB Linux -- hda2: 282 MB Swap I first thought the manboard was having a problem witht he large harddrive, as the BIOS cannot read it properly. (Say`s it`s a 65 GB disc) but after I tried an old HD, if got exactly the same problem ! The install gets to "Now th eroot filesystem is filled with data..." then a string of error messages, including: hda: drive not ready for commands hda: lost interrupt ide0: reset: success which repeats about three times before another screen load of gibberish (well, to me it is!!) ending in: In interrupt handler - not syncing The system then completely locks up, with only the CAPS LOCK keyboard LED, and the one to the right of it, flashing. Even Ctrl/Alt/Del do not work. I have tried running the install from the Xterminal window, exiting the window manger and X altogether, and starting DSL from runlevel 2 from the begining. I have tried runnigg DSL from the CDROM and from RAM (booted with `toram` switch). a quick search on the net using a couple of the error messages seems to suggest a kernek bug, or horror of horrors a knkackered mainboard. I doubt it is the hard drive because I have tried two totally differetn drives, with one made on the 29th of May 2004! At the moment, I`m running DSL from the liveCD loaded to RAM, but would really like to get on with case modding and bolt it all together! Posted by alloydog on Oct. 08 2004,07:18
Update:I had a play around with the hardware. I used a different CD drive - no change. then I putboth the HD and the CDROM drive on the same IDE bus (IDE0) - this time it got past the "Now the root filesystem is filled with data..." bit, print a sucess message in green, then... 'Segmentation error' printed twice, then loads of alarming looking messages, too fast to write down ! I even tried it with both the HD & CD drives on IDE1 & IDE0 disabled. It booted a bit slower, but I got the same problem. I'm now thinking it is not a DSL problem, rather a DSL reaction to another problem as I tried to install VectorLInux 4.3 from CD, but get the message that a zip file is corrupted (downlaoded & burnt the ios image twice & checked the md5 sum, all OK) VectorLinux 3.2 would not even boot from the floppy. The only OS I managed to install was < FreeDOS >, but for some reason that did not detect the CDROM drive. I tried it (DSL install) with one of the RAM modules removed (64MB), but still the same problem... Posted by AwPhuch on Oct. 08 2004,15:04
If you are worried that its your hardware I recommend a utility cd to check all that < ULTIMATE BOOT CD >test your ram and your hd and all that, double check your BIOS as well (disable any com ports you dont plan on using) Perhaps its just a BIOS missmatch or botchup...or maybe your ram is failing... Are you trying standard or enhanced install? Brian AwPhuch Posted by alloydog on Oct. 10 2004,06:55
That looks good, thanks for the link ! I had already checked the HD with Maxtors MaxBlast 3, and every thing checked out OK I tried to run their PowerMax utility which is supposed to do something to BIOSes that cannot handle large HDs, but on unpacking, it failed with the message "Too deep nesting"...:-? But since I have th esame problems with three different HDs, I doubt that is the problem. Hopefully some of the other tools listed will help out. More later... |