The 2 GB limit is irrelevant of file system. dd doesn't know about or
care about file systems. So creating another partition with another file
system would have no affect on dd. Block size is not the same as
volume/partition size. The volume size is the block size times the
number of blocks.
Usb-creator is just a script. It is quite easy to just apply the patch
from https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/321544
to the text file. If you don't feel comfortable doing that. Then you can
manually just find and change 2 lines. It is quite easy. Here are the
relevant
I didn't actually apply these patches directly. I updated mine (0.1.15)
manually. Read the man page of dd. The size of the file that dd creates
is equal to the product of the blocksize and the count. In the 0.1.11
the block size is 1 byte and the count is 'persist' (ie the number of
bytes you
Sorry I missed that comment, I responded in that thread:
https://bugs.launchpad.net/ubuntu/+source/usb-
creator/+bug/321544/comments/11
To repspond to Pi Boy any changes you make to usb-creator will just be
overwritten during the update. It will replace the script with the new
one in the updated
You guys can easily fix your problem by applying the patch in the bug I
linked to above: https://bugs.launchpad.net/ubuntu/+source/usb-
creator/+bug/321544. If you have the 2 GB (2048 MB) limit it is because
usb-creator is telling dd to make a single block that is 2048 MB.
However, dd will only
Blocksize is not the same as volume/partition/file size
(http://en.wikipedia.org/wiki/Block_%28data_storage%29). A file system
usually has a block size associated with it. In general terms, when data
is pulled off the device it will usually pull off the whole block at the
same time. Since related
This is still a problem. In my case it is definitely an issue with the
file size limitations of vfat. I tried to make a persistent usb with
jaunty 9.04 beta DVD. Everything went fine and no errors were reported.
The usb boots up fine but nothing is persistent across reboots. I went
ahead and tried
I think the original bug report may be the same problem as
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/284085. If
the usb is using FAT32 (aka vfat) then there is a 4 GB file size
limitation, that can cause problems when creating a file casper-rw file
that is too big. The casper-rw
This may be because vfat has a file size limitation of 4 GB. That is why
it worked on your smaller 4 GB flash drive but failed on your larger
drive when you tried to make the 7 GB file. Check the casper folder on
your usb drive and see if there is a casper-rw file. If not then that is
your
I am using the jaunty 9.04 beta live DVD to create a persistent USB
stick. Usb-creator is trying to create a single large block and is
failing as a result. Block sizes = 2G aren't allowed by dd. Here is the
error in my .usb-creator.log when I tried to create a 3.9 GB file:
['dd', 'if=/dev/zero',
I have tracked down a more serious problem. The current version of usb-
creator in jaunty beta tries to create the casper-rw file as one large
block, when actually it should use a reasonable block size like 1k and
then create right number of blocks. This is what is causing the dd:
invalid number
I have tracked down a more serious problem. The current version of usb-
creator in jaunty beta tries to create the casper-rw file as one large
block, when actually it should use a reasonable block size like 1k and
then create right number of blocks. This is what is causing the dd:
invalid number
I have tracked down the root of the problem. Usb-creator in jaunty beta
tries to create the casper-rw file as one large block. Notice the
count=1 in the dd command. Actually it should use a reasonable block
size like 1k and then create right number of blocks. Block sizes = 2GB
aren't allowed by
Public bug reported:
Binary package hint: usb-creator
I am using usb-creator 0.1.15 from the jaunty 9.04 beta DVD. I get dd:
invalid number errors in .usb-creator.log file. I thought it was a
limitation of vfat file system, but I tested it by using dd
if=/dev/zeros of=/dev/null and it seems like
They will have to stick with FAT because that is what syslinux supports.
All modern file sytems including ntfs and ext3 already support files
larger than 4 GB. This most recent issue I brought up was the block size
which is different than the file size.
--
No persistence with USB Creator in
Adding the link to update-initramfs is working for me. However I would
like to update my kernel. As Colin said update-initramfs should update
the real kernel that is located in /cdrom. I was wondering how to go
about doing this manually until things are fixed. I tried copying
vmlinuz and
*** This bug is a duplicate of bug 151536 ***
https://bugs.launchpad.net/bugs/151536
evolution-data-server is eating up all of my spare CPU cycles and it is
making my mythtv unable to playback smoothly. Please fix this or post a
work around.
--
evolution-data-server-2.22 high cpu
17 matches
Mail list logo
