Xubuntu Live used to copy files - I/O error - where's the log?
up vote
0
down vote
favorite
I regularly use Xubuntu 18.10 on a live pendrive for when I need to transfer data from one NTFS HD to another when Windows is corrupt, for example. I'm experiencing (I suspect) bad sectors on one HDD and Thunar is showing I/O Errors.
Does Thunar record these errors in a log file and what is the log file's location? Will it save to a live pendrive?
Otherwise, to record the errors reported by Thunar, I'm screen-shotting each error and saving to a jpeg - there's got to be a better way?
I'm not adverse to using Kubuntu or other, if that's a workable solution.
xubuntu thunar
add a comment |
up vote
0
down vote
favorite
I regularly use Xubuntu 18.10 on a live pendrive for when I need to transfer data from one NTFS HD to another when Windows is corrupt, for example. I'm experiencing (I suspect) bad sectors on one HDD and Thunar is showing I/O Errors.
Does Thunar record these errors in a log file and what is the log file's location? Will it save to a live pendrive?
Otherwise, to record the errors reported by Thunar, I'm screen-shotting each error and saving to a jpeg - there's got to be a better way?
I'm not adverse to using Kubuntu or other, if that's a workable solution.
xubuntu thunar
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallbackdmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors usingbadblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or youscp
etc. the file elsewhere)
– guiverc
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I regularly use Xubuntu 18.10 on a live pendrive for when I need to transfer data from one NTFS HD to another when Windows is corrupt, for example. I'm experiencing (I suspect) bad sectors on one HDD and Thunar is showing I/O Errors.
Does Thunar record these errors in a log file and what is the log file's location? Will it save to a live pendrive?
Otherwise, to record the errors reported by Thunar, I'm screen-shotting each error and saving to a jpeg - there's got to be a better way?
I'm not adverse to using Kubuntu or other, if that's a workable solution.
xubuntu thunar
I regularly use Xubuntu 18.10 on a live pendrive for when I need to transfer data from one NTFS HD to another when Windows is corrupt, for example. I'm experiencing (I suspect) bad sectors on one HDD and Thunar is showing I/O Errors.
Does Thunar record these errors in a log file and what is the log file's location? Will it save to a live pendrive?
Otherwise, to record the errors reported by Thunar, I'm screen-shotting each error and saving to a jpeg - there's got to be a better way?
I'm not adverse to using Kubuntu or other, if that's a workable solution.
xubuntu thunar
xubuntu thunar
asked Nov 13 at 10:39
David1618
113
113
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallbackdmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors usingbadblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or youscp
etc. the file elsewhere)
– guiverc
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27
add a comment |
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallbackdmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors usingbadblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or youscp
etc. the file elsewhere)
– guiverc
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallback
dmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors using badblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or you scp
etc. the file elsewhere)– guiverc
Nov 13 at 11:27
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallback
dmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors using badblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or you scp
etc. the file elsewhere)– guiverc
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092511%2fxubuntu-live-used-to-copy-files-i-o-error-wheres-the-log%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
When using a 'live' system, you are using a fs (file-system) created on boot and located in memory; so even if stored in a log file (it'd be in the fallback
dmesg
or sysd log I'd assume) I'd not bother recording it, just have your system check for errors usingbadblocks
- so it's not just by chance (because you tried to use that sector), but the whole device [disk] can be scanned. Anything saved in the 'live' system is lost on shutdown/reboot (unless persistence is enabled, or youscp
etc. the file elsewhere)– guiverc
Nov 13 at 11:27
Unless you have enabled persistence, the log file won't save to the pen drive. A simple google search would have revealed the log location, though.
– Lewis Smith
Nov 13 at 11:27