Data SSD gone read only [Solved]

[ornithorhynchus]

Thanks LS1.

Here's the result of mount:

Code: Select all

$ mount -v
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=8110380k,nr_inodes=2027595,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1630836k,mode=755,inode64)
/dev/sda2 on / type ext4 (rw,noatime,discard)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,relatime)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
pstore on /sys/fs/pstore type pstore (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3261660k,inode64)
/dev/sda1 on /boot/efi type vfat (rw,noatime,fmask=0113,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/sda3 on /home type ext4 (rw,noatime,discard)
/dev/sdb1 on /home/sherbet/rootMX19 type ext4 (rw,relatime)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,size=12k,mode=755,inode64)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/run/cgmanager/agents/cgm-release-agent.systemd,name=systemd)
tmpfs on /run/user/112 type tmpfs (rw,nosuid,nodev,relatime,size=1630832k,mode=700,uid=112,gid=121,inode64)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1630832k,mode=700,uid=1000,gid=1000,inode64)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdd3 on /media/beegees/homeMX type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/dev/sdc1 on /media/beegees/dData type ext4 (ro,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)

And the fstab:

Code: Select all

$  cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=a67d2f14-455c-428a-8115-a809d8ce6040   /                        ext4   discard,noatime                 1 1 
UUID=AFE5-F5A0                              /boot/efi                vfat   noatime,dmask=0002,fmask=0113   0 0 
UUID=90435d99-9c5a-4995-b4d7-1390b10a90fe   /home                    ext4   discard,noatime                 1 0 
/swap/swap                                  swap                     swap   defaults                        0 0 
LABEL=rootMX19                              /home/sherbet/rootMX19   ext4   defaults                        0 0  

Regarding the fstab info.

MX23 mounted OK this morning and it's the first three entries above, viz.
sda1 is /boot/efi above, UUID...F5AO.
sda2 is / above, UUID ...6040
sda3 is /home above, UUID ...98FE

Those 3 partitions are what you listed from my quick system info yesterday - when the drive was sdc, rather than sda as it is today.

Additionally, I have 3 other SSDs mounted today:
sdb: It's my disk that's currently unused. It has old MX19 on it that I've not used since installing MX23. (home/sherbet/rootMX19 above)
sdc: My data disk that isn't listed above.
sdd: AVLinux that I'm not currently using and that isn't listed above.

Hope this info can give you more insight?

Thanks and cheers.

[Arnox]

What was the result of updating the kernel? Have you tried manually dismounting and remounting the drive with explicit read and write enabled as @LinuxSpring1 suggested?

[siamhie]

Here's the result of mount:

Code: Select all

$ mount -v
/dev/sdc1 on /media/beegees/dData type ext4 (ro,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)

sdc: My data disk that isn't listed above.


Hope this info can give you more insight?

Thanks and cheers.

SDC shows ro (read only). All other drives showed rw (read write).

[ornithorhynchus]

Thanks Arnox.

I haven't yet dismounted and remounted the data disk per LinuxSpring suggestion. I thought I'd wait until they've seen the results they requested.

And I haven't yet updated the kernel. That seems a more tricky task than the LinuxSpring suggestion, so I thought I'd do that after doing LinuxSpring's suggestions.

Thanks Siamhle.

Thanks for that observation. I can see it now too. It looks to me that observation supports the LinuxSpring suggestion to unmount and remount. But I'll wait to see if LinuxSpring has anything to add before I do it.

Again, Thanks to all.

Cheers.

[siamhie]

Thanks Siamhle.

Thanks for that observation. I can see it now too. It looks to me that observation supports the LinuxSpring suggestion to unmount and remount. But I'll wait to see if LinuxSpring has anything to add before I do it.

Again, Thanks to all.

Cheers.

@ornithorhynchus Disk Manager can set up other partitions to be mounted at boot time.

disk.png

[ornithorhynchus]

Thanks people.

I've unmounted my data disk but can't get it to remount using the remount command. I don't think I understand that command. But I can remount using KDE Partition Manager. When I do this the data disk appears as "RW" in the list resulting from the command mount -v.

However, this new RW status for my data drive doesn't survive reboot.

I have an unused disk - the one containing the remnants of MX19. I've established a new partition on that disk for data and copied one of my data directories to it. The "RW" status of that new partition does survive reboot. I've deleted the other, old, partition on that disk and plan to continue transferring my data files to that disk. I plan to shred the files on what would then be an old data disk once I've completed transferring files.

I think this will resolve my problem for the present. But I'll explore other options suggested here (e.g. updating the kernel) once I've completed copying the files.

Will keep you posted on that.

Meanwhile, thanks to everyone for helping here. I really appreciate it.

Cheers to all.

[siamhie]

However, this new RW status for my data drive doesn't survive reboot.

I don't recall if disk-manager comes installed with MX KDE but you can find it in the repos. Open Package Installer (MX Tools).

disk-manager.jpg

[rokytnji.1]

On my 1 TB external USB drive formatted as ntfs to hold backups. Everything disappeared. Even file system.
Thought the drive had died after looking at it in gparted.

Made and new msdos btrfs partition of the whole drive. Mounts , copy, paste, OK again.
Don't need ntfs as I don't use windows anymore.

This is probably a apples and orange post. Since my drive is probably a mini spinner instead of sdd.
I had some backups of my backups on another 3 TB external drive I could copy from.
Will see if this fix lasts for me.

[ornithorhynchus]

I've fixed my problem now.

I've transferred my data files to the new disk that I now use as my data disk.

I tried to update the kernel. In fact I downloaded one (6.5.11-4-liquorix-AMD64) and it's listed in MX Boot Options as one of the alternatives that Advanced Options for MX23.3 Libretto offers. However, when I boot up, the Advanced Options for MX23.3 still offers only one choice - 6.1.0-10-amd64. So I don't know what's happening here.

Anyways, I have good access to my data disk and the system boots up OK.

Thanks heaps to all for your thoughts.

Cheers.

[Charlie Brown]

The one shown in MXBO is to (enable you) select any of them to make the default ("Boot to").

Since 6.5.x is the highest numbered one in your case, it's become the default by itself and the older ones (6.1 in this case) got into Advanced Options... So, everything's normal :)

(That's to say: One can manually change the default one to an older kernel via MXBO for whatever reason).