Turris won't read my sdcard anymore

Turris 1.x hardware Turris HW help
1

hey guys. I seem to have a problem with my Turris 1.x …i had it migrated to microsd card for a long time, but after some recent update/reboot, it is not getting fully up and i was seeing the errors regarding mmc0 device:

2023-12-20 10:30:36 err kernel[]: [   64.114139] mmc0: card never left busy state
2023-12-20 10:30:36 err kernel[]: [   64.118461] mmc0: error -110 whilst initialising SD card
2023-12-20 10:30:38 err kernel[]: [   65.377982] mmc0: card never left busy state
2023-12-20 10:30:38 err kernel[]: [   65.382343] mmc0: error -110 whilst initialising SD card
2023-12-20 10:30:39 err kernel[]: [   66.755861] mmc0: card never left busy state
2023-12-20 10:30:39 err kernel[]: [   66.760192] mmc0: error -110 whilst initialising SD card
2023-12-20 10:30:41 err kernel[]: [   68.957599] mmc0: card never left busy state
2023-12-20 10:30:41 err kernel[]: [   68.961926] mmc0: error -110 whilst initialising SD card
2023-12-20 10:30:42 err kernel[]: [   70.145443] mmc0: card never left busy state
2023-12-20 10:30:42 err kernel[]: [   70.149777] mmc0: error -110 whilst initialising SD card
2023-12-20 10:30:44 err kernel[]: [   71.421317] mmc0: card never left busy state
2023-12-20 10:30:44 err kernel[]: [   71.425680] mmc0: error -110 whilst initialising SD card

I assumed the SD card died or, since the router sat in the attic, that due to some low temperatures, the sd card somewhat moved inside the reader. so Today, i took it out, but noticed i can mount it in my laptop.
Next, I assumed the btrfs might be corrupted since i was not able to copy stuff from it, so i simply formatted the card and wanted to start over.
While i have my turris connected via debug cable, i can see that there are still a number of

[  447.537549] mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0

errors.
Also, when i do btrfs_migrate, i am getting a ton of these errors, and the script finally fails with:

root@turris:/# btrfs_migrate
Are you sure you want to lose everything on mmcblk0? (yes/no)
yes
...
[  447.269120] mmcblk0: error -84 transferring data, sector 224704, nr 128, cmd response 0x900, card status 0xc00
[  447.282655] mmcblk0: error -84 transferring data, sector 224832, nr 128, cmd response 0x900, card status 0xc00
[  447.296311] mmcblk0: error -84 transferring data, sector 224960, nr 128, cmd response 0x900, card status 0xc00
[  447.310058] mmcblk0: error -84 transferring data, sector 225088, nr 128, cmd response 0x900, card status 0xc00
[  447.323699] mmcblk0: error -84 transferring data, sector 225216, nr 64, cmd response 0x900, card status 0xc00
...
fdisk: cannot open /dev/mmcblk0: Input/output error
mkfs.fat 3.0.28 (2015-05-16)
/dev/mmcblk0p1: No such file or directory
Can't create fat!

I also tried to insert a new microsd card and having the same issues.
Also tried to create the partitions on my laptop but it is acting the same.
I am now worried that there might be something with the internal card reader? Do you guys have any experience around these issues? what else could i try?

2

This is not pleasant. If I remember correctly, your microSD slot is somehow dead, but not everything is lost. Turris guys have from Pali (ex Turris kernel developer) prepared U-boot update for this incredible powerful device (still in 2023!) in their GitLab even there is how to. Ask them to do that for you, which will allow you to boot from USB devices.

Since I do not have access for anything what Pali did, I am not able to prepare the update, which was necessary to do that for Turris OS 3.x and then for 6.x. Sorry!

2 Likes
3

@Pepe , thanks for the insider info and pointers. What would be the correct way to approach devs? I don’t know their handles here on forum.
Can I simply contact support?
Thanks!

4

Go ahead for that! I think that’s the only approach now, even though they are short-handed, just insist on your request, because as I said it is prepared and it will not take more than one business day to do it all. It is prepared step by step, tested and only it needs to be released. Packages are compiled and must be added or replaced in the old build system manually instead of compiling entirely as it is really complicated to build all packages for Turris OS 3.x.

Someone inside Turris team can say, but we will not make any profit or it does not make sense from the business point of view. Right now, at least, I think it is the only way to tell the public that they care about the oldest device, which they manufactured, and at least to be visible in the public.

They could do more features, which are not complete, but they need to be supported. Even in the basic IT courses, you will be told that you should have a few features instead of many features and you would not know what you should fix first, right? Also, keep in mind that the Turris team has only a few people to do the job, which is kinda questionable looking at the end-of-life version, which is claimed to be stable for us or looking into their GitLab… But how many features you can do in one day? :thinking:

1 Like