LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 03-27-2008, 10:43 PM   #1
deh6
LQ Newbie
 
Registered: Aug 2004
Posts: 18

Rep: Reputation: 0
Cloning Suse10.2 to a different partition: fails boot, (but works with Suse 10.3)


I'm trying to copy a Suse 10.2 on the 2nd HD to the 3rd HD and get it to boot from either drive. The procedure worked on a machine with Suse 10.3, but it fails on a different machine with Suse 10.2. What might be the problem with the following--

Boot fails with the following--
...
loading ext2
Waiting for device /dev/hdd3 to appear: ok
Mounting root /dev/hdd3
mount: unknown filesystem type 'ext3'
{several failed umounts which return busy, then kernel panic -- not syncing}

(The partitions are all ext3.)

The copy procedure is--

1) Copy Suse 10.2, using a live Suse 10.3 CD, from sdb2 where a working Suse 10.2 resides, to sdc3. As root, execute, cp -a source dest
Upon completion the root directories look identical.

2) Go into the new copy and edit the 1st line of /ect/fstab from mounting /dev/hdb2 to / to /dev/hdd3 (Suse 10.2 calls it hdd3, 10.3 calls it sdd3).

3) Setup grub with an option to boot from hdd3 by running Yast/system/boot on the original installation, (or set the options in the grub command line at boot-time, which fails the same way).
 
Old 03-27-2008, 11:44 PM   #2
aus9
LQ Guru
 
Registered: Oct 2003
Posts: 5,124

Rep: Reputation: Disabled
I would like you to expand what errors you are getting at (3) pls.

leaping ahead....whats on first drive?

are all drives still connected when you attempt to boot hdd3.

1) pls consider the relative errors you are likely to get with all drives connected versus 2 drives versus one....with grub counting drives from zero.

2) so post your /etc/fstab from the original suse 10.2 and confirm its the same sdd structure or hdd structure to third drive but it has to differ

eg hdb means slave drive on first ide controller.
...hdd means slave drive on second ide controller

so if you are not removing drives and making jumper positions the same as hdb....the new drive can not have the same fstab and therefore can not have the same grub kernel line for
kernel /boot/vmlinuz-version root=/dev/hdb
 
Old 03-28-2008, 11:25 PM   #3
deh6
LQ Newbie
 
Registered: Aug 2004
Posts: 18

Original Poster
Rep: Reputation: 0
.
Quote:
I would like you to expand what errors you are getting at (3) pls.
Same error as reported, i.e. "mount unknown filesystem 'ext3'" followed by four attempts at umount then Kernel panic. Preceding the "mount unknown..." is a line that says, "loading ext2".

The error indicates that the boot loader is expecting ext2 fs, but the partition is ext3.

Quote:
leaping ahead....whats on first drive?
The first drive has WN98SE, with a bunch of fat partitions. The Suse 10.3 machine has the same HD setup--3 HDs--with WN2K on sda, Suse 10.3 on sdb2, and Suse 10.3 copy on sdc3. It works as expected. The machine in question has WN98SE on hda, Suse 10.2 on hdb2, and Suse 10.2 copy on hdd3.

Quote:
are all drives still connected when you attempt to boot hdd3.
Yes. The HD configuration is not changed.

Quote:
post your /etc/fstab from the original suse 10.2 and confirm its the same sdd structure or hdd structure to third drive but it has to differ
If the filesystem has not been mounted, I would think that at this point fstab would not be a factor.

Here is the fstab from /etc from the hdd3 partition
#/dev/hdb2 / ext2 acl,user_xattr 1 1
/dev/hdd3 / ext3 acl,user_xattr 1 1
/dev/hda1 /windows/C vfat users,gid=users,umask=0002,
iocharset=utf8 0 0
/dev/hda5 /windows/D vfat users,gid=users,umask=0002,
iocharset=cp850 0 0
/dev/hda6 /windows/E vfat users,gid=users,umask=0002,
iocharset=cp850 0 0
/dev/hda7 /windows/F vfat users,gid=users,umask=0002,
iocharset=cp850 0 0
/dev/hda8 /windows/G vfat users,gid=users,umask=0002,
iocharset=cp850 0 0
/dev/hda9 /windows/H vfat users,gid=users,umask=0002,
iocharset=cp850 0 0
/dev/hda10 /windows/I vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hda11 /windows/J vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hda12 /windows/K vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hda13 /windows/L vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hda14 /windows/M vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hda15 /windows/N vfat users,gid=users,umask=0002, iocharset=cp850 0 0
/dev/hdb1 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
/dev/hdd1 swap swap defaults 0 0
/dev/hdd2 /HDD2 auto acl,user_xattr 1 1
#/dev/hdd3 /HDD3 auto acl,user_xattr 1 1

==========================================
Here is the original fstab from hdb2

/dev/hdb2 / ext2 acl,user_xattr 1 1
/dev/hda1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0
/dev/hda5 /windows/D vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda6 /windows/E vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda7 /windows/F vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda8 /windows/G vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda9 /windows/H vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda10 /windows/I vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda11 /windows/J vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda12 /windows/K vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda13 /windows/L vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda14 /windows/M vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hda15 /windows/N vfat users,gid=users,umask=0002,iocharset=cp850 0 0
/dev/hdb1 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
/dev/hdd1 swap swap defaults 0 0
/dev/hdd2 /HDD2 auto acl,user_xattr 1 1
/dev/hdd3 /HDD3 auto acl,user_xattr 1 1

===========================================
Here is fdisk -l for the 2nd & 3rd HD's
Disk /dev/hdb: 81.9 GB, 81964302336 bytes
16 heads, 63 sectors/track, 158816 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 1532 772096+ 82 Linux swap / Solaris
/dev/hdb2 1546 158802 79256677+ 83 Linux
Partition 2 does not end on cylinder boundary.

Disk /dev/hdd: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 1 262 2104483+ 82 Linux swap / Solaris
/dev/hdd2 263 15386 121483530 83 Linux
/dev/hdd3 15387 30515 121523692+ 83 Linux

========================
 
Old 03-29-2008, 12:28 AM   #4
aus9
LQ Guru
 
Registered: Oct 2003
Posts: 5,124

Rep: Reputation: Disabled
1) my main concern was that in doing a copy your fstab if drives remained in....has been answered.

2) I have problems with your hdb fstab entries.
/hdd2 and /hdd3 from your hdb fstab.

as we may have delays in answering each other....what I would like you to consider doing is

to each drive's fstab....delete for the moment all references to other linux drives partitions.

I do not mean windows...I mean entries like
/dev/hdd1 swap swap defaults 0 0
/dev/hdd2 /HDD2 auto acl,user_xattr 1 1

which are from your hdb fstab.

3) and I did not ask earlier...but can you post the file from hdb, /boot/grub/menu.lst please which is the booting file, at the moment until you sort out this...eh? and then you may be considering re-embedding and using the booting files from hdd?
 
Old 03-29-2008, 05:33 PM   #5
deh6
LQ Newbie
 
Registered: Aug 2004
Posts: 18

Original Poster
Rep: Reputation: 0
Quote:
to each drive's fstab....delete for the moment all references to other linux drives partitions
This did not make any difference.

However, I did get it to work by reformatting partition hdd3 from ext3 to ext2. I then re-copied the system from hdb2; fixed fstab, grub remained unchanged from the earlier attemps, and it booted up with no problem.

The boot error had been indicating that it had loaded ext2, but gave an error ("unknown filesystem type, ext3") when it tried to mount it. Changing the partition fs to ext2 made it work.

This suggests that to copy a linux system to another partition and be able to boot up requires that the partition have the same fs as the one the linux system was installed in. If this isn't true, then a) ext2 might be a default fs, given some other problem with the grub parameters, or b) grub is getting the fs type someplace other than fstab (which I would think would require mounting before it could read fstab).

Quote:
can you post the file from hdb, /boot/grub/menu.lst
=================================
# Modified by YaST2. Last modification on Sat Mar 29 12:19:05 EDT 2008
default 0
timeout 8
gfxmenu (hd1,1)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd1,1)
kernel /boot/vmlinuz root=/dev/hdb2 vga=0x31a resume=/dev/hdb1 splash=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (hd0,0)
chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.2
root (hd1,1)
kernel /boot/vmlinuz root=/dev/hdb2 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN
root (hd1,1)
kernel /boot/xen.gz
module /boot/vmlinuz-xen root=/dev/hdb2 vga=0x31a resume=/dev/hdb1 splash=silent showopts
module /boot/initrd-xen

title HDD3 backup
root (hd2,2)
kernel /boot/vmlinuz root=/dev/hdd3 vga=0x31a
initrd /boot/initrd
======================================
 
Old 03-29-2008, 07:49 PM   #6
aus9
LQ Guru
 
Registered: Oct 2003
Posts: 5,124

Rep: Reputation: Disabled
firstly I am glad you solved it.

1) you did not change grub from hdb....so you did not change its booting files so it went from grub ext2(3) stage1.5 to its stage2 and its menu and then jumps to the relevant selected title.

2) grub can handle ext2 or ext3 so I can not explain the change directly.

3) if you had time...reformat back to ext3 but make the kernel line the same style for hdd in case its the initial ram disk image that is complaining.

what I am suggesting is...you copied an initrd that expects a certain environment and it did not get it with your current
kernel /boot/vmlinuz root=/dev/hdd3 vga=0x31a
vs
kernel /boot/vmlinuz root=/dev/hdd3 vga=0x31a resume=/dev/hdb1 splash=silent showopts
 
Old 03-30-2008, 08:48 PM   #7
deh6
LQ Newbie
 
Registered: Aug 2004
Posts: 18

Original Poster
Rep: Reputation: 0
Quote:
1) you did not change grub from hdb....so you did not change its booting files so it went from grub ext2(3) stage1.5 to its stage2 and its menu and then jumps to the relevant selected title.
My post might have been misleading. Grub had the entry for hdd3 from the previous attempts, so it did not need changing.

Quote:
3) if you had time...reformat back to ext3 but make the kernel line the same style for hdd in case its the initial ram disk image that is complaining.
I tried this. No joy.

On the "other" machine (all linux partitions with ext3), I reformatted a partition to ext2, and copied the Suse 10.3 that has been installed on an ext3 partition. It failed the same way, namely, "loading ext3" followed by "mount: unknown filesystem ext2".

This suggests that a linux won't boot up on a filesystem different than the one it was installed on. Could it be that during the installation, modules for the filesystem type are installed in the kernel with the result that the later boot mounting process then fails when a different filesystem is encountered? I haven't found anything to support or refute this, but these experiments seem to support the notion.

If this is true, then maybe a RAID, e.g. md0, partition assigned, with just one partition would make it a "universal" file system. Something to try...
 
Old 04-01-2008, 12:55 AM   #8
deh6
LQ Newbie
 
Registered: Aug 2004
Posts: 18

Original Poster
Rep: Reputation: 0
It looks like the following explains the problem, i.e. initrd needs fixing--

http://www.suseforums.net/index.php?showtopic=45832
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Suse10.2 fails to boot after ndiswrapper/bmcwl5 installation DLHOMME Linux - Wireless Networking 20 06-07-2007 09:05 AM
Dual boot windowsxp and suse10.1, suse not recognizing partition table wantondstrction SUSE / openSUSE 10 06-08-2006 12:42 PM
.xsession-errors filled my root partition now i cant boot suse10.0 64bit ianio Linux - Hardware 1 03-23-2006 05:40 AM
shmget fails in suse 9 but works on suse 8 dcsadler SUSE / openSUSE 0 02-02-2005 11:37 PM
ready to weep: new server, install works, boot fails calebsg Linux - Software 2 11-19-2001 08:35 PM


All times are GMT -5. The time now is 05:12 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration