Re: [newbie] Boot up Error Message
Andre Baron wrote: At 00:01 12/03/99 EST, you wrote: In a message dated 3/11/99 8:50:32 PM Pacific Standard Time, [EMAIL PROTECTED] writes: I would have imagined that /dev would cause problems (a simple cp in /dev will quickly fill your destination directory... that /dev/zero file just never ends...) i ment in windows Even in windows a copy of the whole HD doesn't work. It won't even let you copy any file which is used. And explorer is in use when you copy files. And many win dlls are in use... The solution to this is too boot into command line mode... 2 ways of doing this when windoze is starting up press F8 right at the beginning, or if you are in windows select shutdown then the ms-dos mode option. the command thn would be copy *.* /r d: I believe you can always do /help to figure out for sure. That doesn't really help if he wants to back up his Linux partitions, does it? For copying Linux installations between hard drives, here's what I'd try: 1) Mount the new hard drive. mkdir /mnt/new-drive mount -text2 /dev/hdb1 /mnt/new-drive 2) Change to the root directory and start the copy. cd / cp -ax / /mnt/new-drive 3) Edit /etc/lilo.conf to reflect the name of the new drive. If you'll still be BOOTING from the same drive, you'll just need to change the root= lines within the individual image= stanzas. If you're changing to a new boot drive also, modify the boot= line. 4) Run /sbin/lilo. Watch for errors. 5) Make a boot disk. 6) Shutdown, change the hardware around, and reboot. 7) If there are problems booting from the hard drive, use the boot floppy. It's been awhile since the original question in this thread, and truthfully, I've forgotten what the question even was! Could the original poster please post again? Thanks! -- Steve Philp [EMAIL PROTECTED]
Re: [newbie] Boot up Error Message
In a message dated 3/11/99 8:50:32 PM Pacific Standard Time, [EMAIL PROTECTED] writes: I would have imagined that /dev would cause problems (a simple cp in /dev will quickly fill your destination directory... that /dev/zero file just never ends...) i ment in windows
Re: [newbie] Boot up Error Message
At 00:01 12/03/99 EST, you wrote: In a message dated 3/11/99 8:50:32 PM Pacific Standard Time, [EMAIL PROTECTED] writes: I would have imagined that /dev would cause problems (a simple cp in /dev will quickly fill your destination directory... that /dev/zero file just never ends...) i ment in windows Even in windows a copy of the whole HD doesn't work. It won't even let you copy any file which is used. And explorer is in use when you copy files. And many win dlls are in use... - Rémi -
Re: [newbie] Boot up Error Message
I don't mean to be rude or question whether this really works. I don't have extra space, else I'd try it myself. Can anyone confirm that this works?? No it won't work. You are perfecly right with the problems in dev and the boot sector. What you have to do is use the dd command to make a physical copy of your whole device. The trick is I don't know the syntax :-) It must ressemble "dd if=/dev/hdx of=/dev/hdy ... options" where /dev/hdx is the drive you want to copy and /dev/hdy is the one you copy to. I know you have to specify more things to dd (block sizes,...) but you'll have to use man dd as I'm now at work (on an NT station :-( ) Ask help if you don't know some options... - Rémi -
Re: [newbie] Boot up Error Message
At 15:06 11/03/99 -0800, you wrote: A very good test to see if it's memory or bios-too-"optimized" related is to compile something big (a kernel for example) several times in a row. If your system succeeds to do so without any error, your system can be considered clean on that point and you can start to think about a new hard disk :-) Tell us how things turn out, well, I've recomplied 2.0.36 twice and 2.2.3 twice as well. All of them went through smoothly. Does that mean my system is clean? The disk change will be a major headache..:( Well at least your bios seems to be configured ok (not too optimized). You can read the Sig11 mini howto, they explain many problems that can occur with defective hardware, and ways to check it. One thing you could try, after you have made a copy of your settings :-), is to put your machine in "turtle" mode : change your bios settings to the slowest, disable all optimization,... (more wait states, slowest bus clock, disable 1st and 2nd level processor cache, disable hidden refresh, power management and the likes,... Real turtle mode) Then you try to start linux many times and see if the problem still appears Remember to do it in the conditions where you saw the error : if it only appeared the first time you started linux after a long off period, change the config to turtle mode, than let your machine sleep some times before you start it. (I say that because I had such a problem and it was a real beast to isolate : it only appeared when the machine was "cold") Be patient because a slow pc is... slow :-) - Rémi -
Re: [newbie] Boot up Error Message
At 00:01 12/03/99 EST, you wrote: In a message dated 3/11/99 8:50:32 PM Pacific Standard Time, [EMAIL PROTECTED] writes: I would have imagined that /dev would cause problems (a simple cp in /dev will quickly fill your destination directory... that /dev/zero file just never ends...) i ment in windows Even in windows a copy of the whole HD doesn't work. It won't even let you copy any file which is used. And explorer is in use when you copy files. And many win dlls are in use... The solution to this is too boot into command line mode... 2 ways of doing this when windoze is starting up press F8 right at the beginning, or if you are in windows select shutdown then the ms-dos mode option. the command thn would be copy *.* /r d: I believe you can always do /help to figure out for sure. Andre
Re: [newbie] Boot up Error Message
A very good test to see if it's memory or bios-too-"optimized" related is to compile something big (a kernel for example) several times in a row. If your system succeeds to do so without any error, your system can be considered clean on that point and you can start to think about a new hard disk :-) Tell us how things turn out, well, I've recomplied 2.0.36 twice and 2.2.3 twice as well. All of them went through smoothly. Does that mean my system is clean? The disk change will be a major headache..:(
Re: [newbie] Boot up Error Message
In a message dated 3/11/99 3:23:17 PM Pacific Standard Time, [EMAIL PROTECTED] writes: ? Maybe the disk is starting to go bad. no, but this happens with floppy boot as well. I think it is your RAM. I once had this problem as well. RAM seems to be causing a lot of this kind of intermittent problems. Also, one more thing you might want to try is changing the bios settings. I think you need to disable shadowing (although I don't think this would cause problems as such) and also any "memory holes" settings. You might want to try loading bios defaults (which is considered "safe" by the manufacturer - that is no unsafe performance boosts enabled) and then go around disabling those things above. (I once had such weirdness from wrong bios memory settings so it's worth a look) Thanks for all the help mail.:) I think I will try to nail down the problem first by: 1. check BIOS setting 2. reseat RAM 3. Change HD I really hate to change HD, as I have this system setup already. Can someone gimme a brief run though on how to transfer files from one HD to another without loosing all my settings and programs? I can have another HD hooked in there and copy everything over, but I don't know how will linux handle it. Any help in this transfer would be great!:) this is kind of a quick rig for ya if you have an internel CD-ROM drive take the cabels out of that and stick it into the hard drive while the computers off of course then drag the first hard drive icon to the second and let it copy the data then see if you can boot from that drive
Re: [newbie] Boot up Error Message
I have sucessfully used a program called Ghost to mirror hard drives. It is made by Symantec but I know Powerquest also makes one. Jeffrey Chen wrote: On Thu, 11 Mar 1999, Kuraiken wrote: Is this booting from a floppy? Maybe the disk is starting to go bad. no, but this happens with floppy boot as well. I think it is your RAM. I once had this problem as well. RAM seems to be causing a lot of this kind of intermittent problems. Also, one more thing you might want to try is changing the bios settings. I think you need to disable shadowing (although I don't think this would cause problems as such) and also any "memory holes" settings. You might want to try loading bios defaults (which is considered "safe" by the manufacturer - that is no unsafe performance boosts enabled) and then go around disabling those things above. (I once had such weirdness from wrong bios memory settings so it's worth a look) Thanks for all the help mail.:) I think I will try to nail down the problem first by: 1. check BIOS setting 2. reseat RAM 3. Change HD I really hate to change HD, as I have this system setup already. Can someone gimme a brief run though on how to transfer files from one HD to another without loosing all my settings and programs? I can have another HD hooked in there and copy everything over, but I don't know how will linux handle it. Any help in this transfer would be great!:) -JC -- Jerry Dean 5919 E.Pima St. Tucson, AZ 85712 520-296-7176
Re: [newbie] Boot up Error Message
[EMAIL PROTECTED] wrote: then drag the first hard drive icon to the second and let it copy the data Does this actually work?! I would have imagined that /dev would cause problems (a simple cp in /dev will quickly fill your destination directory... that /dev/zero file just never ends...) And you don't want to copy /proc over, since it's a fake filesystem to begin with. then see if you can boot from that drive Unless it's doing a binary copy from drive to drive, he's going to be missing the boot sector, isn't he? I don't mean to be rude or question whether this really works. I don't have extra space, else I'd try it myself. Can anyone confirm that this works?? -- Steve Philp [EMAIL PROTECTED]
[newbie] Boot up Error Message
Hi Guys, I am having a strange problem. When I boot into Linux, I get a "CRC Error -- System Halted" error when vmlinuz is being loaded. The strange thing is that it only happens sometimes; if I reset the machine 2 or 3 times in a roll, the kernel boots just fine. No error once the kernel got rolling, and no problem running anything including the beautiful KDE. I tried using several different kernel and even compiled the latest 2.2.3 kernel just to test, but the same phenomenon keep happening. What might be the cause here? Could this be hardware related? Here's my setup: Cyrix P150+ 128MB RAM 1.6 GB IDE HD IDE CDROM Logitech Mouse Matrox Mystique and I am running Linux Mandrake 5.3 with 2.2.3 kernel. Please note that this happens with the 2.0.36 kernel that came with mandrake as well. I can live with this error but it is annoying as hell. Any help is greatly appreciated! -JC
Re: [newbie] Boot up Error Message
On Wed, 10 Mar 1999, you wrote: Hi Guys, I am having a strange problem. When I boot into Linux, I get a "CRC Error -- System Halted" error when vmlinuz is being loaded. The strange thing is that it only happens sometimes; if I reset the machine 2 or 3 times in a roll, the kernel boots just fine. No error once the kernel got rolling, and no problem running anything including the beautiful KDE. I tried using several different kernel and even compiled the latest 2.2.3 kernel just to test, but the same phenomenon keep happening. What might be the cause here? Could this be hardware related? Here's my setup: Cyrix P150+ 128MB RAM 1.6 GB IDE HD IDE CDROM Logitech Mouse Matrox Mystique and I am running Linux Mandrake 5.3 with 2.2.3 kernel. Please note that this happens with the 2.0.36 kernel that came with mandrake as well. I can live with this error but it is annoying as hell. Any help is greatly appreciated! -JC I was getting the same error, the problem that caused it in my case was a failing HD of the boot section, I fdisked /mbr and did about three installs of Mandrake before I figured it out. I replaced the drive and have not had a problem since.
