On 8/13/14, Martin G. McCormick wrote:
> I am the one who posted stating that I can't seem to make a
> bootable new hard drive for my Linux Squeeze system. It's been
> quoted, "It ain't what you don't know that will hurt you, but
> what you know that just ain't so." I think I am in that
> territor
Stefan Monnier writes:
> > One last step may be necessary : update the UUIDs in /etc/fstab and
> > /boot/grub/grub.cfg, as you created new volumes with new UUIDs instead
> > of cloning them. Or alternatively, change the UUIDs on the new disk with
> > tune2fs, mkswap... to match the ones on the old
> One last step may be necessary : update the UUIDs in /etc/fstab and
> /boot/grub/grub.cfg, as you created new volumes with new UUIDs instead
> of cloning them. Or alternatively, change the UUIDs on the new disk with
> tune2fs, mkswap... to match the ones on the old disk. Otherwise you'll
> be stu
Bob Weber a écrit :
>
> A second way is to start sysrescuecd normally and mount the root file system
> to
> a directory. Make a directory say x and mount the root filesystem on it. Run
> these three commands: "mount --bind /dev x/dev" and "mount --bind /proc
> x/proc" and "mount --bind /sy
Bob Weber writes:
> I use sysrescuecd (http://www.sysresccd.org/) to make a new drive
> bootable.
> There are two ways to get a bootable disk with sysrescuecd.
>
> One way is to use a special boot mode where sysrescue starts its own
> kernel to a
> system on the hard disk. Once booted you can j
I use sysrescuecd (http://www.sysresccd.org/) to make a new drive bootable.
There are two ways to get a bootable disk with sysrescuecd.
One way is to use a special boot mode where sysrescue starts its own kernel to a
system on the hard disk. Once booted you can just use 'grub-install /dev/sda'
t
On 13/08/14 09:09 AM, Martin G. McCormick wrote:
I am the one who posted stating that I can't seem to make a
bootable new hard drive for my Linux Squeeze system. It's been
quoted, "It ain't what you don't know that will hurt you, but
what you know that just ain't so." I think I am in that
territo
AW writes:
> 1. As far as I know, it's not possible to simply copy a working /dev tree.
> These are special files which are generated with the mknod utility.
>
> 2. Booting a computer is fairly complex. Everything needs to be at a
> specific
> location on the drive, needs to occupy the appropria
On Wed, 13 Aug 2014 08:09:41 -0500
"Martin G. McCormick" wrote:
> but I am curious as to why the first method simply has never booted?
1. As far as I know, it's not possible to simply copy a working /dev tree.
These are special files which are generated with the mknod utility.
2. Booting a c
I am the one who posted stating that I can't seem to make a
bootable new hard drive for my Linux Squeeze system. It's been
quoted, "It ain't what you don't know that will hurt you, but
what you know that just ain't so." I think I am in that
territory now. What I have been doing was to format the ne
On Mon, Aug 4, 2014 at 10:57 AM, Martin G. McCormick
wrote:
> Tom H writes:
>>
>> Are you mounting "/mnt/{dev,proc,sys}" before chrooting?
>
> No. I did try the mount command after chrooting which successfully ran, but
> didn't fix the missing /dev. I bet this is the crux of the
> problem, however
Martin G. McCormick a écrit :
> Tom H writes:
>> Are you mounting "/mnt/{dev,proc,sys}" before chrooting?
>
> No. I did try the mount command after chrooting which successfully ran, but
> didn't fix the missing /dev. I bet this is the crux of the
> problem, however. Mount just mounts everything in
Tom H writes:
> Are you mounting "/mnt/{dev,proc,sys}" before chrooting?
No. I did try the mount command after chrooting which successfully ran, but
didn't fix the missing /dev. I bet this is the crux of the
problem, however. Mount just mounts everything in /etc/fstab. I
don't remember if dev is t
On Mon, Aug 4, 2014 at 7:33 AM, Martin G. McCormick
wrote:
>
> It turns out that the reason I never thought of using mkfs to
> build a working boot sector is that mkfs doesn't do that. Grub,
> however, does but I am still a bit confused as to how to get it
> working. I mounted the new drive on /mn
On Mon, 04 Aug 2014 06:33:35 -0500
"Martin G. McCormick" wrote:
>a working boot sector is that mkfs doesn't do that.
That's correct. However there is another program called 'makefs' that
will create an image file from a user defined directory tree. The
'makefs' program is not the long name ve
It turns out that the reason I never thought of using mkfs to
build a working boot sector is that mkfs doesn't do that. Grub,
however, does but I am still a bit confused as to how to get it
working. I mounted the new drive on /mnt
#mount /dev/sdf1 /mnt
It's all there.
#chroot /mnt
/ is now the top
I knew there would be several suggestions for solutions
to making a new boot disk and I appreciate all of them. I also
appreciate the explanation as to why my previous attempts
at creating a bootable copy failed. It all makes
perfect sense now. I will probably try mkfs first. I have used mk
Le 03/08/2014 14:45, Martin G. McCormick a écrit :
I am replacing a nearly 20-year-old 10 GB conventional
hard drive with a slightly-larger flash drive for / on a
Debian-squeeze system; / on flash as it were. I know this can
work as I have an older version of debian on another box that
ha
On 08/03/2014 03:45 PM, Martin G. McCormick wrote:
> I thought I had a pretty good idea how to do this but I
> obviously am missing something.
> I am replacing a nearly 20-year-old 10 GB conventional
> hard drive with a slightly-larger flash drive for / on a
> Debian-squeeze system; / o
"Martin G. McCormick" writes:
Copy MBR only of a hard drive:
dd if=/dev/hda of=/dev/hdb bs=446 count=1
The last 64 bits of the 512 mbr contain partition
information and this is where I may be all wet. I thought the
disk-copy process took care of that but if not, this is why
I thought I had a pretty good idea how to do this but I
obviously am missing something.
I am replacing a nearly 20-year-old 10 GB conventional
hard drive with a slightly-larger flash drive for / on a
Debian-squeeze system; / on flash as it were. I know this can
work as I have an old
21 matches
Mail list logo
