On 10/20/24 13:00, William Torrez Corea wrote:
I am trying to boot my USB but this device is unrecognizable for the BIOS.
How can I convert filesystems through DD?
I want to save a copy of the file in MSDOS or GPT.
What is the make and model of your computer?
What is the make and model of
On Sun, 20 Oct 2024 14:00:46 -0600
William Torrez Corea wrote:
> I am trying to boot my USB but this device is unrecognizable for the
> BIOS.
Well, that doesn't tell us very much. Are you in fact using a BIOS
(which would expect a MS-DOS partition table), or are you using newer
firmware (which w
md wrote:
> Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to
> the SATA based computer I've been using. With this drive (/dev/sr1), dd
> seems to working fine without having to precede it with dvdbackup -M.
Thomas Schmitt wrote:
> But aren't those copied sectors still sc
Hi,
md wrote:
> > libdvdread: Attempting to retrieve all CSS keys
Pascal Hambourg wrote:
> Didn't these messages about CSS keys ring a bell in anybody's mind ?
In hindsight, yes.
> Check the kernel logs with dmesg.
This yielded a nice theory about libdvdcss and not going to jail.
md wrote:
Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to the
SATA based computer I've been using. With this drive (/dev/sr1), dd seems to
working fine without having to precede it with dvdbackup -M.
In the dvdread README on github, I found this: '. If you attempt to read
Le 10/12/2018 à 06:34, md a écrit :
MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso
32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s
dd: error reading '/dev/sr0': Input/output error
(...)
MD> dvdbackup -M
libdvdread: Attempting to retrieve all CSS keys
libdvdread: This can take a _long_ t
On Monday 10 December 2018 12:57:46 md wrote:
> In the scenarios when dd fails, the amount that dd reads before
> failing varies from to movie dvd to movie dvd. At times dd will read
> 400MB before failing.
>
> A few FWIW snippets:
> dvdbackup 'fixes' the dd problem
> xorriso doesn't 'fix' the dd
Hi,
md wrote:
> [] sr 4:0:0:0: [sr0] tag#20 Sense Key : Illegal Request [current]
> [] sr 4:0:0:0: [sr0] tag#20 Add. Sense: Read of scrambled sector without
> authentication
> [] sr 4:0:0:0: [sr0] tag#20 CDB: Read(10) 28 00 00 3b 23 c0 00 00 40 00
This is probably CSS access restriction.
I gues
In the scenarios when dd fails, the amount that dd reads before failing varies
from to movie dvd to movie dvd. At times dd will read 400MB before failing.
A few FWIW snippets:
dvdbackup 'fixes' the dd problem
xorriso doesn't 'fix' the dd problem
xorriso has similar problem to dd
dvdbackup 'fixes'
On Monday 10 December 2018 04:37:10 Thomas Schmitt wrote:
> Hi,
>
> Jude DaShiell wrote:
> > Why not prefix that dd command with a sudo udevadm settle command
> > and only allow the dd command to run on success case?
>
> man udevadm says:
>
> udevadm settle [options]
>Watches the udev ev
On Monday 10 December 2018 04:11:28 Jude DaShiell wrote:
> On Mon, 10 Dec 2018, Thomas Schmitt wrote:
> > Date: Mon, 10 Dec 2018 02:45:43
> > From: Thomas Schmitt
> > To: debian-user@lists.debian.org
> > Cc: mickyd...@protonmail.com
> > Subject: Re: dd: error
On Monday 10 December 2018 03:44:20 Thomas Schmitt wrote:
> Hi,
>
> Gene Heskett wrote:
> > > > Classic slow spinup.
>
> I wrote:
> > > After 33 MiB of reading ?
> >
> > That much would would also invalidate the dry sliders theory
>
> There might well be mechanical or optical problems involved. As
Hi,
Jude DaShiell wrote:
> Why not prefix that dd command with a sudo udevadm settle command and
> only allow the dd command to run on success case?
man udevadm says:
udevadm settle [options]
Watches the udev event queue, and exits if all current events are
handled.
We have no i
On Mon, 10 Dec 2018, Thomas Schmitt wrote:
> Date: Mon, 10 Dec 2018 02:45:43
> From: Thomas Schmitt
> To: debian-user@lists.debian.org
> Cc: mickyd...@protonmail.com
> Subject: Re: dd: error reading '/dev/sr0': Input/output error
> Resent-Date: Mon, 10 Dec 2018 07:46:
Hi,
Gene Heskett wrote:
> > > Classic slow spinup.
I wrote:
> > After 33 MiB of reading ?
> That much would would also invalidate the dry sliders theory
There might well be mechanical or optical problems involved. As said,
the failure patterns of drives are variform. Thus my question whether
d
On Monday 10 December 2018 02:45:43 Thomas Schmitt wrote:
> Hi,
>
> md wrote:
> > When copying a dvd to file on the harddrive, I'm getting [...]
> > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso
> > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s
> > dd: error reading '/dev/sr0': Input/out
On Monday 10 December 2018 02:34:48 md wrote:
> >> When copying a dvd to file on the harddrive, I'm getting the
> >> message dd: error reading '/dev/sr0': Input/output error
> >> If I first run dvdbackup, then Ctrl-C out of it. I can then reissue
> >> the dd command and it will finish fine. If I e
>> When copying a dvd to file on the harddrive, I'm getting the message
>> dd: error reading '/dev/sr0': Input/output error
>> If I first run dvdbackup, then Ctrl-C out of it. I can then reissue
>> the dd command and it will finish fine. If I eject the dvd then insert
>> another dvd, the same situa
Hi,
md wrote:
> When copying a dvd to file on the harddrive, I'm getting [...]
> MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso
> 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s
> dd: error reading '/dev/sr0': Input/output error
Do you see fresh messages in the output of dmesg ?
Like
De
On Monday 10 December 2018 00:34:58 md wrote:
> When copying a dvd to file on the harddrive, I'm getting the message
> dd: error reading '/dev/sr0': Input/output error
> If I first run dvdbackup, then Ctrl-C out of it. I can then reissue
> the dd command and it will finish fine. If I eject the dvd
On Fri, Nov 02, 2018 at 01:03:12PM +, Adam Weremczuk wrote:
New test results with suggested parameters below:
Slower server
W: 1310720 bytes (13 GB, 12 GiB) copied, 97.5106 s, 134 MB/s
R: 1310720 bytes (13 GB, 12 GiB) copied, 28.6353 s, 458 MB/s
Faster server
W: 1310720 bytes (1
Hi Mike,
Thanks for the suggestion.
New test results with suggested parameters below:
Slower server
W: 1310720 bytes (13 GB, 12 GiB) copied, 97.5106 s, 134 MB/s
R: 1310720 bytes (13 GB, 12 GiB) copied, 28.6353 s, 458 MB/s
Faster server
W: 1310720 bytes (13 GB) copied, 83.7368 s, 15
On Fri, Nov 02, 2018 at 11:58:48AM +, Adam Weremczuk wrote:
dd if=/dev/zero of=test.bin bs=512 count=1024 oflag=sync
That's a uselessly small block size & count. Try again with something
more like bs=128k count=10
Note that your dd test is a write test and your testparm is a read tes
Forgot to mention both run Debian (7.1 and 9.5) and filesystems are ext4
on both.
On 02/11/18 11:58, Adam Weremczuk wrote:
Hi all,
Can somebody explain this huge difference between 2 (almost) identical
servers:
---
On 09/26/2017 11:35 AM, Gene Heskett wrote:
On Tuesday 26 September 2017 09:57:57 Jack Dangler wrote:
I have an existing drive near EOL (judging from the sounds). I got a
replacement drive for it (same size).
I plugged the replacement into a USB port and started a byte-for-byte
copy with
dd
On Tuesday 26 September 2017 09:57:57 Jack Dangler wrote:
> I have an existing drive near EOL (judging from the sounds). I got a
> replacement drive for it (same size).
>
> I plugged the replacement into a USB port and started a byte-for-byte
> copy with
>
> dd if=/dev/sda of=/dev/sdc
>
> The proc
On Tue, Sep 26, 2017 at 04:28:10PM +0200, Thomas Schmitt wrote:
The first suspect for slow dd is small block size.
So you should in any case ask dd for larger chunks as already proposed
by Michael Stone. For copying Debian ISOs to USB sticks the FAQ proposes
4 MiB. But i think 1 MiB is surely eno
Le 26/09/2017 à 15:57, Jack Dangler a écrit :
I have an existing drive near EOL (judging from the sounds). I got a
replacement drive for it (same size).
I plugged the replacement into a USB port and started a byte-for-byte
copy with
dd if=/dev/sda of=/dev/sdc
dd is not the best tool to cop
Hi,
> Is it 'usual' to have dd take upwards of 2 days to copy a drive ?
Not really. An old 500 GiB SATA disk may deliver about 50 MiB/s.
That's 1 seconds, a bit less than 3 hours.
(If you copy from filesystem to filesystem it may last much longer
due to the lookup times in the trees.)
The f
On Tue, Sep 26, 2017 at 09:57:57AM -0400, Jack Dangler wrote:
I have an existing drive near EOL (judging from the sounds). I got a
replacement drive for it (same size).
I plugged the replacement into a USB port and started a byte-for-byte
copy with
dd if=/dev/sda of=/dev/sdc
The process ran
On Tue, Sep 26, 2017 at 09:57:57AM -0400, Jack Dangler wrote:
> I have an existing drive near EOL (judging from the sounds). I got a
> replacement drive for it (same size).
>
> I plugged the replacement into a USB port and started a byte-for-byte copy
> with
>
> dd if=/dev/sda of=/dev/sdc
>
> Th
Hi,
kAt wrote:
> I am trying to find out
> what firmware works with this medium and what it really does.
It's a little computer which implements USB bus operation, and a subset
of the SCSI command protocol, and also manages the mapping from logical
addresses (LBA) to physical addresses.
What it d
Thomas Schmitt:
> Hi,
>
> kAt wrote:
>> All I can say is that I feel honored that some useful code was produced
>> with my problem statement as an inspiration.
>
> Whether it's useful will still have to turn out. :)
> Up to now it has one happy user.
I think being able to use a thumb-stick as a
On 2017-03-28, kAt wrote:
> All I can say is that I feel honored that some useful code was produced
> with my problem statement as an inspiration.
That's like some befuddled bumpkin down in North Carolina saying he's
proud to find a portrait of himself in one of Thomas Wolfe's books.
Actually i
Hi,
now i have spoiled the wet run messages. "Wrote" rather than "Removed"
in the messages agout APM and GPT. Gr.
New source:
http://scdbackup.webframe.org/make_isombr_part.c
MD5 34aa900801f65955a61cebf0280eeb3b
Compile by
cc -g -Wall -o make_isombr_part make_isombr_part.c
New amd6
Hi,
i adopted the idea of a dry run for educational purposes.
It demonstrates in detail what make_isombr_part would do to the
storage device.
With debian-8.7.1-i386-xfce-CD-1.iso on /dev/sdc:
-
$ ./make_isombr_part /dev/sdc a
Hi,
isongbird wrote:
> also, consider that bugs do happen and sometimes
> a dry run switch will discover them before it does
> the actual write to the device.
The code still contains a conditional part which i used with the
initial tests.
If you change
/* # def ine Make_isombr_part_dummY yes
Hi,
kAt wrote:
> All I can say is that I feel honored that some useful code was produced
> with my problem statement as an inspiration.
Whether it's useful will still have to turn out. :)
Up to now it has one happy user.
I am pondering about the partition table mess since quite a while.
On the o
Thomas Schmitt wrote:
> songbird wrote:
>> always give an option to do a dry run without any actual changes
>> being made
>
> But what difference would that make ?
just me and a preference to err on the side
of caution when dealing with devices that might
alter a very basic thing.
> If the pr
kAt wrote:
> All I can say is that I feel honored that some useful code was produced
> with my problem statement as an inspiration.
> I am doing research on the topic trying to learn all that feels like a
> huge gap of how disks and data relate.
>
> Have a nice day Thomas
it is very useful to th
All I can say is that I feel honored that some useful code was produced
with my problem statement as an inspiration.
I am doing research on the topic trying to learn all that feels like a
huge gap of how disks and data relate.
Have a nice day Thomas
kAt
Thomas Schmitt:
> Hi,
>
> i wrote a small
Hi,
songbird wrote:
> always give an option to do a dry run without any actual changes
> being made
But what difference would that make ?
If the program thinks it's not ok, then it will refuse.
If it thinks it's ok, then shall the user refrain nevertheless ?
Of course it's safer to know what is
Thomas Schmitt wrote:
...
>
>
> See a test run with rescatux ISO on /dev/sdc (any current Debian i386
> or amd64 ISO would be suitable, too).
>
> Still less dangerous than manipulating /dev files as superuser is
> to give the
Hi,
i wrote:
> > One may well try to manage the stick by a partition editor.
Richard Owlett wrote:
> Appropriate search terms that would lead to learning "howto"?
"linux"-or-"yourdesktop" together with "partition editor".
The reason to start this thread was about "gparted". We saw output of
"f
On 03/28/2017 09:20 AM, Thomas Schmitt wrote:
Hi,
Richard Owlett wrote:
/dev/sdb3 1140736 15130623 13989888 6.7G 83 Linux
For the records (as Richard obviously knew it already):
If you believe that line, would you like to by a Brooklyn Bridge?
It was legitimately for sale in late 196
Hi,
Richard Owlett wrote:
> /dev/sdb3 1140736 15130623 13989888 6.7G 83 Linux
For the records (as Richard obviously knew it already):
After the run of make_isombr_part, the new partition has no
filesystem.
The commands mkfs or mkdosfs would be the next step, or some GUI tool
for managing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Mar 28, 2017 at 08:41:52AM -0500, Richard Owlett wrote:
> On 03/28/2017 07:17 AM, to...@tuxteam.de wrote:
> >[snip]
> >
> >I'd guess there's a difference between Thomas's processor architecture
> >and yours. [snip]
>
> Recompiled for my archit
On 03/28/2017 07:17 AM, to...@tuxteam.de wrote:
[snip]
I'd guess there's a difference between Thomas's processor architecture
and yours. [snip]
Recompiled for my architecture successfully.
Did a successful minimal install from my modified flash drive.
Operator error or other?
It's always
On 03/28/2017 07:16 AM, Thomas Schmitt wrote:
[snip]
To build your own binary, do in the directory where you have the
file make_isombr_part.c :
cc -g -Wall -o make_isombr_part make_isombr_part.c
This command should end quickly without any messages.
If messages appear, then please show them.
On 03/28/2017 07:16 AM, Thomas Schmitt wrote:
Hi,
Richard Owlett wrote:
I am running Debian 8.6.0 with MATE desktop.
...
bash: /home/richard/Downloads/make_isombr_part: cannot execute binary file:
Exec format error
Can it be your system is equipped with Debian for architecture i386 ?
Yepp ;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Mar 28, 2017 at 02:16:24PM +0200, Thomas Schmitt wrote:
[...]
> http://scdbackup.webframe.org/make_isombr_part.c
Yummy source. Now we're talking :-)
(trapped at work ATM. But I'll sure look into that)
regards
- -- t
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Mar 28, 2017 at 06:53:08AM -0500, Richard Owlett wrote:
> On 03/28/2017 05:10 AM, Thomas Schmitt wrote:
> >[snip]
> >
> >It would be interesting to see how various partition editors react on
> >this state of the USB stick. Can they reduce the s
Hi,
Richard Owlett wrote:
> I am running Debian 8.6.0 with MATE desktop.
> ...
> bash: /home/richard/Downloads/make_isombr_part: cannot execute binary file:
> Exec format error
Can it be your system is equipped with Debian for architecture i386 ?
I forgot to mention that my system is amd64.
> O
On 03/28/2017 05:10 AM, Thomas Schmitt wrote:
[snip]
It would be interesting to see how various partition editors react on
this state of the USB stick. Can they reduce the size of partition 3 ?
Can they remove partition 3 and add on new one ?
That looked interesting. As I had a flash drive wi
Hi,
i wrote a small program which shall make a USB stick with isohybrid ISO
more digestible for partition editors by removing all partition tables
except MBR partitions.
It then creates a new partition in the first MBR partition slot which
is found with block count 0.
usage: ./make_isombr_part
Le 27/03/2017 à 20:11, David Christensen a écrit :
For example, here is an ADATA 4 marketing-GB USB flash drive:
(...)
Burning 10 MB using 'bs=1M':
2017-03-27 11:01:23 root@jesse ~
# time dd if=/dev/urandom of=/dev/sdb seek=3000 count=10 bs=1M && sync
10+0 records in
10+0 records out
10485760
Hi,
i wrote:
> > - APM partition table with block size 2048 (look here for a suspect !)
Pascal Hambourg wrote:
> For whatever reason, libarted-based tools choose to consider that bogus
> Apple partition table.
> Bottom line : libparted-based tools do not handle ISO-hybrid images
> correctly. Do n
Le 27/03/2017 à 14:11, Thomas Schmitt a écrit :
- APM partition table with block size 2048 (look here for a suspect !)
Right.
For whatever reason, libarted-based tools choose to consider that bogus
Apple partition table. Unlike fdisk, you cannot force it to use another
format.
Bottom line
On 03/27/2017 05:38 AM, Greg Wooledge wrote:
... the bs= option in dd. All that does is make the dd command run a
tiny bit faster or slower.
As I understand it, writes smaller than a flash page size cause the
flash drive firmware to fetch or erase an available page of flash,
combine the unmo
On 03/27/2017 04:45 AM, kAt wrote:
David Christensen:
Understand that many memstick images change once they have been
booted, so you must checksum them immediately after burning.
(Thankfully, debian-8.7.1-i386-xfce-CD-1.iso doesn't, so I can verify
my USB flash drive at any time.)
I have done
Hi,
Greg Wooledge wrote:
> If the disk-image came
> from a 4 GB disk, and you write it onto an 8 GB disk, then the 8 GB
> disk will *believe* that it is a 4 GB disk, because it has the metadata
> from a 4 GB disk.
The device size is not determined by the image data which get written to it.
I assu
On Mon, Mar 27, 2017 at 11:45:00AM +, kAt wrote:
> Yes, all this was done, the image on the stick is fine and functional!
> I did not say there was a problem with it, but the rest of the unused
> space ob the disk/mem-stick
When you write a disk-image onto a "disk" (in this case, a USB mass
st
Hi,
my hand made partition 3 fell victim to the deceptions of nested
partitions. It starts inside the ISO after the end of partition 2.
It should of course start after the end of partition 1.
So this is not the right start of partition 3:
> Device Boot Start End Sectors Size Id Typ
On Monday, March 27, 2017 07:45:00 AM kAt wrote:
> Again the question is not so much at the vendor's magic system but why
> would a 0.6G image rent the rest of the disk useless for copying stuff
> in and out, which I have done with many live systems.
To me this is not an unexpected result. I don'
Hi,
kAt wrote:
> >> Disk /dev/sdb: 7.2 GiB, 7751073792 bytes, 15138816 sectors
> [...]
> I suppose this is normal for an 8Gb usb stick. 249Mb go to firmware that
> operates the stick
Hardly. Unless it is an operating-system-on-a-stick.
The habit on the storage sector is to count by SI compli
David Christensen:
> uname -a
>Always start a new thread with these:
2017-03-26 19:50:42 dpchrist@jesse ~
$ cat /etc/debian_version
9.0
$ uname -a
Linux debian9 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64
GNU/Linux
>Also, please post the URL for image.iso/Rescatux 4.0beta.
http://ww
Thomas Schmitt:
> Hi,
>
> kAt wrote:
>>> /sbin/fdisk -l /dev/sdb
>> Disk /dev/sdb: 7.2 GiB, 7751073792 bytes, 15138816 sectors
>
> Is this about the correct size of the stick ?
I suppose this is normal for an 8Gb usb stick. 249Mb go to firmware that
operates the stick I wouldn't know.
>> U
Thomas Schmitt:
> Hi,
>
> kAt wrote:
>>> /sbin/fdisk -l /dev/sdb
>> Disk /dev/sdb: 7.2 GiB, 7751073792 bytes, 15138816 sectors
>
> Is this about the correct size of the stick ?
I suppose this is normal for an 8Gb usb stick. 249Mb go to firmware that
operates the stick I wouldn't know.
>> Uni
On 03/26/2017 10:18 AM, kAt wrote:
dd if=/media/--/image.iso of=/dev/sdb bs=4M; sync
the image works but the format of the drive seems false gparted when
starting says that linux thinks it is a 256k block and not the 4m it
indicates. It shows on an 8G drive an empty space of 28G
Is it the
Hi,
kAt wrote:
> > /sbin/fdisk -l /dev/sdb
> Disk /dev/sdb: 7.2 GiB, 7751073792 bytes, 15138816 sectors
Is this about the correct size of the stick ?
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 byt
Hi,
kAt wrote:
> dd if=/media/--/image.iso of=/dev/sdb bs=4M; sync
> the image works but the format of the drive seems false
The dd option "bs=" has no influence on the block size or other
drive properties as perceived by a partition editor.
> gparted when starting says that linux thinks it
kAt:
> dd if=/media/--/image.iso of=/dev/sdb bs=4M; sync
>
> the image works but the format of the drive seems false
> gparted when starting says that linux thinks it is a 256k block and not
> the 4m it indicates. It shows on an 8G drive an empty space of 28G
>
> Is it the option of bs=4M
On 03/26/2017 12:18 PM, kAt wrote:
dd if=/media/--/image.iso of=/dev/sdb bs=4M; sync
the image works but the format of the drive seems false
gparted when starting says that linux thinks it is a 256k block and not
the 4m it indicates. It shows on an 8G drive an empty space of 28G
Is it the
"dd ... bs=4M" doesn't change the block size of the underlying device.
All it does is say that dd should copy in chunks of 4Mb. If the buffer
size is bigger, then dd spends more time copying and less time telling
the kernel to copy.
On 26/03/17 18:18, kAt wrote:
> dd if=/media/--/image.iso of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 12, 2016 at 01:25:50PM -0600, Richard Owlett wrote:
> On 11/12/2016 12:26 PM, Pascal Hambourg wrote:
> >Le 12/11/2016 à 18:22, Richard Owlett a écrit :
> >>
> ddrescue /dev/sda /mnt/defective_drive.img
> /mnt/defective_drive.log
> >
On Sun 13 Nov 2016 at 08:54:05 +1300, Ben Caradoc-Davies wrote:
> On 13/11/16 08:25, Richard Owlett wrote:
> >I've gone to lenghts to defeat Debian's attempts to out-M$ Wm Gates.
>
> Redmond is now our ally against the closed garden at Cupertino, with cloud
> image support, open-sourced language
On 13/11/16 08:25, Richard Owlett wrote:
I've gone to lenghts to defeat Debian's attempts to out-M$ Wm Gates.
Redmond is now our ally against the closed garden at Cupertino, with
cloud image support, open-sourced language platforms, and even Ubuntu
integration on the desktop.
We've always b
On 11/12/2016 12:26 PM, Pascal Hambourg wrote:
Le 12/11/2016 à 18:22, Richard Owlett a écrit :
ddrescue /dev/sda /mnt/defective_drive.img
/mnt/defective_drive.log
(...)
Can this be run as a user, or are root permissions required.
Unless the user has read permission on the raw device, it mu
Le 12/11/2016 à 18:22, Richard Owlett a écrit :
ddrescue /dev/sda /mnt/defective_drive.img /mnt/defective_drive.log
(...)
Can this be run as a user, or are root permissions required.
Unless the user has read permission on the raw device, it must be run as
root.
My defective drive is /de
On 11/12/2016 2:29 AM, Richard Owlett wrote:
On 11/12/2016 1:31 AM, Christian Seiler wrote:
On 11/11/2016 10:38 PM, Richard Owlett wrote:
I was wondering about that.
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
is
not first time user friendly. Will re-read after a good nigh
On 11/11/2016 10:45 PM, Andy Smith wrote:
Hi Richard,
On Fri, Nov 11, 2016 at 03:31:21PM -0600, Richard Owlett wrote:
How big might the logfile be when trying to recover a known flaky 300
GB drive. I've lots of space? Some convienient, some not.
TL;DR: this depends on how many bad sectors you
On 11/11/2016 10:38 PM, Richard Owlett wrote:
> I was wondering about that.
> https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html is
> not first time user friendly. Will re-read after a good night's
> sleep. Will also look for appropriate tutorials. Suggestions?
Well, I would sugges
Hi Richard,
On Fri, Nov 11, 2016 at 03:31:21PM -0600, Richard Owlett wrote:
> How big might the logfile be when trying to recover a known flaky 300
> GB drive. I've lots of space? Some convienient, some not.
TL;DR: this depends on how many bad sectors you expect to find. If
the number is likely t
On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
> I had been removed after becoming unreliable.
Sorry to hear that. Advanced years don't come on their own, do they?
(Sorry, couldn't resist it)
On 11/11/2016 11:49 AM, Nicolas George wrote:
Le primidi 21 brumaire, an CCXXV, Andy Smith a écrit :
You are better off using GNU ddrescue for taking images of
possibly-failing devices.
IIRC, there is a catch there: there is another program with a very
similar name that does not work the same
On 11/11/2016 12:13 PM, The Wanderer wrote:
On 2016-11-11 at 12:37, Christian Seiler wrote:
Hi,
Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith
:
Hi Richard,
On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
I was considering using dd to copy the entire drive to a
*SIN
On 2016-11-11 at 12:37, Christian Seiler wrote:
> Hi,
>
> Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith
> :
>
>> Hi Richard,
>>
>> On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
>>
>>> I was considering using dd to copy the entire drive to a
>>> *SINGLE* partition of a
Le primidi 21 brumaire, an CCXXV, Andy Smith a écrit :
> You are better off using GNU ddrescue for taking images of
> possibly-failing devices.
IIRC, there is a catch there: there is another program with a very
similar name that does not work the same way. Be careful when installing
it.
> Amongst
Hi,
Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith :
>Hi Richard,
>
>On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
>> I was considering using dd to copy the entire drive to a *SINGLE*
>> partition of a 1 TB drive with the intention making a "byte perfect"
>> of of the defe
Hi Richard,
On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
> I was considering using dd to copy the entire drive to a *SINGLE*
> partition of a 1 TB drive with the intention making a "byte perfect"
> of of the defective drive to a new 300 GB drive at a later time to
> then attempt
On 08/12/2014 08:35 PM, Stephen Powell wrote:
On Tue, 12 Aug 2014 15:19:16 -0400 (EDT), Martin Smith wrote:
On 11/08/2014 12:16, Stephen Powell wrote:
On Mon, 11 Aug 2014 01:15:31 -0400 (EDT), Reco wrote:
...
cp -a /var/www/* /media/lin50
This may work if there are no "hidden" files in the d
On Tue, 12 Aug 2014 15:19:16 -0400 (EDT), Martin Smith wrote:
> On 11/08/2014 12:16, Stephen Powell wrote:
>> On Mon, 11 Aug 2014 01:15:31 -0400 (EDT), Reco wrote:
>>> ...
>>> cp -a /var/www/* /media/lin50
>>
>> This may work if there are no "hidden" files in the directory (files whose
>> names be
On 11/08/2014 12:16, Stephen Powell wrote:
On Mon, 11 Aug 2014 01:15:31 -0400 (EDT), Reco wrote:
While dd can be used to copy a directory, it cannot be used alone for
this task. Try this:
...
cp -a /var/www/* /media/lin50
This may work if there are no "hidden" files in the directory (files wh
On Mon, 11 Aug 2014 01:15:31 -0400 (EDT), Reco wrote:
>
> While dd can be used to copy a directory, it cannot be used alone for
> this task. Try this:
>
> ...
>
> cp -a /var/www/* /media/lin50
This may work if there are no "hidden" files in the directory (files whose
names begin with a period), an
On 11/08/14 05:48, Ethan Rosenberg wrote:
Dear List -
I am having trouble w/ dd. I am sure that it is probably a stupid mistake.
Anyway..,.
/dev/sdb [500 G external USB drive] has one partition /dev/sdb1 which is
mounted on /media/lin50
I wish to copy /var/www to the USB drive.
I have tried
Hi.
On Mon, 11 Aug 2014 00:48:29 -0400
Ethan Rosenberg wrote:
> Dear List -
>
> I am having trouble w/ dd. I am sure that it is probably a stupid mistake.
You've made four mistakes indeed.
> root@meow:/var# dd if=/var/www of=/dev/sdb1/ bs=2048
> dd: failed to open ‘/dev/sdb1/’: Is a direc
On 07/15/14 16:37, Jonathan Dowland wrote:
On Tue, Jul 15, 2014 at 03:14:47PM +0200, Christian Groessler wrote:
the final output of 'dd' is in "SI mode" (or how to call it). It
uses 10^6 instead of 2^20 for "megabyte".
...
Is there a switch to display in "traditional" units
Not in dd itself,
On Tue, Jul 15, 2014 at 03:14:47PM +0200, Christian Groessler wrote:
> the final output of 'dd' is in "SI mode" (or how to call it). It
> uses 10^6 instead of 2^20 for "megabyte".
...
> Is there a switch to display in "traditional" units
Not in dd itself, afaik.
Recent-ish coreutils versions have
El 2012-08-05 a las 17:47 -0700, Fnzh Xx escribió:
(sending back to the list)
> On Sun, 05 Aug 2012 02:28:22 -0700, Fnzh Xx wrote:
>
> (please, no html posts, thanks)
>
> > root@debian:/home/tiger# dd if=/dev/sda of=/dev/sdb bs=10240k
> > 11447+1 records in
> > 11447+1 records out
> > 12003
On Mon, Aug 6, 2012 at 12:50 AM, Bob Proulx wrote:
> Fnzh Xx wrote:
>>
>> root@debian:/home/tiger# dd if=/dev/sda of=/dev/sdb bs=10240k
>> 11447+1 records in
>> 11447+1 records out
>> 120034123776 bytes (120 GB) copied, 4729.59 s, 25.4 MB/s
>> root@debian:/home/tiger# blkid
>> ...
>> why /dev/s
1 - 100 of 212 matches
Mail list logo
