DD not working

[Craig White]

On Thu, 2007-08-30 at 11:51 -0600, Karl Larsen wrote:
>     I have been trying to use the F7 that I copied to the new Hard Drive 
> but instead I'm getting very strange results. With just the new Hard 
> Drive mounted I set up Grub and changed grub.conf so the proper root was 
> showing. But it would not boot and the error was file system not good. 
> So DD copy must have ruined the file system I put on.
> 
>     So back to the Old Hard Drive and it has some weird stuff going. I 
> wanted to fix the /dev/sdb5 file system and here is what happend:
> 
> [root at k5di ~]# fsck /dev/sdb5
> fsck 1.40.2 (12-Jul-2007)
> e2fsck 1.40.2 (12-Jul-2007)
> /dev/sdb5 is mounted. 
> 
> WARNING!!!  Running e2fsck on a mounted filesystem may cause
> SEVERE filesystem damage.
> 
> Do you really want to continue (y/n)? yes
----
at this point - you have to ask yourself...Is there something in my
constitution that is hell bent to self destruction?
----
> 
> f7: recovering journal
> f7: clean, 174545/10246368 files, 3132553/10239421 blocks
> [root at k5di ~]# mount -t ext2 /dev/sdb5 /mnt
> mount: /dev/sdb5 already mounted or /mnt busy
> 
> The last 2 lines say that /dev/sdb5 is mounted to this Old Hard Drive 
> somehow. I did not do this. /etc/fsack did not do this. So not sure what 
> is going on. And last the /etc/grub.conf has been changed by something 
> to the wrong on this computer. Weird!
----
you can always check what is mounted and where it is mounted by simply
issuing the command 'mount'

you can always 'unmount' filesystems with the 'umount' command but
realize that if you unmount your filesystem with necessary files such
as /usr or /etc - the system is likely to refuse because they are in
use.

you can see what filesystems are set to mount at bootup or later by
checking /etc/fstab and/or what is mounted and when by
checking /var/log/messages

-- 
Craig White <craig at tobyhouse.com>