On Mon, Mar 13, 2017 at 08:36:59PM -0700, David Christensen wrote:
> >and the destination ended up bigger,
> >possibly because one or more of the backups on the source had been using some
> >kind of hardlink de-dupe (I've ranted about hardlink trees being a problem in
> >various backup topics on -u
Hello,
On Mon, Mar 13, 2017 at 08:36:59PM -0700, David Christensen wrote:
> Is anyone aware of a utility that can walk a file system and replace
> identical files with hard links?
As an alternative to doing this, you could consider using a
filesystem with block-level de-duplication support.
ZFS
On 03/14/2017 04:52 AM, The Wanderer wrote:
On 2017-03-13 at 23:36, David Christensen wrote:
Is anyone aware of a utility that can walk a file system and replace
identical files with hard links?
Try rdfind. It's in Debian; I don't use it myself, largely because the
(accepted upstream years a
On 03/14/2017 03:34 AM, David wrote:
On 14 March 2017 at 14:36, David Christensen wrote:
Doing a quick test, it appears that rsync copies hard linked files as if
each were a different file:
rsync -a hard-link-1/ hard-link-2
Here, 'man rsync' says:
"Note that -a does not preserve hardlinks,
On 2017-03-13 at 23:36, David Christensen wrote:
> On 03/13/2017 02:01 AM, Jonathan Dowland wrote:
>
>> On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote:
>> and the destination ended up bigger, possibly because one or more
>> of the backups on the source had been using some kind
On 14 March 2017 at 14:36, David Christensen wrote:
>
> Doing a quick test, it appears that rsync copies hard linked files as if
> each were a different file:
>
> rsync -a hard-link-1/ hard-link-2
Here, 'man rsync' says:
"Note that -a does not preserve hardlinks, because finding
multiply-linked f
On 03/13/2017 02:01 AM, Jonathan Dowland wrote:
On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote:
I'd always put a step 0) in there: is imaging what you want to do? Consider
a file-level backup with rsync (etc etc, as discussed elsewhere in this
thread)
I do imaging for system
On Fri, Mar 10, 2017 at 10:00:45PM -0800, David Christensen wrote:
> >I'd always put a step 0) in there: is imaging what you want to do? Consider
> >a file-level backup with rsync (etc etc, as discussed elsewhere in this
> >thread)
>
> I do imaging for system disks. I do backups and archives for
On 03/10/2017 12:49 AM, Jonathan Dowland wrote:
On Thu, Mar 09, 2017 at 09:04:56PM -0800, David Christensen wrote:
I use LUKS swap (random key) and root (passphrase). I think it's the piece
of the boot chain that gives me the LUKS prompt for root (before the GRUB
menu).
You get that prompt *b
On Thu, Mar 09, 2017 at 09:04:56PM -0800, David Christensen wrote:
> I use LUKS swap (random key) and root (passphrase). I think it's the piece
> of the boot chain that gives me the LUKS prompt for root (before the GRUB
> menu).
You get that prompt *before* GRUB?
I use LUKS everywhere and only g
On 03/08/2017 10:56 PM, Felix Miata wrote:
Was that disk ever used for anything besides Jessie, not new or
wiped first?
The disk was wiped before installing Jesse.
Run strings on it or view in a sector editor and you'll probably see
grub somewhere, if it's a typical Linux installation that p
On Wed, Mar 08, 2017 at 09:46:32PM -0800, David Christensen wrote:
> What is in blocks 1-101?
I believe it's part of grub. My limited understanding of how it works is
it's split up into separate stages designed to fit within the "holes" in
a typical MBR layout, each stage having enough code to ini
Hi,
David Christensen wrote:
> Examining a Windows XP disk, the first partition (C:\) starts at block 63
> (track 1):
> [...]
> Number Start End SizeType File system Flags
> 1 63s156296384s 156296322s primary ntfs boot
That's an oldfashioned layout. Bad
David Christensen composed on 2017-03-08 21:46 (UTC-0800):
...
Examining a Jesse system drive, the first partition starts at block 2048
(1 MB = 2**20 bytes):
2017-03-08 21:30:04 root@jesse ~
# parted /dev/sda u s p
Model: ATA SAMSUNG SSD UM41 (scsi)
Disk /dev/sda: 31277232s
Sector size (logica
On Tue, 2007-05-15 at 21:53 +0100, Piers Kittel wrote:
> Hello all,
>
> I work for a very tiny charity. I was given 2 Dell Dimension 1100
> computers with Debian installed originally, used as test machines.
> Their hard drives were wiped on purpose by an external company (long
> story, tha
> > I've attached an external hard drive to my etch AMD64 box, booted my
> > AMD64 box into the debian installer, and installed a fresh i386 etch
> > onto the external drive.
> >
> > Now I can't boot my box without the external drive attached, because
> > grub complains with "error 21."
This is fi
> > [EMAIL PROTECTED]:~$ sudo chroot /mnt/debinst /bin/bash
> > chroot: cannot run command `/bin/bash': Exec format error
>
> I got into this thread late... but this is the error that you get when
> the chrooted disk is not mounted with -o exec
That doesn't seem to explain my problem:
[EMAIL PR
Matt Miller wrote:
I've attached an external hard drive to my etch AMD64 box, booted
my AMD64 box into the debian installer, and installed a fresh i386
etch onto the external drive.
Now I can't boot my box without the external drive attached,
because grub complains with "error 21."
So boot into
> > I've attached an external hard drive to my etch AMD64 box, booted my
> > AMD64 box into the debian installer, and installed a fresh i386 etch
> > onto the external drive.
> >
> > Now I can't boot my box without the external drive attached
> > you're done.
>
> It looks like the MBR of your Etch
> > I've attached an external hard drive to my etch AMD64 box, booted
> > my AMD64 box into the debian installer, and installed a fresh i386
> > etch onto the external drive.
> >
> > Now I can't boot my box without the external drive attached,
> > because grub complains with "error 21."
>
> So boot
On Sat, Apr 07, 2007 at 01:30:57 +0200, Matt Miller wrote:
> > I've attached an external hard drive to my etch AMD64 box, booted my
> > AMD64 box into the debian installer, and installed a fresh i386 etch
> > onto the external drive.
>
> Now I can't boot my box without the external drive attached,
Florian Kulzer wrote:
On Sat, Apr 07, 2007 at 01:30:57 +0200, Matt Miller wrote:
I've attached an external hard drive to my etch AMD64 box, booted my
AMD64 box into the debian installer, and installed a fresh i386 etch
onto the external drive.
Now I can't boot my box without the external drive
On Sat, Apr 07, 2007 at 01:30:57AM +0200, Matt Miller wrote:
> > I've attached an external hard drive to my etch AMD64 box, booted my
> > AMD64 box into the debian installer, and installed a fresh i386 etch
> > onto the external drive.
>
> Now I can't boot my box without the external drive attache
> I've attached an external hard drive to my etch AMD64 box, booted my
> AMD64 box into the debian installer, and installed a fresh i386 etch
> onto the external drive.
Now I can't boot my box without the external drive attached, because
grub complains with "error 21." I'm thinking that when the
Solved. Thanks for all who helped. Just couple of clarifications for those who
refer this
in future:
"root" in grub corresponds to the drive where grub is installed, usually in
/boot/grub
root = (hdx,y) /* put hd inside the braces and not as shown in the message
below) */
similarly
setup(hd0
On Wed, 24 Nov 2004 10:40, Michael Z Daryabeygi wrote:
> Punit Ahluwalia wrote:
> >I installed grub to /dev/hdc2 which is also /root. This is not a dual
> > boot. It is plain and simple "Woody".
> >
> >How do I install grub to the MBR?
>
> you must start grub, either from in a working linux or by b
Punit Ahluwalia wrote:
I installed grub to /dev/hdc2 which is also /root. This is not a dual boot. It
is plain
and simple "Woody".
How do I install grub to the MBR?
you must start grub, either from in a working linux or by booting
directly into grub.
from the grub command line:
$ root = hd(x,y
On Tue, Nov 23, 2004 at 12:43:32PM -0800, Punit Ahluwalia wrote:
> I installed grub to /dev/hdc2 which is also /root. This is not a dual boot.
> It is plain
> and simple "Woody".
>
> How do I install grub to the MBR?
If I understand your setup correctly, you want to install grub to hda.
This is
I installed grub to /dev/hdc2 which is also /root. This is not a dual boot. It
is plain
and simple "Woody".
How do I install grub to the MBR?
--- CW Harris <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 23, 2004 at 10:00:38AM -0800, Punit Ahluwalia wrote:
> > Thanks for the response. But I did dpkg
On Tue, Nov 23, 2004 at 10:00:38AM -0800, Punit Ahluwalia wrote:
> Thanks for the response. But I did dpkg -P lilo. yet, nothing chnages.
>
This sounds like your BIOS is trying to boot the old LILO boot sector
rather than your grub boot sector. Are you installing grub to the MBR
or to a partition
Thanks for the response. But I did dpkg -P lilo. yet, nothing chnages.
--- Kent West <[EMAIL PROTECTED]> wrote:
> Punit Ahluwalia wrote:
>
> >After upgrading to kernel 2.6.7, my system does not bring up the lilo or
> >grub menu. I
> was
> >using lilo initially but tried setting up grub, but it
Punit Ahluwalia wrote:
After upgrading to kernel 2.6.7, my system does not bring up the lilo or grub
menu. I was
using lilo initially but tried setting up grub, but it seems the problem is
unrelated
with either of them. After the BIOS transfers the control, the screen displays
a message
"searchi
This must depend on the bios, all the ones I have seen did not allow this.
regards
S
-Original Message-
From: Alvin Oga [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 28 July 2004 3:52 p.m.
To: Steven Jones
Cc: [EMAIL PROTECTED]
Subject: mbr RE: Requesting advice on s/w RAID-1 install
On
ehr ... is lilo installed ?
you should have at least
other options
prompt
default=something
image=/boot/vmlinuz_change_extension
root=/dev/hd_change
label=something
read-only
other=/dev/hd_change
label=somethingelse
andrea
On Tue, May 27, 2003 at 02:26:41PM +01
On Tue, Jan 01, 2002 at 10:35:06PM -0800, L Vogtmann wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| On Tuesday 01 January 2002 08:11 pm, Paul A. Thomas wrote:
| > MBR FA13:
|
| You're seeing the GRUB (Grand Unified Bootloader) boot menu.
No. The GRUB menu is a nice graphical (asci
install-mbr is the program that you are accessing.
Try looking at man install-mbr to tell you how it works.
-Original Message-
From: Paul A. Thomas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 2 January 2002 12:12 PM
To: Debian List
Subject: MBR 13FA
Hi.
My first install is functiona
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 01 January 2002 08:11 pm, Paul A. Thomas wrote:
> MBR FA13:
You're seeing the GRUB (Grand Unified Bootloader) boot menu.
F = floppy
A = advanced
1 = boot 1st partition
3 = boot 3rd partition
(don't quote me, as I don't use grub, only seen
Thomas, Rick wrote:
>1. I have two hard drives sda1 and sdb1. I have RedHat installed on sda1
>and Debian installed on sdb1. The master boot record on the sdb1(Debian
>disk) was accidently erased. I can still mount the drive but I can no
>longer boot from the sdb1 drive. Is there any way to
Rick Thomas writes:
RT> 1. I have two hard drives sda1 and sdb1. I have RedHat installed on sda1
RT> and Debian installed on sdb1. The master boot record on the sdb1(Debian
RT> disk) was accidently erased. I can still mount the drive but I can no
RT> longer boot from the sdb1 drive.
Are you u
On Wed, 2001-09-19 at 17:29, Matthew Sackman wrote:
> Hi People,
>
> Got a weird one here...
>
> I've been setting up a new box and swapping things over from my
> existing computer. On this computer the windows drive is hda
> and linux is on hdb and hdd
>
> Previously, using LILO writing to the
If your drive has more than 1024 cylinders, that can cause a problem as
well. If it is, you might try repartitioning it into two partitions, then
install potato on the first partition. Making sure of course that the first
partition ends at cylinder 1023. Also, if you have SCSI drives, sometimes
I think I'm just going to resort to booting off a floppy. I appreciate all
the help I've recieved.
doc
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
hi doc
those silly lilo problems could be due to many possible reasons...
try each of the following...
- boot off floppy ( best bet )
- boot into single user than run lilo again
( if it fails..try more of the following experiments
- use a rescue disks and create a bootable flop
y linear instead of lba32, see if that helps.
Finally, what sort of machine is this on? How old is the bios etc?
-Original Message-
From: The Doc [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 13, 2001 12:13 PM
To: debian-user@lists.debian.org
Subject: RE: MBR Problem
I tried
fdisk /mb
I tried
fdisk /mbr
and then reinstalled potato, installing lilo on /dev/hda1, not the MBR.
I still get that shit when I boot.
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
If this is a dual boot system do the fdisk /mbr from
the dos prompt.
--- Robert Schmidt <[EMAIL PROTECTED]>
wrote:
> fdisk /mbr should do it
>
> -Original Message-
> From: The Doc [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 13, 2001 11:46 AM
> To: debian-user@lists.debian.org
> Subject:
fdisk /mbr should do it
-Original Message-
From: The Doc [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 13, 2001 11:46 AM
To: debian-user@lists.debian.org
Subject: MBR Problem
Hello all,
I need a way to clear my master boot record on my first hard disk. No
matter how much I uninstall and
On Tue, May 01, 2001 at 11:04:06AM -0400, Paindavoine, Matthieu (MPAINDAV)
wrote:
> Loading 1.
>
> I don't quite understand what my problem is. Do I need to fix the MBR, or do
> I need to play with lilo?
> (I think it's option 2, because it goes like
> Boot: MBR ---> LILO ---> Kernel,
>
Hello Frederik,
* Frederik Vanrenterghem wrote:
> Hi all,
>
> I've installed Debian 2.2 on an old 486 yesterday (which caused some minor
> problems). Everything turned out fine in the end, except the boot
> process. It's a Linux-only system, I've partitioned the disk as follows:
> /dev/hda1: /bo
Use dd to copy to local_file and read with hex reader like MC.
# dd if=/dev/hda of=local_file count=20
MC is midnight commander in console.
Osamu
On Tue, Sep 19, 2000 at 05:02:06PM +, stefan goeman wrote:
> Hello,
>
> Is there a way to read my current MBR, or is this the file mbr.b in
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
> I have to uninstall Linux and put WindowsNT on a workstation at work.
> I have formated the disk with fdisk and I get
> LILO
> Linux Loading ..
> Error 0x01
> Linux Loading ..
> etc
> .
> .
> .
>
> How do I erase the MBR?
It worked.
Thanks, Now I have to go back to crashes or figuring out why it crashes.
For those timing Linux uptime, I would say about a month of continuous
use.
Dan
Steve Zinck <[EMAIL PROTECTED]> wrote:
> On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
>
> > How do I erase
Use dos boot floppy with fdisk on it. Then type 'fdisk /mbr'
Oliver
Dan Hutchinson wrote:
>
> I have to uninstall Linux and put WindowsNT on a workstation at work.
> I have formated the disk with fdisk and I get
> LILO
> Linux Loading ..
> Error 0x01
> Linux Loading ..
> etc
> .
> .
>
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
> How do I erase the MBR?
In DOS you can do "fdisk /mbr".
--
Steve Zinck <[EMAIL PROTECTED]>
http://nerd.halifax.ns.ca
On 4/12/99 luis wrote:
how can i install a sort of mbr that runs before lilo ?
because after having instaled debian i need to install a dos
partition, but as hda1 is the swap, hda2 linux and hda3 is dos, lilo
can not load the last partition (far beyong the 1024 kbytes limit)
if LILO won't boo
Boot from any DOS 6.X/Win95 bootable diskette and once in the DOS prompt
type fdisk /mbr. This will reinstate your clubbered MBR.
BTW, is there anyway in this list to reply to the list instead of the
author? My problem is I have filtering of incoming emails and it doesn't
work 'coz my filter loo
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
> I was wondering how hard it is to remove/replace the mbr package. We have
> a single system running hamm, for which we want to disable the capability
> of booting from a diskette. Currently we've disabled floppy-boot in the
> BIOS, and configured
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
: I was wondering how hard it is to remove/replace the mbr package. We have
: a single system running hamm, for which we want to disable the capability
: of booting from a diskette. Currently we've disabled floppy-boot in the
: BIOS, and configur
> went through, ("1+0 in, 1+0 out" etc) but made no difference to booting --
> still "Lil-" and system hangs.
> My system _did_ work before -- honest!!
Did you alter the bios settings for your hdisk at boot up? ... If you have
auto hdd detection turn that on (as opposed to LBA or LARGE) .. It shou
59 matches
Mail list logo
