On 17May2020 19:38, Robert Moskowitz wrote:
On 5/17/20 7:12 PM, Cameron Simpson wrote:
On 17May2020 19:06, Robert Moskowitz wrote:
Well I am shopping for a USB ext HD...
At least 2TB, <$100, USB 2, Good life time 2,5" or 3.5"?
Well I will call the local Micro Center tomorrow and see w
On 5/17/20 7:33 PM, Ed Greshko wrote:
On 2020-05-18 07:06, Robert Moskowitz wrote:
On 5/17/20 6:37 PM, Samuel Sieb wrote:
On 5/17/20 1:29 PM, Robert Moskowitz wrote:
I basically jammed done the y key until it finished. I am going to get a new
drive...
So many errors. I wonder how? Perh
On 5/17/20 7:12 PM, Cameron Simpson wrote:
On 17May2020 19:06, Robert Moskowitz wrote:
Well I am shopping for a USB ext HD...
At least 2TB, <$100, USB 2, Good life time 2,5" or 3.5"?
Well I will call the local Micro Center tomorrow and see what they
have in stock and do a drive up p
On 2020-05-18 07:06, Robert Moskowitz wrote:
>
>
> On 5/17/20 6:37 PM, Samuel Sieb wrote:
>> On 5/17/20 1:29 PM, Robert Moskowitz wrote:
>>> I basically jammed done the y key until it finished. I am going to get a
>>> new drive...
>>>
>>> So many errors. I wonder how? Perhaps 2 rsyncs running a
On 17May2020 15:11, George N. White III wrote:
According to the man page, "fsck.xfs" is just "exit 0".
It has has lead up logic to accept the correct command line arguments,
but yes. The kernel "mount" for XFS does any repair. It is all very
nice.
There is a separae "xfs_repair" command fo
On 17May2020 16:29, Robert Moskowitz wrote:
I basically jammed done the y key until it finished. I am going to get
a new drive...
FYI, there's a BSD derived command called "yes" whose purpose in life is
to print "yes" (or a string of your choice) forever, precisely for
piping into other pro
On 17May2020 19:06, Robert Moskowitz wrote:
Well I am shopping for a USB ext HD...
At least 2TB, <$100, USB 2, Good life time 2,5" or 3.5"?
Well I will call the local Micro Center tomorrow and see what they have
in stock and do a drive up pickup.
I tend to buy Western Digital Element
On 5/17/20 6:37 PM, Samuel Sieb wrote:
On 5/17/20 1:29 PM, Robert Moskowitz wrote:
I basically jammed done the y key until it finished. I am going to
get a new drive...
So many errors. I wonder how? Perhaps 2 rsyncs running at the same
time?
No. You could possibly get messed up files,
On 5/17/20 1:29 PM, Robert Moskowitz wrote:
I basically jammed done the y key until it finished. I am going to get
a new drive...
So many errors. I wonder how? Perhaps 2 rsyncs running at the same time?
No. You could possibly get messed up files, although rsync is pretty
safe. But you s
On Sun, 17 May 2020 at 17:30, Robert Moskowitz wrote:
> I hope.
>
> I basically jammed done the y key until it finished. I am going to get
> a new drive...
>
> So many errors. I wonder how? Perhaps 2 rsyncs running at the same time?
>
It is almost certainly a hardware problem: hard disk, cabl
I hope.
I basically jammed done the y key until it finished. I am going to get
a new drive...
So many errors. I wonder how? Perhaps 2 rsyncs running at the same time?
On 5/17/20 3:51 PM, Robert Moskowitz wrote:
On 5/17/20 3:32 PM, Jonathan Billings wrote:
On May 17, 2020, at 14:14, R
Hi,
Robert Moskowitz wrote:
> sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
This is a command transport failure of the lowlevel driver. I know such
effects from dying USB boxes with optical drives (having SATA controllers).
https://www.tldp.org/HOWTO/archived/SCSI-Pr
On 5/17/20 3:32 PM, Jonathan Billings wrote:
On May 17, 2020, at 14:14, Robert Moskowitz wrote:
# fsck /dev/sdc
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /d
On May 17, 2020, at 14:14, Robert Moskowitz wrote:
>
> # fsck /dev/sdc
> fsck from util-linux-ng 2.17.2
> e2fsck 1.41.12 (17-May-2010)
> fsck.ext2: Superblock invalid, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc
>
> [...]
> # parted /dev/sdc
On 5/17/20 2:13 PM, Gordon Messmer wrote:
On 5/17/20 10:22 AM, Robert Moskowitz wrote:
How can I get this bad file out of the way so I can back up properly?
IIRC, an IO error can result from either a corrupt filesystem or a
media error. The kernel "dmesg" can tell you more about the cause
On 5/17/20 1:52 PM, Richard wrote:
Date: Sunday, May 17, 2020 13:22:54 -0400
From: Robert Moskowitz
I am having a problem with rsyncing:
rsync -ah --stats --delete /home/
/media/HD103SI/backups/homebase/home
rsync:
readlink_stat("/media/HD103SI/backups/homebase/home/abba/abba/Excel
/Home/Pow
On 5/17/20 10:22 AM, Robert Moskowitz wrote:
How can I get this bad file out of the way so I can back up properly?
IIRC, an IO error can result from either a corrupt filesystem or a media
error. The kernel "dmesg" can tell you more about the cause of the
error, typically. If there's filesy
On Sun, 17 May 2020 at 14:54, Richard
wrote:
>
> > Date: Sunday, May 17, 2020 13:22:54 -0400
> > From: Robert Moskowitz
> >
> > I am having a problem with rsyncing:
> >
> > rsync -ah --stats --delete /home/
> > /media/HD103SI/backups/homebase/home
> > rsync:
> > readlink_stat("/media/HD103SI/bac
> Date: Sunday, May 17, 2020 13:22:54 -0400
> From: Robert Moskowitz
>
> I am having a problem with rsyncing:
>
> rsync -ah --stats --delete /home/
> /media/HD103SI/backups/homebase/home
> rsync:
> readlink_stat("/media/HD103SI/backups/homebase/home/abba/abba/Excel
> /Home/Power usage.xls") fail
I am having a problem with rsyncing:
rsync -ah --stats --delete /home/ /media/HD103SI/backups/homebase/home
rsync:
readlink_stat("/media/HD103SI/backups/homebase/home/abba/abba/Excel/Home/Power
usage.xls") failed: Input/output error (5)
rsync: recv_generator: failed to stat
"/media/HD103SI/bac
20 matches
Mail list logo
