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
Hi,
stan wrote:
> Or maybe it is researchers using the captcha to train their AI, and
> they just want more input? :-)
This suspicion is not new:
https://www.androidpolice.com/wp-content/uploads/2017/10/nexus2cee_xkcd-self-driving.png
Have a nice day :)
Thomas
Hi,
Tim wrote:
> Take it to a garage and give it an indirect blast of air
Well, as long as the miracle cure lasts, i will try not to stirr up
anything in the BD drive.
But i applied to the worn-off DVD drive a few blows from a borrowed
can of keyboard duster (half a pound of butane, ewww). Regr
Hi,
Steve Berg wrote:
> Get this with either one of my data BD-R's or a commercial bluray movie
> disk, Blade Runner in this case:
> libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT (+
> LOAD): [2 06 00] Drive not ready. No reference position found.
The drive does not like th
Hi,
Steve Berg wrote:
> I've got some data saved to blu-ray BD-R disks that won't read.
> [...] I'm positive it's a BluRay drive [...]
> Anyone have any idea what could cause this?
You should try to find out whether it is a problem of medium and drive
or of the potentially present filesystem.
In
Hi,
Andrew Wood wrote:
> Note that I'm not especially concerned with restoring the USB exactly - with
> all its partitions, etc.
In this case it seems consensus that you should wipe out its partition
table and create one that fits your intentions. E.g. one single partition
claiming the device up
Hi,
Samuel Sieb wrote:
> I was thinking that he had used one of the tools to
> create the live media, but that usually gives a mount point of "LIVE", so it
> likely was a straight write of the iso.
Oops. I did not consider unpacker/installer tools.
So Andrew Wood should better run something like
Hi,
Andrew Wood wrote:
> This leads me to wonder if I can simply rename the volume (is that
> the correct term?) to the previous name and then use Duplicity?
If the ISO was copied to the USB stick in a way that it can boot,
then the old partition table of the USB stick was overwritten at that
occ
Hi,
Andrew Wood wrote:
> > How do I restore the contents of the USB flash drive so that it has the
> > same contents as the /run/media/awood/7160-75C1 ??
Samuel Sieb wrote:
> sudo mkfs.fat -i 716075C1 /dev/sdb1
One will normally want to erase the partition table brought by the ISO
and instead cr
Hi,
ToddAndMargo wrote:
> > $ watch -n 2 "ls -al /lin-bak | grep -i OurStuff.tar | awk '{print $9, $5}'"
> > watch: failed to parse argument: 'ls -al /lin-bak | grep -i OurStuff.tar |
> > awk '{print , }'': Invalid argument
The problem is that the '-quotes, $9 and $5 are in "-quotes. The '-quote
Hi,
bruce wrote:
> now. I'm officially in the twilight zone...
> rsync -avz /home/test/cat/ test@192.168.125.133:/home/test/cat
> rsync -avz /home/test/cat/ test@192.168.125.133:/home/test/cat
> I'm wondering if there's some weird char being inserted..
In your mail these lines differ by th
Hi,
i wrote:
> > I still get
> > mount: /dev/loop0p1: can't read superblock
Sreyan Chakravarty wrote:
> May be I am doing something wrong.
Success by mistake is a classical pattern. :))
We will learn more when success vanishes righteously.
> I did not even know that USB sticks had a MBR part
Hi,
> 139255322 us [ 180481085 ]
This says that the run already lasted 180 seconds and the SCSI command
to which this line belongs lasted 139 seconds. (Your patience is in
good shape.)
> INQUIRY
There are only two of these commands in the course of normal drive
examination by libburn. So
Hi,
> But when I add an output device to the image like
> xorriso -indev test.iso \
> -boot_image any keep \
> -map "$file_or_tree_on_disk" "$path_in_iso" \
> -outdev test.iso
>
> Everything magically works.
> Weird.
Hm. This should yield the same result as -dev tes
Hi,
Sreyan Chakravarty wrote:
> Okay, so what you are doing is actually against convention.
It's fully compliant. Just moving apart the default mountable superblock
from the chain of session superblocks which need an extra option to
mount(8) in order to get mounted.
> Essentially, the OS assume
Hi,
Sreyan Chakravarty wrote:
> I am kind of confused as to the difference/advantage between keeping the old
> boot image versus rebuilding one.
My first multi-session proposal was to keep as much of the boot equipment
as possible.
After all, we began with the riddle why your genisoimage produced
Hi,
> 139255322 us [ 180481085 ]
This says that the run already lasted 180 seconds and the SCSI command
to which this line belongs lasted 139 seconds. (Your patience is in
good shape.)
> INQUIRY
There are only two of these commands in the course of normal drive
examination by libburn. So
Hi,
Tom Horsley wrote:
> My current theory is that it has something to do with
> the phase II region protection (which is supposed to be hardware
> rather than software)
That would be plausible.
But letting the drive hang on open with the need for power-off seems
to be a drastic reaction.
> It
Hi,
Tom Horsley wrote:
> I have a nice modern LG WH16NS40 Blu-ray rewriter [...]
> trying to rip a DVD [...]
> openat(AT_FDCWD, "/dev/sr0", O_RDONLY <-- never finishes till I unplug it
That's not usual. I have a BH16NS40 in a USB box from DeLOCK. No problems
to open it with any medium.
In gener
Hi,
i wrote falsely:
> $ sudo -P -f Fedora-Workstation-Live-x86_64-31-1.9.iso
That should of course have been a losetup run:
sudo losetup -P -f Fedora-Workstation-Live-x86_64-31-1.9.iso
Have a nice day :)
Thomas
___
users mailing list -- users@l
Hi,
Sreyan Chakravarty wrote:
> xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep
> -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
Looks ok. But see below for a variation that pleases GNOME Disks.
First some diagnosis:
> double clicking in GNOME File Manage
Hi,
i wrote:
> The resulting ISO will grow by the size of the whole ISO directory tree
> and the size of the data files which get added.
Clarification:
"size of the whole ISO directory tree" means the size of the meta-data,
not the size of the data files in the tree.
The meta-data in Fedora-Works
Hi,
Sreyan Chakravarty wrote:
> If someone asked you to create a custom Fedora ISO that you could use in
> VirtualBox/DVD/USB, what would you do ?
(As first i'd try what you did: Build a new ISO from the mounted original.
Then i'd try whether the original works in the test situation.
Then i'd i
Hi,
Sreyan Chakravarty wrote here:
> Its stuck at the bootmenu.
and at sysli...@syslinux.org:
> Unfortunately when I boot and press enter nothing happens.
So i assume you see an ISOLINUX menu with the labels you expect from your
isolinux.cfg file. (If not, then this would make much more sense to
Hi,
> I'm having trouble finding a good HOWTO for xorriso.
There are examples at the end of the man pages. Online:
https://www.gnu.org/software/xorriso/man_1_xorriso.html#EXAMPLES
https://www.gnu.org/software/xorriso/man_1_xorrisofs.html#EXAMPLES
https://www.gnu.org/software/xorriso/man_1_
Hi,
> I'm having trouble finding a good HOWTO for xorriso.
There are examples at the end of the man pages. Online:
https://www.gnu.org/software/xorriso/man_1_xorriso.html#EXAMPLES
https://www.gnu.org/software/xorriso/man_1_xorrisofs.html#EXAMPLES
https://www.gnu.org/software/xorriso/man_1_
Hi,
i wrote:
> > Afaik, K3B uses growisofs as burn backend. It formats BD-R media
> > by default,
Richard Shaw wrote:
> I'm assuming it can format on the fly? There was no "formatting" stage.
It does this automatically before writing begins. BD-R formatting does
not last long. Other than with B
Hi,
Richard Shaw wrote:
> I wanted to use libburn as the fork of the cdrecord apps are known toi
> have issues. Not sure what the problem was but after spinning up a bunch
> of times it just crapped out with an unhelpful error.
I'm the developer of libburn, which works underneath Xfburn, cdrskin,
Hi,
Richard Shaw wrote:
> To summarize the process:
I will keep this description for future use.
The UDF gap is a problem. I'd express my hope for implementation
if i was not myself among the candidates to try such an endeavor.
ECMA-167 and UDF 2.60 are available for free. They are just
awful to
Hi,
> On a side note cdrskin burned at 6X this time, not sure why...
I would guess that subtle timing effects are involved.
My workstation's USB shows similar symptoms with 16x DVD
(not on SATA, or on eSATA and USB of younger test machine).
Did you use dvd_obs=64k or stream_recording=on this tim
Hi,
> Will do, but I'm not sure when I'll have the need just yet.
No need to hurry.
I could try myself at the cost of wasted media and the risc
that my hardware and system differ too much from yours.
Kernel 2.6, burner at USB, ... several reasons why i might be
unable to reproduce.
So it is bette
Hi,
Richard Shaw wrote:
> cdrecord without was at 6X and cdrskin without at about 4X
Source code and man page of cdrskin indicate that a burn
run on BD-R has a transfer chunk size of 32 KiB if not
- option stream_recording=on is given
- or option dvd_obs=64k is given
- or ./configure option --ena
Hi,
> growisofs with defect management
> burned at about 3X, cdrecord without was at 6X and cdrskin without at
> about 4X.
I wonder why cdrskin could be slower. When all setups are made,
then it is only about banging out data chunks of 64 kB.
If the 4x speed is quite constant, then it might be a
Hi,
> Currently I have a blank BD-R disc in the drive but mount was still
> showing the previous disc volume label which is why xorriso was
> failing...
I always disliked the habit of growisofs to try unmounting
the drive before it begins to operate. umount is an admin job,
whereas burning is a u
Hi,
> So the "unformatted" one is pretty obvious which explains my first
> failure... but then I tried reducing the image using the 24756879360
> (24.8GB) size, which still failed. Should I assume then that failure
> was because growisofs reserved more spare space in its formatting
> than I allowe
Hi,
Richard Shaw wrote:
> When I use dvd+rw-mediainfo I see
> several different capacaities. Obviously if you use the formatting
> with defect management then you're going to loose some capacity, but
> the output is not clear which one is the correct.
You probably mean something like this:
Moun
Hi,
sorry for breaking the thread. I was not subscribed up to now
and did not yet find an archive that exposes message ids.
--
It is not that bad with Blu-ray. At least with the backends.
(I am the developer of libburn and use BD-R and
37 matches
Mail list logo
