On which device do you have your images stored, which mount point?
Problem with thumbnail cache
- Thread starter Muru
- Start date
On two devices on the HDD, at Downloads in Home and in a logical partition (fat32).
So the problem is on the same that on multiple disks the thumbnails won't load? Can you share in a screenshot what you see instead of the thumbnails?
Also check this topic out on the Linux Mint forums.
Last edited:
I can see the thumbnails. A message appears on top of them which says ' A problem has been detected on your thumbnail cache. Fixing it will require administrative privilege.' Two buttons below that "fix" and "ignore". Though I tried fixing as suggested it doesn't work. What I've noticed is that the laptop hangs once this message comes or I'm unable to write to the HDD. But I can write to the USB. At times the panel disappears. Menu button doesn't work.
I had missed that part.
Strange.
Try booting from a Linux Mint live iso with a usb flash drive and then running a filesystem check on all of your filesystems. I'm still getting the idea it's either a disk problem or filesystem problem with what yo are experience. If the problem still persists after running a filesystem check then what I would do is backup your files to an external hard disk and reinstall. Then check if you run into the same problem or not.
I've done that already. The problem persists.
A filesystem check on all disks or reinstall? If you have done both, a third option would be to install a different Linux Mint version to see what happens there and if still happens there then I would say it's a hardware problem.
I can't say what the "problem" in the message refers to, but there is something odd in the partitioning of the hard drive. It looks like it might be a 250G hard drive with about 50G unaccounted for or perhaps unallocated:
Code:
NAME FSTYPE FSVER FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 ext4 1.0 69.3G 19% /
├─sda2 vfat FAT32 182M 3% /boot/efi
├─sda3
├─sda5 vfat FAT32
├─sda6 vfat FAT32 126.9G 1% /media/murali/AUDIO-VIDEO
└─sda7 vfat FAT32
sr0What would be the rationale for such an odd partitioning arrangement? Particularly when the root partition will itself include a /media directory which the desktop environment would use in the normal way for mounting media.
If one wished to have a separate partition for storing audio-video files, then naming it something other than "media" would avoid confusion. A separate partition for such files would not be inappropriate for the case where the user wished to re-install the operating system on the root partition and not affect those audio-video files on their own partition.
But, what are the devices sda3, sda5 and sda7? The mystery is intriguing. The lsblk executable is usually able to show the sizes of all devices, but it appears to have failed here.
Last edited:
< /media/murali/AUDIO-VIDEO>
the media refers to directory in root partition. I guess it is shown in the output of lsblk because it was mounted. sda3 is most probably the extended partition and sda5 and sda7 refer to two other partition which I use for storing documents etc.
the media refers to directory in root partition. I guess it is shown in the output of lsblk because it was mounted. sda3 is most probably the extended partition and sda5 and sda7 refer to two other partition which I use for storing documents etc.
This is the output after running lsblk befor mounting any partition.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 93.2G 0 part /
├─sda2 8:2 0 191M 0 part /boot/efi
├─sda3 8:3 0 1K 0 part
├─sda5 8:5 0 146.8G 0 part
├─sda6 8:6 0 127.9G 0 part
└─sda7 8:7 0 97.7G 0 part
sdb 8:16 1 0B 0 disk
sr0 11:0 1 1024M 0 rom
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 93.2G 0 part /
├─sda2 8:2 0 191M 0 part /boot/efi
├─sda3 8:3 0 1K 0 part
├─sda5 8:5 0 146.8G 0 part
├─sda6 8:6 0 127.9G 0 part
└─sda7 8:7 0 97.7G 0 part
sdb 8:16 1 0B 0 disk
sr0 11:0 1 1024M 0 rom
Today when I first tried to boot up the following appeared:
systemd-journal failed to write. Ignoring: Read-only file system (22 items xxx bytes) and that line kept on repeating with the numbers changing. After doing a power off I
systemd-journal failed to write. Ignoring: Read-only file system (22 items xxx bytes) and that line kept on repeating with the numbers changing. After doing a power off I
Sorry. The net got cut off and the message became incomplete. So I'm repeating it.
Today when I first tried to boot up the following appeared:
systemd-journal failed to write. Ignoring: Read-only file system (22 items xxx bytes) and that line kept on repeating with the numbers changing. After doing a power off I switched on again after sometime and everything is running fine.
Today when I first tried to boot up the following appeared:
systemd-journal failed to write. Ignoring: Read-only file system (22 items xxx bytes) and that line kept on repeating with the numbers changing. After doing a power off I switched on again after sometime and everything is running fine.
@Muru welcome to linux.org 
I'll try not to interfere too much with the good work being done here by our helpers. They'll try not to believe me.
Could you share with us the output from the Terminal command, of
I'd like to look at the specs for your machine.
TIA
Chris Turner
wizardfromoz
I'll try not to interfere too much with the good work being done here by our helpers. They'll try not to believe me.
Could you share with us the output from the Terminal command, of
Code:
inxi -MI'd like to look at the specs for your machine.
TIA
Chris Turner
wizardfromoz
Machine:
Type: Laptop System: LENOVO product: 3259KCQ v: ThinkPad Edge E530
serial: MP2T3FT
Mobo: LENOVO model: 3259KCQ serial: 1ZM4D31M5H7 UEFI-[Legacy]: LENOVO
v: H0ETA0WW (2.60 ) date: 06/14/2018
OK thanks for that.
This may assist others to help more.
Your system BIOS have not had an upgrade in 6 years, you might want to attend to that.
The reference to UEFI-[Legacy] may account for the weird partitioning that @osprey referenced above.
If it were me, I would be looking to safeguard any data stored in /dev/sda5 , /dev/sda6, and /dev/sda7 and then install one more time, but if so, perform a standard installation (usually top one) to wipe drive and install. Do not choose "Other/Something Else".
That should provide a standard UEFI outcome rather than extended partitions and logical partitions.
While the unit dates back to 2014, the smartctl outputs seem to indicate it has life left in it.
Cheers
Wizard
This may assist others to help more.
Your system BIOS have not had an upgrade in 6 years, you might want to attend to that.
The reference to UEFI-[Legacy] may account for the weird partitioning that @osprey referenced above.
If it were me, I would be looking to safeguard any data stored in /dev/sda5 , /dev/sda6, and /dev/sda7 and then install one more time, but if so, perform a standard installation (usually top one) to wipe drive and install. Do not choose "Other/Something Else".
That should provide a standard UEFI outcome rather than extended partitions and logical partitions.
While the unit dates back to 2014, the smartctl outputs seem to indicate it has life left in it.
Cheers
Wizard
Will i be able to make the partitions later on? If these partitions are formatted as ext4 can files stored on them be opened when I send these files to someone who has a Windows machine? How do I upgrade the BIOS?
I would search
ThinkPad Edge E530 BIOS upgrade
and see if their support have a file available. If so, download it to a USB stick, look in your BIOS utility for a section on flashing the BIOS or upgrading the BIOS and go from there.
Yes. You would create them in the format of NTFS, and then they can be both shared with other Windows users, and also accessed from Linux.
Linux can detect Windows files but Windows can't with Linux.
I did this and ran lsblk. This is the output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 513M 0 part /boot/efi
└─sda3 8:3 0 465.3G 0 part /
