Asunder problem

[Member roland]

I ran Asunder to copy the soundtracks on a cd to WAV files but all I got was the playlist file, the process finished very fast without creating any soundtrack files.

The preferences dialog indicates messages will be written to /var/log/asunder.log but I could find no such file, in fact the messages are written to /var/log/messages and in the log I found references to a missing module TOMOYO that seemed to cause the process to fail with every track processed and resulted in a error number 002.

Attempting to resolve it without bothering anyone I researched Asunder a little and decided to install tools-tomoyo (or similar name) which ran successfully.

Now my PC will boot but antiX will not load, it hangs with the messages you can see on the screen snapshot. I cannot even boot from the 19.3 dvd iso.

Because this install of 19.3 is not ´straight from the box´ I would like to undo the tools-tomoyo install I did rashly, has anyone any suggestions as to where I should start?

[Member roland]

Helpful

Up

0

::

sorry, would not load last time, too big maybe.

Attachments:

1. 

   DSC02029.jpg
   

[Member roland]

Helpful

Up

0

::

False alarm, typing ‘disable’ and enter results in a normal boot and I was then able to remove tomoyo-tools which I now learn is a MAC extension for security in Linux.

My remarks about Asunder still hold, it fails to write the WAV file requested, indeed the processing is so rapid it cannot have read the the cd track beyond whatever index data it may contain.

Has anyone met this problem before? I have used Asunder before and never had any problems.

[Anonymous]

Helpful

Up

0

::

sudo apt install wavpack

The asunder package accurately lists wavpack as a “recommends” item (vs “depends”)
and antiX default apt policy is (thankfully, IMO) configured to NOT automagically install “recommends”

[Member roland]

Helpful

Up

0

::

Is there anything else I might try?

roland@antix1:~
$ su
Password:
root@antix1:/home/roland# apt install wavpack
Reading package lists… Done
Building dependency tree
Reading state information… Done
wavpack is already the newest version (5.1.0-6).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@antix1:/home/roland# apt install flac
Reading package lists… Done
Building dependency tree
Reading state information… Done
flac is already the newest version (1.3.2-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@antix1:/home/roland# apt install lame
Reading package lists… Done
Building dependency tree
Reading state information… Done
lame is already the newest version (3.100-2+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@antix1:/home/roland#

• This reply was modified 2 years ago by roland.

[Anonymous]

Helpful

Up

0

::

Within asunder, visit Preferences } Advanced and enable logging.
Retry the operation then check the logfile to see if any error or debugging messages are provided.

[Member roland]

Helpful

Up

0

::

Job repeated with diagnostics as full as I could devise. I have used asunder many times with the same or very similar preferences and it always worked as expected. This is the first time I have used it on this particular build and with 19.3 installed, which is fully updated.

The following log is not written to the stated file /var/log/asunder.log, it appears in /var/log/messages which seems to be a generalised session log. I have edited out all but the first and last track fail messages to make it more readable. The entire rip process too only 10 seconds or so showing that the tracks were not being read through.

Thanks for your input with this problem.

May 8 12:11:51 antix1 asunder: Starting Asunder 2.9.3
May 8 12:11:51 antix1 asunder: Pixmap dir: /usr/share/pixmaps
May 8 12:11:51 antix1 asunder: using completion file name: /home/roland/.cache/asunder/asunder_album_artist
May 8 12:11:51 antix1 asunder: Reading completion data
May 8 12:11:51 antix1 asunder: using completion file name: /home/roland/.cache/asunder/asunder_album_title
May 8 12:11:51 antix1 asunder: Reading completion data
May 8 12:11:51 antix1 asunder: using completion file name: /home/roland/.cache/asunder/asunder_album_genre
May 8 12:11:51 antix1 asunder: Reading completion data
May 8 12:11:51 antix1 asunder: starting track: 1, ending track: 20
May 8 12:11:52 antix1 asunder: read_disc: discid=1d103614
May 8 12:11:52 antix1 asunder: update_tracklist() disk ‘1d103614’ ‘(null)’ ‘(null)’ ‘(null)’
May 8 12:11:52 antix1 asunder: Found 0 CDDB matches
May 8 12:13:29 antix1 kernel: [ 998.077832] r8169 0000:08:00.0: invalid large VPD tag 7f at offset 0
May 8 12:13:30 antix1 kernel: [ 998.144100] r8169 0000:0b:00.0: invalid large VPD tag 7f at offset 0
May 8 12:13:37 antix1 kernel: [ 1005.632411] ACPI: \: failed to evaluate _DSM (0x1001)
May 8 12:13:54 antix1 kernel: [ 1022.713576] ACPI: \: failed to evaluate _DSM (0x1001)
May 8 12:13:58 antix1 kernel: [ 1026.140348] wlan1: authenticate with dc:f8:b9:9a:9a:77
May 8 12:13:58 antix1 kernel: [ 1026.143235] wlan1: send auth to dc:f8:b9:9a:9a:77 (try 1/3)
May 8 12:13:58 antix1 kernel: [ 1026.176803] wlan1: authenticated
May 8 12:13:58 antix1 kernel: [ 1026.178121] wlan1: associate with dc:f8:b9:9a:9a:77 (try 1/3)
May 8 12:13:58 antix1 kernel: [ 1026.188476] wlan1: RX AssocResp from dc:f8:b9:9a:9a:77 (capab=0x431 status=0 aid=1)
May 8 12:13:58 antix1 kernel: [ 1026.193426] wlan1: associated
May 8 12:13:58 antix1 kernel: [ 1026.216632] wlan1: disassociated from dc:f8:b9:9a:9a:77 (Reason: 2=PREV_AUTH_NOT_VALID)
May 8 12:14:09 antix1 kernel: [ 1037.785284] wlan1: authenticate with dc:f8:b9:9a:9a:78
May 8 12:14:09 antix1 kernel: [ 1037.789324] wlan1: send auth to dc:f8:b9:9a:9a:78 (try 1/3)
May 8 12:14:09 antix1 kernel: [ 1037.816722] wlan1: authenticated
May 8 12:14:09 antix1 kernel: [ 1037.818135] wlan1: associate with dc:f8:b9:9a:9a:78 (try 1/3)
May 8 12:14:09 antix1 kernel: [ 1037.820219] wlan1: RX AssocResp from dc:f8:b9:9a:9a:78 (capab=0x411 status=0 aid=1)
May 8 12:14:09 antix1 kernel: [ 1037.824968] wlan1: associated
May 8 12:14:09 antix1 kernel: [ 1037.828187] wlan1: disassociated from dc:f8:b9:9a:9a:78 (Reason: 2=PREV_AUTH_NOT_VALID)
May 8 12:14:32 antix1 kernel: [ 1060.928475] wlan1: authenticate with dc:f8:b9:9a:9a:77
May 8 12:14:32 antix1 kernel: [ 1060.931007] wlan1: send auth to dc:f8:b9:9a:9a:77 (try 1/3)
May 8 12:14:32 antix1 kernel: [ 1060.959601] wlan1: authenticated
May 8 12:14:32 antix1 kernel: [ 1060.960075] wlan1: associate with dc:f8:b9:9a:9a:77 (try 1/3)
May 8 12:14:32 antix1 kernel: [ 1060.967821] wlan1: RX AssocResp from dc:f8:b9:9a:9a:77 (capab=0x431 status=0 aid=1)
May 8 12:14:32 antix1 kernel: [ 1060.972999] wlan1: associated
May 8 12:14:32 antix1 kernel: [ 1061.029731] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
May 8 12:15:10 antix1 kernel: [ 1098.576790] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:15:50 antix1 kernel: [ 1138.583593] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:16:30 antix1 kernel: [ 1178.572873] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:17:10 antix1 kernel: [ 1218.561942] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:17:50 antix1 kernel: [ 1258.550930] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:17:58 antix1 asunder: Saving configuration
May 8 12:18:07 antix1 asunder: Making album directory ‘/media/sdd2/motown classics – motown classics/’
May 8 12:18:07 antix1 asunder: Creating playlists
May 8 12:18:07 antix1 asunder: using completion file name: /home/roland/.cache/asunder/album_artist
May 8 12:18:07 antix1 asunder: Saving completion data
May 8 12:18:07 antix1 asunder: using completion file name: /home/roland/.cache/asunder/album_title
May 8 12:18:07 antix1 asunder: Saving completion data
May 8 12:18:07 antix1 asunder: using completion file name: /home/roland/.cache/asunder/album_genre
May 8 12:18:07 antix1 asunder: Saving completion data
May 8 12:18:07 antix1 asunder: encode() waiting for ‘barrier’
May 8 12:18:07 antix1 asunder: encode() waiting for ‘available’
May 8 12:18:07 antix1 asunder: completed tracks 0, rip 0.00%; encoded tracks 0, mp3 0.00% ogg 0.00% opus 0.00% flac 0.00% wavpack 0.00% monkey 0.00% musepack 0.00% aac 0.00%; prip 0.00% pencode 0.00%
May 8 12:18:07 antix1 asunder: Ripping track 1 to “/media/sdd2/motown classics – motown classics/01 – Unknown Artist – Track 1.wav”
May 8 12:18:07 antix1 asunder: 9013 started: cdparanoia -Z -e -d /dev/cdrom 1 x01.wav
May 8 12:18:09 antix1 asunder: completed tracks 0, rip 0.00%; encoded tracks 0, mp3 0.00% ogg 0.00% opus 0.00% flac 0.00% wavpack 0.00% monkey 0.00% musepack 0.00% aac 0.00%; prip 0.00% pencode 0.00%
May 8 12:18:10 antix1 kernel: [ 1278.159203] ata5: hard resetting link
May 8 12:18:10 antix1 kernel: [ 1278.877089] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 8 12:18:11 antix1 asunder: completed tracks 0, rip 0.00%; encoded tracks 0, mp3 0.00% ogg 0.00% opus 0.00% flac 0.00% wavpack 0.00% monkey 0.00% musepack 0.00% aac 0.00%; prip 0.00% pencode 0.00%
May 8 12:18:12 antix1 kernel: [ 1280.224009] ata5.00: configured for UDMA/66
May 8 12:18:12 antix1 kernel: [ 1280.297826] ata5: EH complete
May 8 12:18:12 antix1 asunder: Ripping 1 finished
May 8 12:18:12 antix1 asunder: rip() waiting for barrier
May 8 12:18:12 antix1 asunder: rip() done waiting
May 8 12:18:12 antix1 asunder: rip() signaling available
May 8 12:18:12 antix1 asunder: encode() done waiting, counter is now 0
May 8 12:18:12 antix1 asunder: Ripping track 2 to “/media/sdd2/motown classics – motown classics/02 – Unknown Artist – Track 2.wav”
May 8 12:18:12 antix1 asunder: 9024 started: cdparanoia -Z -e -d /dev/cdrom 2 x02.wav
May 8 12:18:12 antix1 asunder: encode() waiting for ‘barrier’
May 8 12:18:12 antix1 asunder: encode() waiting for ‘available’
May 8 12:18:12 antix1 asunder: Ripping 2 finished
May 8 12:18:12 antix1 asunder: cdparanoia(): rename() to ‘/media/sdd2/motown classics – motown classics/02 – Unknown Artist – Track 2.wav’ failed with errno=2
May 8 12:18:17 antix1 asunder: Ripping track 20 to “/media/sdd2/motown classics – motown classics/20 – Unknown Artist – Track 20.wav”
May 8 12:18:17 antix1 asunder: 9052 started: cdparanoia -Z -e -d /dev/cdrom 20 x20.wav
May 8 12:18:17 antix1 asunder: encode() waiting for ‘barrier’
May 8 12:18:17 antix1 asunder: encode() waiting for ‘available’
May 8 12:18:17 antix1 asunder: completed tracks 19, rip 0.00%; encoded tracks 19, mp3 0.00% ogg 0.00% opus 0.00% flac 0.00% wavpack 0.00% monkey 0.00% musepack 0.00% aac 0.00%; prip 95.00% pencode 0.00%
May 8 12:18:17 antix1 asunder: Ripping 20 finished
May 8 12:18:17 antix1 asunder: cdparanoia(): rename() to ‘/media/sdd2/motown classics – motown classics/20 – Unknown Artist – Track 20.wav’ failed with errno=2
May 8 12:18:17 antix1 asunder: rip() waiting for barrier
May 8 12:18:17 antix1 asunder: rip() done waiting
May 8 12:18:17 antix1 asunder: rip() signaling available
May 8 12:18:17 antix1 asunder: encode() done waiting, counter is now 0
May 8 12:18:30 antix1 kernel: [ 1298.540124] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:19:10 antix1 kernel: [ 1338.536487] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:19:50 antix1 kernel: [ 1378.538320] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:20:30 antix1 kernel: [ 1418.547607] [UFW BLOCK] IN=wlan1 OUT= MAC=e0:d4:e8:36:55:4c:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xE0 TTL=1 ID=0 DF PROTO=2
May 8 12:21:10 antix1 kernel: [ 1458.563171] [UFW BLOCK] IN=wlan1 OUT= MAC=01:00:5e:00:00:01:dc:f8:b9:9a:9a:77:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2

Attachments:

1. 

   asunder_pref_1.jpg
   

2. 

   asunder_pref_2.jpg
   

3. 

   asunder_pref_3.jpg
   

4. 

   asunder_pref_4.jpg
   

[Anonymous]

Helpful

Up

0

::

cdparanoia(): rename() to ‘/media/sdd2/motown classics – motown classics/02 – Unknown Artist – Track 2.wav’ failed with errno=2

seems like you need to investigate why the rename operation is failing
? a non-writeable destination has been specified
? non-writable due to media type? mount options? user lacks write permission?

[Member roland]

Helpful

Up

0

::

Thanks Skidoo, I looked at the permissions for every folder in /media and find to my surprise that the folder ‘roland’ (my $home user folder) has ‘root’ ownership whereas all other partition folders have ‘roland’ ownership. This is a recent install, but I have no recollection of having any event during the install process or since that would have caused me to change the ownership. This ownership must I believe have been conferred by the installer or at least at install time.

I have not yet run a chown to rectify matters until I have put the situation before you and request your comments.

Thanks again for your input.

Attachments:

1. 

   media_permissions.jpg
   

[Anonymous]

Helpful

Up

0

::

‘roland’ (my $home user folder) has ‘root’ ownership

screenshot shows a directory pathed at /media/roland
but
your $HOME directory is probably elsewhere ( /home/roland )
To confirm this, at commandline you can type: echo $HOME

So, yes, the way forward will be to “fix” the permissions of the media subdirectory.
sudo chown -R roland:roland /media/roland

[Member roland]

Helpful

Up

0

::

The suggested chown has restored the permissions to what they should be however have produced another mystery that I do not understand. I installed 4 identical and brand new 500gb disk drives in this build. At first boot it became apparent they came already formatted as Vfat with names in chinese characters which I did not want. I therefore before the installer ran, removed these with Gparted and replaced them as follows:-

drive 0 – sda1 for antiX, sda5 for swap, sda6 for $HOME and sda7 for data
drive 1 – sdb1 for data, sdb2 for data
drive 2 – sdc1 for data, sdc2 for data
drive 3 – sdd1 for data, sdd2 for data

Disk manager then produced a list of drive labels saying that no drives could be found corresponding to these labels, and inviting me to delete the labels if I wished and which was recommended, I did so.

I took advantage of the facility in 19.3 to install antiX on a dedicated partition sda1, swap on sda5, $HOME on sda6 and data on the remaining volumes.

But Gparted finds another partition and I do not know where it is located, 100mb and which Gparted cannot read, producing i-o errors. It is not visible on the maps of sda sdb sdc or sdd. It is causing no trouble except slows up the load of Gparted considerably and the warning messages have to be repeatedly cancelled, but strictly speaking I have no reason to run Gparted now the build is complete. However I would like to be rid of it after discovering the reason why it appears. I wonder if it has a real existence? I don’t suppose it could be the extended partition containing sda5 sda6 and sda7?

I’m sorry this post is drifting away from the original Asunder topic which I feel is secondary to resolving this mystery. I hope I am not stretching the rule too much?

Attachments:

1. 

   asunder_rogue_partition.jpg
   

2. 

   sda1_sda5_sda6_sda7.jpg
   

[Member Xecure]

Helpful

Up

0

::

Try to see all drives and partition with lsblk, to show also label
sudo lsblk -o name,mountpoint,label,size,uuid
This way you can figure out in which disk the strange partition is hiding.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member roland]

Helpful

Up

0

::

roland@antix1:~
$ su
Password:
root@antix1:/home/roland# lsblk -o name,mountpoint,label,size,uuid
NAME MOUNTPOINT LABEL SIZE UUID
sda 465.8G
├─sda1 / rootantiX19 48.8G 2310738f-8a5a-4dee-a14f-c0ec6c3a93a6
├─sda2 1K
├─sda5 [SWAP] swap 11.7G 1540a43b-5380-407b-a657-be4b262d6e04
├─sda6 /home homeantiX 200.2G 231afe95-3cba-4993-beb1-b52726510965
└─sda7 /media/antix_data sda7_data 205G 3eedced4-3153-41ef-9147-953c4a5795fe
sdb 465.8G
├─sdb1 /media/sdb1 sdb1 232.7G 0a085231-c321-49d4-aaf0-9d7f71cf067d
└─sdb2 /media/sdb2 sdb2 233.1G 7cf9bdcd-a2e9-493c-90f7-68cbd17af463
sdc 465.8G
├─sdc1 /media/sdc1 sdc1 232.9G a8aca46c-d144-456c-93ae-39bc84a527c9
└─sdc2 /media/sdc2 sdc2 232.9G 8b2f7fe4-ac6f-406e-a4e4-8e9e0ab2d50c
sdd 465.8G
├─sdd1 /media/sdd1 sdd1 232.9G f949503c-76cd-4b06-ade0-fc54a756915a
└─sdd2 /media/sdd2 sdd2 232.9G 198b6b77-a1e4-4adf-b340-98a24491a44e
sde 100M
sr0 1024M
root@antix1:/home/roland#

It doesn’t seem to provide any further information. Being only very small it isn’t a problem, but anything I don’t know the reason for may be a hidden problem. There are no other physical drives or volumes than the ones listed and which I know about having built it from scratch, which are sda thru sdd and their associated volumes. The screenshot shows files in /dev in this name range, there is an sde and an sdf present.

I wonder if I should simply disregard it, unless you feel it there may be value in further investigation, Xecure?

Attachments:

1. 

   sde_sdf.jpg
   

[Member Xecure]

Helpful

Up

0

::

roland wrote:

sde 100M

Could this a card-reader or something similar? It doesn’t have an UUID, so it doesn’t seem to be a storage device, and it isn’t mounted either, so I see no risk in it.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member roland]

Helpful

Up

0

::

I think you have hit the nail on the head!

I have a media device reader, which also has a Sata-2 and Sata-3 socket, which I wired up to the required headers on the mainboard and/or a Sata expansion card in a PCE-express 1-lane slot. On the front panel one socket is labelled SATA and the other ESATA. I now feel certain this device is the cause of this phantom drive sde, and that there is a potential sdf also lurking in there.

Apologies for this wild goose chase Xecure, I shall try in future to remain focused on the problem I posted and not be sidetracked by interesting yet irrelevant issues. I do however welcome problems of this nature, in 48 years of computers in my life I have discovered one great truth, one learns nothing without getting ones hands dirty in the nuts and bolts of IT.

I now expect Asunder to function as it should, having returned ownership to myself of my user volume.

If you see nothing further regarding Asunder you may infer that the problem was resolved, and thanks again.

[Author]

Posts