0

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.
Zyst
  • 1
  • 4
    IO errors can be related to physical issues (which you chase up using tools like 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:10
  • And I get system logs, where? Search "system logs"? No results. – Zyst Jan 01 '25 at 16:13
  • I'm on Linux Mint which I understand is a subversion or derivative of Ubuntu, and as this issue is fundamental to the OS, it doesn't matter what issue. I enjoy that you told me to use badblocks as if I didn't already tell you badblocks reported 0 issue. Being an external drive, I am moving it to Ubuntu 22.04 LTS and will find out that the input/output error is still there. Give me just a couple minutes to do that physical relocation process of the usb attached drive. – Zyst Jan 01 '25 at 16:14
  • I can confirm that this same drive accessed by Ubuntu 22.04 LTS does not load the folder/file in question. It gives the error same as above, except for Nautlius, it will use different language: This location could not be displayed and instead of "...could not display the contents...", the error message is "...could not display all the contents..." only difference is the word "all". Anyway, can we move on to further diagnostic criterion? – Zyst Jan 01 '25 at 16:19
  • System logs are a nothingburger that I can tell. Will edit in the system logs. Why they are in reverse order, who knows. But this going to be as verbatim as I can get. – Zyst Jan 01 '25 at 16:21
  • Well, systemlogs does tell me that Ubuntu and probably Mint want me to set the "force" flag. How do I do that? That would probably fix my issue and tell it to just load the files instead of making up a vague error? – Zyst Jan 01 '25 at 16:31
  • NTFS filesytems are best repaired from a Windows machine, which offers a more capable repair tool for NTFS. – ubfan1 Jan 01 '25 at 17:31
  • Only Ubuntu and official flavors of Ubuntu are on-topic here, refer https://askubuntu.com/help/on-topic where you'll find other SE sites where you question will be welcome if you don't want to use a Linux Mint forum. (One advantage of Ubuntu is its many support options, you opted for Linux Mint so take advantage of its support options, or SE Unix & Linux found in the on-topic link) – guiverc Jan 01 '25 at 20:40
  • Answer seems to be get on windows, use chkdsk or something, and then it will delete the indexes to your files. The files might be recoverable with a deleted-data recovery program. But for me, I just restored the files from a backup.

    But 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
  • @guiverc this problem persisted on ubuntu, I'm glad you asked me for my logs, I gave you my ubuntu logs, and you promptly ignored them. Cheers – Zyst Jan 06 '25 at 04:48

0 Answers0