Error unable to save resume file no such file or directory

Using a Qnap NAS.

qnapper

Posts: 1
Joined: Thu Aug 05, 2010 8:14 pm

Error: Unable to save resume file: No such file or directory

Using a Qnap NAS.

Installed transmission and started the daemon using the user «transmission».

Somehow i get this error after a short while when downloading a torrent:
Error: Unable to save resume file: No such file or directory

Trying to use the «admin» user instead when starting the daemon i do not get this error. So the transmission user does not got the right permission to write to some file?

The transmission user got read/write access on both the —config-dir and the —download-dir does it need access somewhere else?

blackjancsi

Posts: 6
Joined: Sat May 30, 2009 8:31 pm

Re: Error: Unable to save resume file: No such file or direc

Post

by blackjancsi » Fri Oct 22, 2010 9:34 pm

Hi,

I have a Western Digital MyBook World Edition II (blue ring), have the exact same problem. The problem only comes up when I don’t run transmission as root, but with

Code: Select all

sudo -u username transmission-daemon

The config and download directories are owned by the transmission user. What could be wrong? (I recently did a firmware upgrade to have an external hard drive on NTFS running, and as I was stupid enough not to backup everything well, now I have to reconfigure transmission… ouch)

Anyone, any ideas?

Thx,
Janos

blackjancsi

Posts: 6
Joined: Sat May 30, 2009 8:31 pm

Re: Error: Unable to save resume file: No such file or direc

Post

by blackjancsi » Fri Oct 22, 2010 9:58 pm

OK, I managed to find the solution. I had to give BOTH the config and download dirs as params to transmission-daemon (so I guess it took that from the root .config, not that users .json file), and now it works:

Code: Select all

sudo -u transuser transmission-daemon -g /home/transuser/.config/transmission-daemon/ -w /shares/internal/PUBLIC/downloads/

Hope that helps.

Janos

Источник

  • Attention, TrueNAS Community Members.

    General Help has now been set to read-only mode.

    To make sure you can easily find what you’re looking for, we’ve relocated all relevant categories under their respective version. This change will simplify searching for information and minimize any confusion about where to post.

Register for the iXsystems Community to get an ad-free experience

  • Thread starter

    tabs138

  • Start date

    Jun 15, 2013

Status
Not open for further replies.

  • #1

I’ve been having a hell of a time getting Transmission to work properly, and I’ve read everything I could find regarding this issue and have had no luck. So any advice or tips would be greatly appreciated at this point!

After following the installation instructions from the recent Lifehacker NAS article, everything has been working fine except for the fact that Transmission will begin a download, but will eventually produce the following error after a few minutes:

Error: Unable to save resume file: No such file or directory

I also get this error whenever I attempt to pause an actively downloading torrent. What’s really strange is that I’m able to download torrents to completion, but I have to constantly go to the WebGUI and restart the download every few minutes.

If it’s any help, I’ll copy some of the jail permissions I’ve set in case anyone sees a glaring error. I did a chmod 777 on some of the folders since I have no external network security concerns. Please don’t hesitate to ask for any other details or screenshots if needed.

My download folder — /mnt/usr/BTDownloads

Code:

drwxrwxr-x  4 1001  transmission    6 Jun 15 16:05 BTDownloads

Transmission folder — /mnt/usr/pbi/

Code:

drwxrwxrwx 17 1003 1003 25 Jun 12 01:52 transmission-amd64

Transmission home directory

Code:

drwxrwxrwx 3 transmission transmission 5 Jun 15 15:07 home

Elo

Contributor


  • #2

If it’s any help, I’ll copy some of the jail permissions I’ve set in case anyone sees a glaring error. I did a chmod 777 on some of the folders since I have no external network security concerns. Please don’t hesitate to ask for any other details or screenshots if needed.

My download folder — /mnt/usr/BTDownloads

Code:

drwxrwxr-x  4 1001  transmission    6 Jun 15 16:05 BTDownloads

Transmission folder — /mnt/usr/pbi/

Code:

drwxrwxrwx 17 1003 1003 25 Jun 12 01:52 transmission-amd64

Transmission home directory

Code:

drwxrwxrwx 3 transmission transmission 5 Jun 15 15:07 home

I had the same error. The the usr/pbi directory structure inside the jail had owner 1014 (I followed the Youtube video to the letter). I changed the owner to root:wheel and set the permissions to 777 for the resume and the torrent directories (you se the full path as part of the error message). This solved that problem for me but is ofcourse a very insecure solution. I o struggle with problems of connecting to trackers. In fact I am not able to connect to anyone of them but that is for another thread :)

Status
Not open for further replies.
Источник

Содержание

  1. Transmission
  2. [Solved] Unable to save resume file: Input/output error
  3. [Solved] Unable to save resume file: Input/output error
  4. Re: Error: Unable to save resume file: Input/output error
  5. Re: Error: Unable to save resume file: Input/output error
  6. Re: Error: Unable to save resume file: Input/output error
  7. Re: Error: Unable to save resume file: Input/output error
  8. Трансмишн вылетает со странной ошибкой
  9. Transmission: Ошибка Unable to save resume file: Operation not supported
  10. Вопрос
  11. Виктор Илюхин
  12. Виктор Илюхин
  13. Unable to save resume file: permission denied #68
  14. Comments
  15. Footer
  16. transmission Remote GUI Unable to save resume file

Transmission

A Fast, Easy, and Free BitTorrent client

[Solved] Unable to save resume file: Input/output error

[Solved] Unable to save resume file: Input/output error

Post by edoornav » Fri Feb 11, 2011 7:05 am

After years and years of using Transmission with no problem and clicking the «Nope» button when it asks to donate, I finally donated $10. A few days later, I’m getting this error and can’t download anything:

«Error: Unable to save resume file: Input/output error»

This problem started to occur when I was torrenting a collection of files larger than my remaining disk space. When I realized this, I unchecked most of the files and then abandoned this torrent altogether. But now I still have this problem. Any ideas? Thanks.

Re: Error: Unable to save resume file: Input/output error

Post by x190 » Fri Feb 11, 2011 7:56 am

/Library/Application Support/Transmission and make sure the .torrent and .resume files are gone for that torrent. Make sure you remove (trash and delete) any .part files belonging to the torrent that may be using disk space unnecessarily. Ensure that you have plenty of disk space for any remaining torrents.

If you now have sufficient disk space but still get the error try running Disk Utility first aid.

Re: Error: Unable to save resume file: Input/output error

Post by edoornav » Fri Feb 11, 2011 8:44 am

Thanks x190. This is what I’ve done:

1) Removed all torrents from Transmission
2) Quit Transmission
3) Deleted all .torrent files and .part files
4) Deleted all files in

/L/A/T/Torrent
5) Repaired permissions with Disk Utility

When I re-download the torrent and start Transmission, after a few minutes of activity I get the same error. I have 32GB available on my disk and I’m just trying to download a few files of a 4GB torrent.

Are there any other tricks I can try? If I wanted to completely start from scratch, would I just need to delete the application and support files in

/Library/Application Support/Transmission? Is there anything else that would need to be cleared or reset? Thanks for your help.

Re: Error: Unable to save resume file: Input/output error

Post by x190 » Fri Feb 11, 2011 9:30 am

When you use Disk Utility run «Verify Disk». If errors are found, repair disk using Disk Utility on your Install disc.

If you want to get rid of all T’s support files and re-set prefs, here’s the list.

† Try d/ling a different torrent for testing purposes. Perhaps the one you are having trouble with is corrupted somehow.

Re: Error: Unable to save resume file: Input/output error

Post by edoornav » Tue Feb 15, 2011 1:12 pm

Источник

Трансмишн вылетает со странной ошибкой

Debian tsting, transmission-daemon Скачивает по несколько Мб и вылетает «Error: Unable to save resume file: No such file or directory»

Права на запись в папку, естественно, есть. Файлы качаются (только очень медленно)

В конфиге поменял только папку для скачивания и umask выставил на 0. Папку для неоконченных торрентов включал и выключал — не помогает.

В принципе трансмиссия мне не критична, пробовал rtorrent — слишком много костылять нужно. Но если кто-то посоветует более адекватный клиент без гуев и демоном буду благодарен.

пробовал rtorrent — слишком много костылять нужно

//У меня в конфиге umask почему-то 18.

umask я поправил на 0, я ж пишу — на старой системе было 18, но были очень странные права на файлы.

Костылять рторрент нужно до состояния демона. Нужно писать свой rc скрипт, а мне банально лень 🙂

ВИдел, но оно стартует в скрин, но зачем? есть детач. Я не пользуюсь скрином, максимум — тмукс. Короче костыли 🙂

Конфиг в хомяке поправь, оно не из /etc берёт.

Угу, ясно. Подожди, когда ошибка твоя исправится.

И если ты больше ничего не менял в transmission-daemon, то он у меня работает с umask 18.

Я знаю, в /etc/defaults поменял настройки, теперь он из хомяка берет.

Ну сейчас я поставил на 18 и перезапустил — ошибка на месте. Разве что обрывается закачка после 50-100Мб.

Источник

Transmission: Ошибка Unable to save resume file: Operation not supported

Спросил Виктор Илюхин,
11 марта, 2020

Вопрос

Виктор Илюхин

Виктор Илюхин

Доброго времени суток! Через некоторое время после добавления торрента выпадает ошибка — Unable to save resume file: Operation not supported, причем конкретной зависимости по времени выпадения ошибки, настроек клиента и интернет-центра не выявил. С чем это может быть связано?

Сохранение идет на внешний хард.

Transmission Версия:2.94. KeeneticOS: 3.3.12.

Изменено 11 марта, 2020 пользователем Виктор Илюхин

Источник

Unable to save resume file: permission denied #68

Transmission frequently stops downloading with the following error:
Unable to save resume file: permission denied

Folders in /config are set with the following permissions:

I set the /config/resume folder permissions to abc users and it solved the issue.

Host: Fedora release 29 (Twenty Nine)
Docker: 18.09.1

Image linux/transmission was pulled and ran w/o modification

The text was updated successfully, but these errors were encountered:

The abc user runs as the UID and GID you pass to it. If you have 1001:1001 perms on a file when you ran with 1000:1000, you must have at some time had a user or container write that file their with 1001:1001 perms.

Same problem here.
But when I look into files permissions resume file has the user permission.

4 drwsr-xr-x 5 le0pa-rd debian-transmission 4096 Mar 23 12:41 .
4 drwxr-xr-x 3 root root 4096 Mar 23 12:11 ..
4 drwxr-xr-x 2 le0pa-rd debian-transmission 4096 Mar 23 12:11 blocklists
4 drwxr-xr-x 2 le0pa-rd debian-transmission 4096 Mar 23 12:18 resume
0 lrwxrwxrwx 1 le0pa-rd root 38 Mar 25 2020 settings.json -> /etc/transmission-daemon/settings.json
4 -rw——- 1 le0pa-rd debian-transmission 133 Mar 23 12:20 stats.json
4 drwxr-xr-x 2 le0pa-rd debian-transmission 4096 Mar 23 12:18 torrents

Where am I doing wrong?

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

transmission Remote GUI Unable to save resume file

Помогите разобраться с transmission Remote GUI.
При добавлении торрента начинает закачку и сразу выдает ошибку:
Unable to save resume file: Permission denied

Посмотри права на /var/lib/transmission-daemon и всё что ниже. Он туда состояние закачек сохраняет.

у меня transmission-daemon работает от имени transmission от этого, директория куда он пишет принадлежит ему

transmission daemon запусти с опцией логами. посмотри куда он пытается писать.

Странно.
Запускаю демон вот так:

[2017-05-16 08:33:14.648] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
[2017-05-16 08:33:14.648] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)

Там в логе ещё про опции sysctl должно быть сказано который нужно настроить (в /etc/sysctl.conf). Это возможно и влияет на скорость.

sudo /etc/init.d/transmission-daemon start
Unable to save resume file: Permission denied

А тут неизвестно от какого юзера демон запускается в твоём дистре. Там наверное папки нет нужной.

Можно запускать transmission-daemon и от своего юзера.

Источник

Источник

NB. Автор исходит из предположения, что по торрентам будет скачиваться только легальный контент. Мне, например, удобно торрентом грузить Ubuntu отсюда

1. Выбираем диск, на который будем качать. Создаем там папку у меня — Download, полный путь /mnt/WD2T/Files/Download/
Папки можно создать многими способами, IMHO проще всего — через FTP. Если обеспечить полный доступ к этим папкам (777) — вам будет проще. Если создавали папку через FTP, как он описан в этом блоге — права на месте.

2. (рекомендуется)Создаем папку там, где будут лежать служебные файлы transmission. Этого можно не делать, но тогда при перезагрузке будут долго перехешироваться уже загруженные файлы. Папку лучше убрать куда-то подальше, например на созданный ранее датасет Sys. У меня, впрочем, эта папка лежит рядом с Dowload, на /mnt/WD2T/Files/start/sys/
UPD Не рекомендую создавать эту папку на флешке — я так делал и за полгода флешка сточилась.

3. (необязательно) Создаем горячую папку, куда будем кидать торрент файлы. У меня /mnt/WD2T/Files/start/

4. Подготовка закончена, идем в Services|BitTorrent
Устанавливаем параметры

Peer port — обычно работает и по умолчанию. Но есть исключения. Я обычно генерю utorrent на PC случайный порт, убеждаюсь, что с ним работает — и ставлю его. Честно признаюсь, у меня сейчас не тот порт, что на картинке.

Указываем в полях Download directory, Configuration directory и Watch directory созданные нами папки.

Distributed hash table — зависит от того,откуда качаете. Некоторые администраторы трекеров не любят DHT.

User mask — поставьте 0000, меньше проблем с правами будет.
save-restart, если не ругнулось — идем дальше

5. Управлять можно через встроенный веб интерфейс по адресу-порту, указанных как URL. Он с годами сильно продвинулся и тоже позволяет переименовывать раздачи. Но есть много других клиентов, даже для Android. Для windows —  Transmisson-Remote-GUI.

6. Теперь можно качать. Бросаем торрент файл в горячую папку. Или, еще лучше, указываем виндам открыть торрент в transmission remote

7. Если все хорошо — пошла закачка

Если ни одного пира не обнаруживается — смотрим сетевую архитектуру, прежде всего роутер. Полезно сначала убедиться, что мю-торрент качает, поставить такой же порт.

Если закачка начинается, но сразу прерывается с ошибкой — скорее всего дело в правах.
Проще всего (подставьте свои имена папок)
chmod -R 777 /mnt/WD2T/Files/Download/
chmod -R 777 /mnt/WD2T/Files/start/sys/
chmod -R 777 /mnt/WD2T/Files/start/

разрешить все на всех монтированных дисках, как предлагалось выше. Квалифицированные юнуксоиды знают более правильный путь, но они этот текст, думаю, не читают.

или переставить права в файловом менеджере
Advanced|File Manager
логин-пароль как при входе в вебгуй

PS Крайне полезно в Система|Общие параметры Настройки DNS IPv4 DNS-серверы указать кроме собственного роутера и какой-нибудь внешний DNS. Я обычно указываю гугловский 8.8.8.8
Можно указать Яндексовский или своего провайдера

PPS C ошибкой kernel: pid 12422 (transmission-daemon), uid 999: exited on signal 10 я боролся в конце этого поста

UPD от 25 дек 2015 Камрад RU_Taurus предложил более симпатичное решение. Команды ниже. Можно положить как PostInit скрипт в System|Advanced|Command scripts
service transmission stop && pw usermod transmission -G wheel -d /mnt/WD2T/Files/start/sys && service transmission start

Везде вместо /mnt/WD2T/Files/start/sys напишите ту папку, которую вы указали для настроек в п 2.

Кроме того, эту папку надо отдать transmission (можно через Advanced|Execute command)
chown -R transmission /mnt/WD2T/Files/start/sys
/UPD

Источник

Трансмишн 2.61 тоже качает с резкими перепадами.
HDD-ext2

    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 128,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "blocklist-url": "http://www.example.com/blocklist",
    "cache-size-mb": 4,
    "dht-enabled": true,
    "download-dir": "/media/DISK_A1/transmission/downloads",
    "download-queue-enabled": true,
    "download-queue-size": 3,
    "encryption": 0,
    "idle-seeding-limit": 30,
    "idle-seeding-limit-enabled": true,
    "incomplete-dir": "/media/DISK_A1/transmission/incomplete",
    "incomplete-dir-enabled": true,
    "lpd-enabled": false,
    "message-level": 1,
    "open-file-limit": 16,
    "peer-congestion-algorithm": "lp",
    "peer-limit-global": 15,
    "peer-limit-per-torrent": 10,
    "peer-port": 52400,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": "default",
    "pex-enabled": false,
    "port-forwarding-enabled": false,
    "preallocation": 2,
    "prefetch-enabled": 0,
    "queue-stalled-enabled": true,
    "queue-stalled-minutes": 30,
    "ratio-limit": 5,
    "ratio-limit-enabled": true,
    "rename-partial-files": true,
    "rpc-authentication-required": true,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "{b68530dce6bf55de55aa3fe91b845aedb0069c06ruStzsd0",
    "rpc-port": 9091,
    "rpc-url": "/transmission/",
    "rpc-username": "admin",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": true,
    "scrape-paused-torrents-enabled": true,
    "script-torrent-done-enabled": false,
    "script-torrent-done-filename": "",
    "seed-queue-enabled": false,
    "seed-queue-size": 10,
    "speed-limit-down": 2000,
    "speed-limit-down-enabled": true,
    "speed-limit-up": 500,
    "speed-limit-up-enabled": true,
    "start-added-torrents": true,
    "trash-original-torrent-files": true,
    "umask": 2,
    "upload-slots-per-torrent": 14,
    "utp-enabled": false,
    "watch-dir": "/media/DISK_A1/transmission/torrentwatch",
    "watch-dir-enabled": true
Источник

Дабы не плодить тем. После подключения внешнего диска по USB он какое-то время работает и на него даже можно скачать файлы.

А потом лог выдает подобные ошибки:

Цитата

[C] Aug  5 04:39:51 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 6565, block_bitmap = 215121920
[I] Aug  5 04:39:56 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:39:56 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:39:56 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:39:56 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 66 98 08 00 00 00 08 00
[E] Aug  5 04:39:56 kernel: blk_update_request: critical medium error, dev sda, sector 1721239552
[C] Aug  5 04:39:56 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 6566, block_bitmap = 215154688
[I] Aug  5 04:40:02 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:40:02 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:40:02 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:40:02 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 68 a4 08 00 00 00 08 00
[E] Aug  5 04:40:02 kernel: blk_update_request: critical medium error, dev sda, sector 1755580416
[C] Aug  5 04:40:02 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 6697, block_bitmap = 219447296
[I] Aug  5 04:40:05 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:40:05 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:40:05 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:40:05 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 6a 78 08 00 00 00 08 00
[E] Aug  5 04:40:05 kernel: blk_update_request: critical medium error, dev sda, sector 1786251264
[C] Aug  5 04:40:05 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 6814, block_bitmap = 223281152
[I] Aug  5 04:40:13 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:40:13 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:40:13 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:40:13 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 6a 8c 08 00 00 00 08 00
[E] Aug  5 04:40:13 kernel: blk_update_request: critical medium error, dev sda, sector 1787561984
[C] Aug  5 04:40:13 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 6819, block_bitmap = 223444992
[I] Aug  5 04:40:17 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:40:17 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:40:17 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:40:17 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 6f 0c 08 00 00 00 08 00
[E] Aug  5 04:40:17 kernel: blk_update_request: critical medium error, dev sda, sector 1863059456
[C] Aug  5 04:40:17 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 7107, block_bitmap = 232882176
[I] Aug  5 04:40:41 wmond: WifiMaster1/AccessPoint0: (MT76x2) STA(d8:ce:3a:8f:1f:69) GTK rekey done, group cipher AES.
[I] Aug  5 04:40:49 kernel: usb 1-1: reset high-speed USB device number 2 using ehci-platform
[I] Aug  5 04:41:32 wmond: WifiMaster0/AccessPoint0: (MT7628) STA(a4:50:46:d6:3b:bf) GTK rekey done, group cipher AES.
[I] Aug  5 04:41:33 wmond: WifiMaster0/AccessPoint0: (MT7628) STA(0c:e0:dc:45:e9:01) GTK rekey done, group cipher AES.
[I] Aug  5 04:41:36 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[I] Aug  5 04:41:36 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
[E] Aug  5 04:41:36 kernel: blk_update_request: I/O error, dev sda, sector 2048
[E] Aug  5 04:41:36 kernel: Buffer I/O error on dev sda1, logical block 0, lost sync page write
[I] Aug  5 04:42:45 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[I] Aug  5 04:42:45 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
[I] Aug  5 04:42:45 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
[I] Aug  5 04:42:45 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 70 48 08 00 00 00 08 00
[E] Aug  5 04:42:45 kernel: blk_update_request: critical medium error, dev sda, sector 1883768832
[C] Aug  5 04:42:45 kernel: EXT4-fs error (device sda1): ext4_wait_block_bitmap:529: comm transmissiond: Cannot read block bitmap — block_group = 7186, block_bitmap = 235470848
[E] Aug  5 04:42:45 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
[I] Aug  5 04:43:16 kernel: usb 1-1: reset high-speed USB device number 2 using ehci-platform
[I] Aug  5 04:44:03 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[I] Aug  5 04:44:03 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
[E] Aug  5 04:44:03 kernel: blk_update_request: I/O error, dev sda, sector 2048
[E] Aug  5 04:44:03 kernel: Buffer I/O error on dev sda1, logical block 0, lost sync page write
[I] Aug  5 04:44:59 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[I] Aug  5 04:44:59 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 01 4a f0 00 00 10 00
[E] Aug  5 04:44:59 kernel: blk_update_request: I/O error, dev sda, sector 84720
[W] Aug  5 04:45:00 kernel: EXT4-fs warning (device sda1): ext4_end_bio:307: I/O error -5 writing to inode 158498820 (offset 0 size 8192 starting block 10592)
[E] Aug  5 04:45:00 kernel: Buffer I/O error on device sda1, logical block 10334
[E] Aug  5 04:45:00 kernel: Buffer I/O error on device sda1, logical block 10335
[W] Aug  5 04:45:00 kernel: JBD2: Detected IO errors while flushing file data on sda1-8
[I] Aug  5 04:45:56 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[I] Aug  5 04:45:56 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 6a 78 00 00 38 00
[E] Aug  5 04:45:56 kernel: blk_update_request: I/O error, dev sda, sector 27256
[E] Aug  5 04:45:56 kernel: Aborting journal on device sda1-8.
[E] Aug  5 04:45:56 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
[I] Aug  5 04:46:52 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[I] Aug  5 04:46:52 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 01 4a 18 00 00 08 00
[E] Aug  5 04:46:52 kernel: blk_update_request: I/O error, dev sda, sector 84504
[W] Aug  5 04:46:52 kernel: EXT4-fs warning (device sda1): ext4_end_bio:307: I/O error -5 writing to inode 12 (offset 0 size 4096 starting block 10564)
[E] Aug  5 04:46:52 kernel: Buffer I/O error on device sda1, logical block 10307
[W] Aug  5 04:47:38 kernel: JBD2: Detected IO errors while flushing file data on sda1-8
[C] Aug  5 04:47:38 kernel: EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[C] Aug  5 04:47:38 kernel: EXT4-fs (sda1): Remounting filesystem read-only

Источник

  1. Hi,
    I wonder has someone successfull experience with built-in Transmission? I had tried
    it with beta firmwares: 2017-06-16 v1.2.1.5, 2017-05-17 v1.2.0.2, 2017-05-04 v1.2.0.0, 2017-04-01 v1.1.2.0.
    I tried to set download path to external SATA hard drive (EXT3), to USB flash drive (FAT32), to internal storage (/sdcard/Download), but the result was the same — a minute after download starts (I see .part file in destination location, so it proves that donwload path was set correctly) it stops with error message «Unable to save resume file: No such file or directory». Interesting is that I was able to complete one ~100 Mb download (to USB drive) manually invoking «Start download» every time it was stopping. The only working way to flash the formware for me is «Recovery method». USB update does nothing, OTA update fails or says that I’m using the latest firmware. May be this somehow connected to the main problem.
    May be it possible to install some external torrent client (via appstore) that has web-interface to manage downloads?
    Olegs.

  3. New firmware, same problem! Please give a permission to save config file!!!

  4. Please, any feedback regarding the question would be appreciated.

Share This Page


Egreat Forum

Источник

Понравилась статья? Поделить с друзьями:
  • Error unable to initialize the unity engine как исправить
  • Error unable to initialize steam api please make sure steam is running and
  • Error unable to initialize smbios library
  • Error unable to initialize main class
  • Error unable to initialize gtk is display set properly