Re: DD not working
- From: Craig White <craig@xxxxxxxxxxxxx>
- Date: Thu, 30 Aug 2007 11:10:23 -0700
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@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@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@xxxxxxxxxxxxx>
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- References:
- DD not working
- From: Karl Larsen
- DD not working
- Prev by Date: Re: Intel 82566DC-2 problem
- Next by Date: Re: DD not working
- Previous by thread: Re: DD not working
- Next by thread: Re: DD not working
- Index(es):
Relevant Pages
- Re: getfsent(3) and spaces in fstab
... Each filesystem is described on a separate line; ... having a space in
a filesystem or mount point will violate ... if the name of the file system or the
mount point ... (freebsd-hackers) - SUMMARY: how do I REALLY delete a file?
... leaving the rest of the file system intact. ... Wipedrive doesn't seem to be
available for Solaris, but might be of interest to ... run this on each filesystem
where the files from ... >Solaris' UFS] do not satisfy this assumption." ...
(SunManagers) - Re: usb device
... The file system on the device is fat32! ... >>I had a similar problem
while trying to mount a newly bought USB stick ... It was mountable and writeabel and readable
under Windows XP ... >Yes definitely check the filesystem on the device. ...
(Debian-User) - Summary: df -k : discrepancy in the % displayed
... The standard file system reserves about 10% of the kbytes for efficiency; ...
is unavailable to anyone except root. ... If you created your filesystem with default
options, ... This 5% or so reservation is probably not worth bothering with on a 1-2GB
... (SunManagers) - Re: How to take down a system to the point of requiring a newfs with one line of C (userland)
... If we think it's purely a property of the number of files in the root directory, then you
can limit the number of inodes in the file system at all. ... Too many files in a top-level
UFS-2 filesystem directory will cause ... I got a page fault panic on mount of the
new distfiles ... catch the messages when it panics, which it will as soon as the mount
is ... (FreeBSD-Security)