Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by homey If Linux was on the Master drive before, the Slave drive should have no effect on that unless the drive jumpers are set wrong.
Thanks homey !
My slave drive works ok when running Windows.
How do I go on making my Linux start up again after my harddisk replace?
I assume there is a Linux boot log somewhere. Could it be of any help reading this? I have access to Linux files from whithin Windows using an explorer program reading linux files.
Linux is on your master drive, windows is on the slave.
You can boot windows now from the slave drive. That means that you must have re-installed windows after you installed Linux. If so then windows has over-written your Linux boot loader, either grub or lilo.
Re-install grub or lilo. You will have to be root. You can do that form a recovery disk or a Linux live CD like knoppix.
Originally posted by teckk "Linux is on your master drive, windows is on the slave.
Thanks teckk !
I did not express myself clearly. Both Windows and Linux is on my master drive. I mentioned Windows to make clear there is no hardware problem on my system.
Quote:
Originally posted by teckk ...you must have re-installed windows...
No, I haven't. Linux refuse to start up after I replaced my slave harddisk. And, I forgot to mention, I also have installed a new ISA-card whith four new USB-ports.
So, to conclude. I have no hardware problem. Windows works ok on the system.
Here is the message displayed when Linux startup halts:
resuming from /dev/hda6
Resuming from device hda6
Kernel panic: Resume Machine: Unable to find suspended-data (-misspelled?
This is all I can see, and I don't understand what it means.
It seems that somehow you lost the hda6 extended partition, which is used for suspending the system to disk (hibernate).
When you are at the lilo or grub screen, press ESC to get the lilo/grub prompt. There, enter the name of your default entry (usually "linux") followed by the "noresume noresume2" parameters:
Code:
LILO> linux noresume noresume2
When you have booted, give the output of the "mount" command (with no parameters), and the contents of /etc/fstab. And if you know how (eg: with fdisk), give the exact layout of your partitions.
[thort@dhcppc0 thort]$ mount
/dev/ide/host0/bus0/target0/lun0/part3 on / type ext3 (rw)
none on /proc type proc (rw)
none on /proc/bus/usb type usbfs (rw)
none on /dev type devfs (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,mode=0620)
/dev/ide/host0/bus0/target0/lun0/part5 on /home type ext3 (rw)
none on /mnt/floppy type supermount (rw,sync,dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,codepage=850)
/dev/ide/host0/bus0/target0/lun0/part1 on /mnt/hda1 type vfat (rw,umask=000,iocharset=iso8859-1,codepage=850,quiet)
/dev/ide/host0/bus0/target0/lun0/part2 on /mnt/hda2 type vfat (rw,umask=000,iocharset=iso8859-1,codepage=850,quiet)
/dev/ide/host0/bus0/target1/lun0/part1 on /mnt/hdb1 type vfat (rw,umask=000,iocharset=iso8859-1,codepage=850,quiet)
none on /mnt/zip type supermount (rw,dev=/dev/sda4,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,codepage=850)
none on /mnt/zip2 type supermount (rw,dev=/dev/scsi/host0/bus0/target5/lun0/part4,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,codepage=850)
none on /mnt/hd type supermount (rw,dev=/dev/ide/host0/bus0/target1/lun0/part1,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,codepage=850)
Thank you for the details, it really helps in grasping the situation.
There's obviously nothing wrong related to your second hard drive.
However, I see three strange things about your first hard drive:
1/ hda6 is declared as a swap partition under Linux, but Windows shows it as a FAT32 partition. I don't have windows so I don't know if it is a Windows bug... You may want to format this swap partition under Linux, and maybe (if Windows still sees it as FAT32) ensure somehow that Windows does not see it.
2/ I find it strange to have a swap partition 17GB big. Are you sure you intend to use it as a swap partition? Maybe it is on the Linux side that this partition is misconfigured...
3/ Minor point: no swap partition is declared in the /etc/fstab file. Depending on the quantity of RAM you're using, you may want to declare hda6 as a swap partition in /etc/fstab
More over, I have one very important advice to give you:
You seem to be using "software suspend", ie: suspend to disk, AKA hibernation. This is a great feature indeed, but be sure to NEVER, ever, under any circonstances, resume from swap when you have used your computer since you last shut it down using the "hibernate" feature.
In other words:
- If you boot with the "noresume" or "noresume2" option, then either reformat the swap partition before halting the PC, or suspend again, thus overwriting the previously suspended session.
- Don't boot into Windows and access data that is shared with Linux after you have suspended Linux to disk (the reverse is true too).
Boot up process runs as it shall. Only green ok all the way.
I went to Mandrake Control Center and edited the partitions.
I deleted the huge swap partition shown, and created a new swap partition in the empty 996 Mb space. Then I formated the empty space I got after the old swap partition as a Windows partition. Then I restarted Linux and everything now works ok. Also Windows still works ok.
Is it right to set the swap partition to 996 Mb? I have 512 Mb RAM. I somewhere heard the swap partition has to be twice the size of the available RAM.
One thing I'm wondering about. I have three Linux partitions. Two of them show up in the graph in dark red as / and /home. The third, in green, is the swap partition. Do Linux use three partitions or am I remembering wrong?
Quote:
Originally posted by theYinYeti You seem to be using "software suspend", ie: suspend to disk, AKA hibernation.
This I wasn't aware of. I didn't even know there was such an option in Linux.
Quote:
Originally posted by theYinYeti Don't boot into Windows and access data that is shared with Linux after you have suspended Linux to disk (the reverse is true too).
Interesting information. I often move data from Linux to the Windows partition. I will be cautious if I use the hibernation feature.
And, once again, thank you for taking time to help me!
Suspend to disk is indeed possible in linux, and much more reliable than suspend to ram. However, there are currently 3 methods, some of which require ACPI (or part of it), and some of which don't; I am myself a little lost among those LOL.
You can have further information on this topic here: http://www.suspend2.net/
If you use Software suspend, it helps to have at least as much swap as you have ram. Else 512MB for example are more than enough in most cases. The rule swap=ram*2 dates back from when the average ram amount was 32MB or similar; it is obsolete now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.