The folder contents could not be displayed.
Sorry, could not display the contents of "[folder name]": Error when getting information for file "/folder/folder/folder/folder/folder/file.ext": Input/output error
There's no helpful information in this error box. The file explorer just stays in the folder that is the grandparent to the file; it refuses to open the folder that is parent to the file.
The only thing any googling has told me is to run badblocks. Well, I did, this is the result after 56 hours:
Checking blocks 0 to 3906982911
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
So if there are no bad blocks (should never have been on such a new hard drive), what do I do to fix this?
Using "rm " does not work.
rm: cannot remove '<file>': Input/output error
So I can't delete it to even just redownload the file.
System Logs from searching Super-key "System Logs" and pressing Enter, then going to "All" section:
I am putting in all the logs from the time I found the logs up to when I plugged in the drive and navigated via nautilus to the folder and got the error.
Could not load a pixbuf from icon theme. NLThis may indicate the pixbuf loaders or the mime database could not be found.
[session uid=1000 pid=3911 Successfully activated service 'org.gnome.logs'
Unknown key gtk-primary-buttons-wraps-slider in /mytheme.ini
[session uid=1000 pid=3911] Successfully activated service 'org.gnome.Calculator.SearchProvider'
Unknown key gtk-primary-button-wraps-slider in /mytheme.ini
[session uid=1000 pid=3911] Successfully activated service 'org.gnome.Characters.BackgroundService'
systemd-hostnamed.service: Deactivated successfully
DING: Gjs-Message: 11:17:04.739: JS LOG: Couldn't parse protonvpn-app.desktop as a desktopfile, will treat it as a regular file.
[session uid=1000 pid=3911] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
Mounted /dev/sdb1 at /media/user/drivename on behalf of uid 1000
Global ownership and permissions enforced, configuration type 7
pam_unix(cron:session): session closed for user root
ntfs3: sdb1: volume is dirty and "force" flag is not set!
sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dv/sdb1' failed with exit code 1.
sd 11:0:0:0: [sdb] Attached SCSI disk
sdb: sdb1
sd 11:0:0:0: [sdb] Assuming drive cache: write through
.....ready
Started Hostname Service.
[system] Successfully activated service 'org.freekdesopt.hostname1'
Called "net usershare info" but it failed: failed to execute child process "net" (No such file or directory)
Starting Hostname Service...
[system] Activated via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' rquested by ':1.171' (uid=1000 pid=8555 comm=/usr/bind/nautilus --gap..."
ses 11:0:0:1: Failed to bind enclosure -19
sd 11:0:0:0: [sdb] Spinning up disk...
ses 11:0:0:0:1: Attached scsi generic sg2 type 13
sd 11:0:0:0: Attached scsi generic sg1 type 0
scsi 11:0:0:0:1: Enclosure WD SES Device 2007 PQ: 0 ANSI: 6
bus: 4, device: 3 was not an MTP device
scsi host11: usb-storage 4-1:1.0
usb-storage 4-1:1.0: USB Mass Storage device detected
usb 4-1: SerialNumber: snredacted
Now I just tried https://askubuntu.com/questions/112150/how-to-correctly-fix-a-dirty-ntfs-partition-without-using-chkdsk's suggestion for sudo ntfsfix -d /dev/sdb1 and it gave results:
refusing to operate on read-write mounted device /dev/sdb1
okay, unmount and try again
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1
NTFS partition /dev/sdb1 was processed successfully
Then I went back to nautilus and clicked on the drive name in the sidebar and then checked my logs again, this is what I have new up until the previous log entry that began/ended with the pixbuf from icon theme log message:
ntfs3: sdb1: MFT: r=b30, expect seq=1 instead of 2!
gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed
DING: Gjs-Message: 11:33:34.195: JS LOG: Couldn't parse protonvpn-app.desktop as a desktop file, will treat it as a regular file.
[session uid=1000 pid=3911] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
Mounted /dev/sdb1 at /media/user/name on behalf of uid 1000
+ sleep 3600
pam_unix(sudio:Session): session closed for user root
DING: Gjs-Message: 11:33:16.316: JS LOG: Couldn't parse protonvpn-app.desktop as a desktop file, will treat it as a regular file.
Unmounted /dev/sdb1 on behalf of uid 1000
media-user-name.mount: Deactivated successfully.
Cleaning up mount point /media/user/name (device 8:17 is not mounted)
Unmounting /dev/sdb1 (name)
pam_unix(sudo:session): session closed for user root
Can't update stage view actors <unnamed>[<MetaSurfaceActorX11>:0xhexid] is on becausse it nees an allocation.
Unknown key gtk-primary-button-wraps-slider in /mytheme.ini
[session uid=1000 pid=3911] Successfully acivated service 'org.gnome.Calculator.SearchProvider'
Unknown key gtk-primary-button-wraps-slider in /mytheme.ini
[session uid=1000 pid=3911] Successfully activated service 'org.gnome.Characters.BackgroundService'
Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0xhexid] is on because it needs an allocation.
anacron.service: Deactivated succesffully
Normal exit 90 jobs run)
STarted Run anacron jobs.
pam_unix(cron:session): session closed for user roote
(root) CMD ([ -x /etc/init.d/anacron ] && if [ ! - d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
pam_unix(cronsession): session opened for user root(uid=0 by (uid=0)
Can't update stage views actor <unnamed>[<MetaSurafceActorX11>:0xhexid] is on because it needs an allocation.
Could not laod a pixbuf from icon theme. NLThis may indicate that pixbuf loaders or the mime database could not be found.
badblocks) and logical issues where you use other tools appropriate to the file-system in use. You've not provided any specifics as to what you're using (what Ubuntu product & release) and what file-system is involved; thus we're limited in what help we can actually provide. Your unstated system logs may provide more clues too if you look, – guiverc Jan 01 '25 at 06:10But what caused it? Possibly trying to move 1/4 of the drive capacity from one folder to another. So maybe do it in chunks at a time instead to avoid the issue.
– Zyst Jan 06 '25 at 04:47