On Mon, Apr 25, 2011, at 12:04:41 +0200, Klistvud wrote:
> Hmm, perhaps your live system is performing some disk writes *while*
> your dd is doing its thing, thus effectively overwriting
> (corrupting) some sectors already written by dd?
All of the OS versions I was trying in my test environment
On Mon, Apr 25, 2011, at 10:09:58 +0200, Klistvud wrote:
> It would seem we're finally getting somewhere. This should be fairly
> easy to test, namely: performing dd on an *unmounted* (not live)
> system and seeing if it finally works.
Yes, I tried this yesterday. Using dd to write the image to
On Mon, Apr 25, 2011, at 11:02:40 +0800, Huang, Tao wrote:
> to my understanding, writing with dd on a mounted device leads to
> unpredictable results, and never guarantees to work.
I understand what you mean but it does work 100% of the time on the
versions I mentioned including Lenny, just not E
On Mon, Apr 25, 2011, at 09:45:44 +0800, Huang, Tao wrote:
> what do u mean by "live running file system"?
> a mounted file system?
Yes. Debian is installed and running on sda and I am trying to
overwrite the current installation with this disk image.
Thanks,
-Mark
--
To UNSUBSCRIBE, email to
On Sun, Apr 24, 2011, at 22:54:48 +0800, Huang, Tao wrote:
> what about a binary diff on those two written images.
>
> i guess the difference should be at the beginning / end of the device.
> just diff their hex value instead of a real binary diff.
> try
>
> $ dd if=/dev/sda bs=1024 count=1 | hex
On Sat, Apr 23, 2011, at 21:49:39 +0900, Osamu Aoki wrote:
> What was the size of image.img in exact bytes? What happened if you
> specified exact image size via "count"? What happened if bs=1024?
The size of image.img is 31457280 bytes. I have tried several ways
below and listed in parentheses w
On Wed, Apr 13, 2011, at 07:13:13 -0500, Mark Kane wrote:
> One thing to add is that the documentation I'm going off of was
> written back in 2008 and specifically mentions doing this
> successfully from Linux (though not sure which distro the author had
> used). I would think
On Wed, Apr 13, 2011, at 21:19:43 +1000, Scott Ferguson wrote:
> Upon reflection I'd be willing to bet it's down to the difference
> between versions of coreutils - there's a couple of minor changes up
> until 8.9 (according to NEWS). While most of the changes I've read
> about improve speed and re
On Wed, Apr 13, 2011, at 14:33:34 +1000, Scott Ferguson wrote:
> It's possible the script uses ddrescue instead of dd to create the
> image
> - though I still don't understand why that would make a difference.
I could be wrong, but from looking at the script a bit it looks like dd
is used to creat
On Wed, Apr 13, 2011, at 10:54:46 +1000, Scott Ferguson wrote:
> What commands did you use to create the original image?
>
> If image.img was created by simply:-
> dd if=/dev/sda of=/image.img
> then bs is unnecessary.
I did not create the image directly using dd but rather used a script
which ma
On Tue, Apr 12, 2011, at 19:13:39 +0200, Klistvud wrote:
> Perhaps GRUB/LILO just doesn't find it? Additionally -- and I may be
> off target here -- shouldn't that be 'of=/dev/sdax' (a partition, not
> a device)?
Hi and thanks for the reply.
I should have mentioned this in my original message,
Hi everyone,
I'm trying to write a bootable disk image to a hard drive using dd in
Debian like so:
dd if=image.img of=/dev/sda bs=1M
dd completes without error and appears to have written this
successfully, however when trying to boot from sda the operating system
does not boot properly as if th
ution. I currently use Firefox and Thunderbird and
Open Office with Trend Micro as the firewall.
Thank you
Anthony Kane
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
work, although a little more dated still retains that sense of musical
intelligence.
IOW, Once again, I looked to Alan for help.
it comes to the real world possibility of artificial intelligence and
harnessing .
well known for their superior intelligence and complex social systems,
are thought to
I'm new to debian itself, and seem to be having a problem with regard
to modules.
I've succesfully compiled and booted with kernel 2.4.12 without a
problem. The issue I have is with missing modules.
I've done a 'make modules' and 'make modules_install' but upon
reboot, the system is unable to
I had this running beautifully on ReHad 6.1 and FreeBSD 3.2 before I moved my
own box from RedHat to FreeBSD.
--cokane
Thomas Keusch had the audacity to say:
> Hello,
>
> does anybody happen to be running NFS between FreeBSD und Linux
> successfully and painless?
>
> I've got FreeBSD 3.4S cvsupp
Matthias Murra
> Hope this has helped to make my point a bit clearer. :-)
Indeed. As it turns out, my CD file hierarchy is all messed up so it is
_impossible_ to install right now. Thanks anyway!
- d.
Karl J Klug wrote:
> HmI don't know Can you pass the geometry to the kernel? If
> the boot messages show the correct C/H/S geometry, then the problem is
> with cfdisk, I guess. There's probably a way to force fdisk to use a
> particular geometry, but I've never tried it. Try looking
Matthias Murra wrote:
> Your BIOS shouldn't be a problem then. Have you checked the BIOS
> settings?
Yeah, all the settings are Linux-friendly.
> How come? I simply created a partition that would hold the basic Debian
> slink system on the "8.4 GB drive" that cfdisk detected in conjunction
> with
Matthias Murra wrote:
> I guess you're using a motherboard with a not-so-recent BIOS (like mine,
> which is from 1997) and a 2.0.x kernel.
My BIOS is dated 6/8/99 and the Official CD, which I am trying to install
from, uses a 2.0.36 kernel.
> Please see the Large Disk Mini HOWTO on details concer
Karl J Klug wrote:
> I think this is the drive that was in the Thinkpad we installed Linux on.
> We used
>
> 1825/240/63
>
> for the parameters.
I tried, but not matter what I entered, it kept seeing 1024/240/63. As a
test of sorts, I tried to install FreeBSD and it came off without a hitch.
Wha
Karl J Klug wrote:
> Look at the disk settings in your BIOS to see what C/H/S settings are
> being used. If you can figure out what disk you have you can get
> the real C/H/S settings from the manufacturers web site.
My BIOS won't tell me what C/H/S settings are being used, just size in MB,
but I
Karl J Klug wrote:
> Specify disk geometry when you boot:
Is there a way to find out what disk geometry to specify?
Why isn't it detected correctly / why is it detected incorrectly?
Thanks in advance!
- d.
I am trying to install Debian GNU/Linux 2.1 on a Dell Inspiron 7000 with a
14.1GB hard drive. Currently, Win98 has half of it and I am hoping to give
Linux the other half. During the partitioning part of the installation
process, however, cfdisk tells me, "yes, Win98 has a 6740MB partition, but
t
MRCE wrote:
> Not a very sophisticated question, but does anyone know how
> to stop the beep that comes with every keystroke on the WYSE-50
> dummy terminal?
I guess the not-very-sophisticated answer would be to rip out it's
speaker.
- d.
Gang:
I have started to install Linux using dselect and the cd-rom method. On
the menu when I select [A]cess and select cd-rom it puts me in a screen
that asks for a block device name
What is this? I haven't found anything in any of the instructions that
tells me what to do with this. I can't mo
I am a fairly new Linux user with a question concerning using
startx from a user account. When I try to execute startx from a user
account, I get the message:
xf86OpenConsole:Server must be running with root permissions
You should be using Xwrapper to start the server or xdm. We strongly
In article <[EMAIL PROTECTED]> you write:
>[EMAIL PROTECTED] (Jim Lynch)
>>
>> Did you try /dev/sr0 ???
>
>Thanks for responding. I guess that boot-up message and devices list
>should have given me a clue.
>
>There is no /dev/sr0, so I used mknod to make one doing
>
>mknod sr0 b 11 0
>
>I then
[EMAIL PROTECTED] (Jim Lynch)
>
> Did you try /dev/sr0 ???
Thanks for responding. I guess that boot-up message and devices list
should have given me a clue.
There is no /dev/sr0, so I used mknod to make one doing
mknod sr0 b 11 0
I then did
mount -t iso9660 -r /dev/sr0 /cdrom
and got the
I have a SCSI cd-rom drive attached to an AHA-2940U controller. The boot
disk on the same controller is device 0 while the cd drive is device 3. My
machine boots fine off of the disk and it used to mount cd-roms without
trouble. At some point it stopped being able to do so:
spasm:/proc# mount -t
30 matches
Mail list logo
