#2099

What steps are you taking to record?

Any errors from Maiden?

Do you have disk space available? (Use df -h from the command line over ssh to check)

1 Like
#2100

all im doing when trying to record is hit K like always and it just throws up the bellow error

from maiden
stack traceback:
/home/we/norns/lua/core/menu/tape.lua:66: in upvalue ‘update_tape_index’
/home/we/norns/lua/core/menu/tape.lua:161: in function ‘core/menu/tape.key’
/home/we/norns/lua/core/menu.lua:139: in function </home/we/norns/lua/core/menu.lua:116>
lua: /home/we/norns/lua/core/menu/tape.lua:66: attempt to index a nil value (local ‘f’)

Norns: development
#2101

ssh into Norns shows:
192.168.1.220 ~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 59G 2.5G 55G 5% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 83M 381M 18% /dev/shm
tmpfs 464M 14M 450M 3% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 253M 41M 212M 16% /boot
tmpfs 93M 0 93M 0% /run/user/1000

#2102

Try a SYSTEM>RESET maybe?

1 Like
#2103

Yes I’ve tried reset :slight_smile:

#2104

How did you run your update? I saw you posting over in the main norns update thread, just wondering if you’d attempted some kind of forced update that may have pulled from the norns branch rather than the fates one?

#2105

Have you updated to 201029?

You may want to delete the ~/version.txt file (via ftp or ssh), then run the update from the norns menu.

#2106

Yeah I’ve updated no problem - that’s the thing, it’s not related to any update as it happened before the new firmware update and hasn’t been Changed at all by them…

#2107

What are the contents of the file at ~/dust/audio/tape/index.txt on your system?

You could try deleting that index.txt file and see if that clears the error or not.

Or also check the permissions for that file or directory.
(EDIT - this is sounding like it might be a file permissions problem - getting the output from ls -la in the tape directory and maybe also one level up in audio would be informative)

#2108

Thank you for all your work and time! Update worked fine as usual, needed a system > reset to get sound back after rebooting - tape was fine, but scripts were not.

#2109

everything goes well. thanks

#2110

image
image1280×720 117 KB

#2111

I don’t know what’s going on…my recordings got deleted a week or so ago when this started so I’m super fine with starting off all fresh and new…unless something jumps out

#2112

Create a new tape directory at ~/dust/audio/ (and that will fix it)

1 Like
#2113

Thank you so much - the hours I’ve spent!!
At least I learned something
Thank you for all this work you do, it’s very appreciated
Now to the tape mobile!!

#2114

for anyone having an issue expanding their memory on fates i found this guide useful https://raspberry-projects.com/pi/pi-operating-systems/raspbian/troubleshooting/expand-filesystem-issues

1 Like
#2115

FWIW - I’d suggest only trying the process on that link if you have otherwise not been able to get the disk expanded with the instructions on the github.

1 Like
#2116

updating on a pi 4 , is there a progress bar or is it mean to just hang on checking for update until complete? (via wifi)

#2117

Should be something like… checking for update, downloading, updating, update complete.

(I’ll look for the actual steps when I’m back at a computer and fates)

Maiden REPL will show output/progress during update. Maybe try again and watch maiden for status.

1 Like
#2118

literally just worked now , so all good :slight_smile:

1 Like