I see a few posts online up to as late as 2014 about this.
Brasero doesn't see my external usb drive either but I'd be surprised if it is still not working since then.
Do I need to mount the drive? This drive coexists on my system with an usb backup drive.
Thanks for any help.
Well the much maligned Windows system can detect a blank disk in this very same external drive & automatically open burner software ready to select a path for burning an iso file.It's a CD/DVD burner, why would it need to detect an external HDD?
The below df cmd says the drive is already mounted & Brasero records the iso file I want to write but it can't see a a disk to write it to? Help please.If you want to add files from your usb device then i think you need to go the path where you have mounted your usb device.
If you dont know where your usb device is mounted then use the df command.
df
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/ada0p2 1885047176 25439456 1708803952 1% /
devfs 2 2 0 100% /dev
procfs 8 8 0 100% /proc
/dev/gptid/2f1fb21a-e6a2-11e9-99ba-00d8615800d0 605494576 169806008 387249008 30% /media/disk
I assume you are refering by usb drive to the external USB CD/DVD burner. It might lead to misunderstanding not to refer to it directly, as seen at the above responses.Brasero doesn't see my external usb drive ...
camcontrol devlist
.................. (pass1,cd0)
link cd0 cdrom
link cd0 dvd
perm cd0 0660
perm pass1 0660
perm xpt0 0666
pw groupmod operator -m dalpets
shutdown -r now
I assume you are refering by usb drive to the external USB CD/DVD burner. It might lead to misunderstanding not to refer to it directly, as seen at the above responses.
To gain access to the USB CD/DVD burner you need to permit read, write to the device. Check the device information by running as root
camcontrol devlist
See which device information is displayed,ex:
.................. (pass1,cd0)
Change accordingly to obtained device information, edit:
/etc/devfs.conf
Code:link cd0 cdrom link cd0 dvd perm cd0 0660 perm pass1 0660 perm xpt0 0666
/dev/cd0 has owner|group root|operator. Add the user to the operator group.
pw groupmod operator -m dalpets
Reboot system:
shutdown -r now
root@FreeBSD11:/home/Brenton # camcontrol devlist
<WDC WD10EFRX-68FYTN0 82.00A82> at scbus2 target 0 lun 0 (pass0,ada0)
<AHCI SGPIO Enclosure 1.00 0001> at scbus6 target 0 lun 0 (ses0,pass1)
<Slimtype eSAU208 4 NL01> at scbus7 target 0 lun 0 (pass2,cd0)
root@FreeBSD11:/home/Brenton # ee /etc/devfs
In the example in my last posting I omitted the device type naming,scbus, target, lun from the camcontrol command output and wrote only what is important.I was expecting to see something like your example
As root:<Slimtype eSAU208 4 NL01> at scbus7 target 0 lun 0 (pass2,cd0)
ee /etc/devfs.conf
link cd0 cdrom
link cd0 dvd
perm cd0 0660
perm pass0 0660
perm pass1 0660
perm pass2 0660
perm pass3 0660
perm xpt0 0666
pw groupmod operator -m dalpets
(replace dalpets with the actual users name), execute shutdown -r now
. The disc to write in Brasero should be availaible now.My pleasure.Thank you for your continued help.
root@FreeBSD11:/home/Brenton # fsck
** /dev/ada0p2 (NO WRITE)
USE JOURNAL? no
** Skipping journal, falling through to full fsck
SETTING DIRTY FLAG IN READ_ONLY MODE
UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=88685111 (48 should be 16)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=87816917 OWNER=Brenton MODE=100644
SIZE=9340 MTIME=Nov 4 02:37 2019
CLEAR? no
UNREF FILE I=87816992 OWNER=Brenton MODE=100644
SIZE=9340 MTIME=Nov 4 02:34 2019
CLEAR? no
UNREF FILE I=88686023 OWNER=Brenton MODE=100600
SIZE=2 MTIME=Nov 4 02:37 2019
CLEAR? no
UNREF FILE I=88686025 OWNER=Brenton MODE=100600
SIZE=2 MTIME=Nov 4 02:37 2019
CLEAR? no
UNREF FILE I=88766833 OWNER=Brenton MODE=100640
SIZE=0 MTIME=Nov 4 02:37 2019
CLEAR? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
443244 files, 3179943 used, 232450949 free (53821 frags, 29049641 blocks, 0.0% fragmentation)
tingo@kg-core2$ file ~/dl/bsd/fbsd/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso
/home/tingo/dl/bsd/fbsd/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso: ISO 9660 CD-ROM filesystem data 'FREEBSD_INSTALL' (bootable)
xorriso -devices
-----------------------------------------------------------------------------
0 -dev '/dev/cd0' rwrwr- : 'TSSTcorp' 'CDDVDW SH-S223B'
1 -dev '/dev/cd1' rwrwr- : 'TSSTcorp' 'DVD-ROM SH-D162C'
-----------------------------------------------------------------------------
xorriso -outdev /dev/cd0 -toc
Drive current: -outdev '/dev/cd0'
Media current: DVD+R
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
Drive current: -outdev '/dev/cd0'
Drive access : exclusive:unrestricted
Drive type : vendor 'TSSTcorp' product 'CDDVDW SH-S223B' revision 'SB02'
Drive id : 'Q9146GBSA0823200'
Media current: DVD+R
Media product: MCC/004/48 , Mitsubishi Chemical Corporation
Media status : is blank
Media blocks : 0 readable , 2295104 writable , 2295104 overall
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
xorriso -as cdrecord -v -eject dev=/dev/cd0 ~/dl/bsd/fbsd/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso
.I am a relative newcomer to all of this, so some detail may not make sense unless elucidation is given on the "howto". Thank you for that.Hmm, maybe it is something I or you don't understand here. ada0p2 is a partition on a hard drive. An ISO image is a file which the file(1) command can identify, like this
And where (which device name) is your CD / DVD burner in all this? It is supposed to be /dev/cd0 or something like it.Code:tingo@kg-core2$ file ~/dl/bsd/fbsd/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso /home/tingo/dl/bsd/fbsd/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso: ISO 9660 CD-ROM filesystem data 'FREEBSD_INSTALL' (bootable)
You are trying to burn from an ISO image (a file) to media (a recordable CD or DVD) in your CD /DVD burner right?
(for completeness: an ISO image covers a whole device, partition table and all, it can NOT be written to a partition on a device with a result that works)
Don't execute arbitrary commands you don't know if they are needed to be used or not. First put a diagnosis of the problem, then take action.root@FreeBSD11:/home/Brenton # fsck
Do you mean the burning (recording) process interrupts and the error message pops up, or does the error message appear from another action taken? Btw, are we talking here about burning DVD's or CD's?.... it creates an image checksum & indicates it is 'starting to record' but it goes no further.
I get the following error message.
What do you mean by "the burner ... will not boot an iso made on a windows machine"? What did you expect from Brasero to do with the windows made iso?The burner will not burn a disc & will not boot an iso made on a windows machine?
Hi,
i propose to inspect the problem by burn backends, rather than a GUI burner
or system management commands. I am developer of xorriso and could help with
interpreting its behavior.
E.g. list the recognizable and accessible drives by
Code:xorriso -devices
Do you mean the burning (recording) process interrupts and the error message pops up, or does the error message appear from another action taken? Btw, are we talking here about burning DVD's or CD's?Don't execute arbitrary commands you don't know if they are needed to be used or not. First put a diagnosis of the problem, then take action.
OK.
I assumed, without thinking, that ISO's by nature were not platform dependent. I understand better now!What do you mean by "the burner ... will not boot an iso made on a windows machine"? What did you expect from Brasero to do with the windows made iso?
All image types are platform neutral, as far as burning them to CD orThe burner will not burn a disc & will not boot an iso made on a windows machine?
[...]
i assumed, without thinking, that ISO's by nature were not platform dependant.
So what happened to this "cd0" ?Code:root@FreeBSD11:/home/Brenton # camcontrol devlist ... <Slimtype eSAU208 4 NL01> at scbus7 target 0 lun 0 (pass2,cd0)
Yes, a couple of usb3, but I am loathe to do so because moving them around can affect booting.Hi,
so the drive has indeed no separate power supply cable but pulls current
only from the USB interface ?
Does the computer have other USB sockets which you could try ?
Is the "maligned Windows system", for which it works, running on the same
computer hardware ?
I cannot find anything about inspecting system logs in
https://www.freebsd.org/doc/handbook/
So i ask Google and find the advise to read file
/var/log/messages
Have a nice day
Ahum ... https://www.freshports.org/sysutils/tkdvd ...TKDVD 4.0.9