You are not logged in.
Thanks MiyoLinux, it was the second one that I am familiar with.
Something about the Deepin startup sound is like fingernails on a chalk board.
Hi MiyoLinux, your ascii release of Miyo had a startup 'song' included, which is not in Miyo based on ceres. Do you still have the file of that? Right now I'm being sacrilegious and using the Windows XP startup sound.
Earlier I used the sudo smartctl -a /dev/sdc command. It shows this:
$ sudo smartctl -a /dev/sdc
[sudo] password for ron:
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-1-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 7200.5
Device Model: ST9500424AS
Serial Number: - redacted -
LU WWN Device Id: - redacted -
Firmware Version: 0001BSM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Wed Nov 24 21:16:47 2021 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
- - snip - -
I was able to test my two internal drives (they both passed), but I'm getting an error message trying to test the portable drive:
sudo smartctl -d ata -H /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-1-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: Invalid argument
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
EDIT
Okay, I'm not sure if this was right, but I changed ata in the command to scsi, and that came back like this. On the internal drives it reads PASSED, but with this it reads OK. Did I do it right?
sudo smartctl -d scsi -H /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-1-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
I'm just scratching my head now as to why I got that error message in the first place.
Thanks to all, especially Altoid.
I would strongly recommend a SMART test on that device.
Noted. I would need to download smart-notifier for that, right? I'm guessing its use would be self-explanatory.
Thanks for all your help.
ron@ron:~$ sudo apt update && sudo apt upgrade
--- snip ---
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Did all three of the above. To me, it looks like there isn't a problem (which makes me wonder why I got that error message). Or am I mistaken?
$ sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
gnome-desktop3-data libfluidsynth2 libgnome-desktop-3-19 libxkbregistry0
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 3,892 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 287054 files and directories currently installed.)
Removing libgnome-desktop-3-19:amd64 (41.1-1) ...
Removing gnome-desktop3-data (41.1-1) ...
Removing libfluidsynth2:amd64 (2.1.7-1.1) ...
Removing libxkbregistry0:amd64 (1.3.1-1) ...
Processing triggers for libc-bin (2.32-4) ...
$ sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ sudo apt-get install --reinstall linux-image-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1,480 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 286777 files and directories currently installed.)
Preparing to unpack .../linux-image-amd64_5.15.3-1_amd64.deb ...
Unpacking linux-image-amd64 (5.15.3-1) over (5.15.3-1) ...
Setting up linux-image-amd64 (5.15.3-1) ...
sudo apt-get install --fix-broken returned this:
$ sudo apt-get install --fix-broken
[sudo] password for ron:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
gnome-desktop3-data libfluidsynth2 libgnome-desktop-3-19 libxkbregistry0
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
From /var/log/apt/term.log
Setting up linux-image-5.15.0-1-amd64 (5.15.3-1) ...
Segmentation fault
dpkg: error processing package linux-image-5.15.0-1-amd64 (--configure):
installed linux-image-5.15.0-1-amd64 package post-installation script subprocess returned error exit status 139
and
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-5.15.0-1-amd64 (= 5.15.3-1); however:
Package linux-image-5.15.0-1-amd64 is not configured yet.
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured.
and
Errors were encountered while processing:
linux-image-5.15.0-1-amd64
linux-image-amd64
Log ended: 2021-11-20 17:21:37
From /var/log/dpkg.log
2021-11-20 17:21:37 configure linux-image-5.15.0-1-amd64:amd64 5.15.3-1 <none>
2021-11-20 17:21:37 status half-configured linux-image-5.15.0-1-amd64:amd64 5.15.3-1
2021-11-20 17:21:52 status installed linux-image-5.15.0-1-amd64:amd64 5.15.3-1
2021-11-20 17:21:52 configure linux-image-amd64:amd64 5.15.3-1 <none>
2021-11-20 17:21:52 status unpacked linux-image-amd64:amd64 5.15.3-1
2021-11-20 17:21:52 status half-configured linux-image-amd64:amd64 5.15.3-1
2021-11-20 17:21:52 status installed linux-image-amd64:amd64 5.15.3-1
The inxi report shows the new kernel running, like I wrote in the original post. Did something really go wrong?
$ inxi -Fxz
System: Kernel: 5.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: MATE 1.24.1
Distro: Devuan GNU/Linux 5 (daedalus/ceres)
Machine: Type: Desktop System: ASUS product: All Series v: N/A serial: <filter>
Mobo: ASUSTeK model: H81M-C v: Rev X.0x serial: <filter> BIOS: American Megatrends v: 3602 date: 03/26/2018
CPU: Info: Dual Core model: Intel Pentium G3220 bits: 64 type: MCP arch: Haswell rev: 3 cache: L2: 3 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 11972
Speed: 1297 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 1297 2: 1297
Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel
bus-ID: 00:02.0
Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (HSW GT1) v: 4.5 Mesa 21.2.5 direct render: Yes
Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.15.0-1-amd64 running: yes
Sound Server-2: PipeWire v: 0.3.40 running: no
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK H81M-C driver: r8169 v: kernel
port: e000 bus-ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 387.53 GiB used: 161.03 GiB (41.6%)
ID-1: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3160815AS size: 149.05 GiB
Partition: ID-1: / size: 233.72 GiB used: 77.42 GiB (33.1%) fs: ext4 dev: /dev/sda5
Swap: ID-1: swap-1 type: file size: 256 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info: Processes: 156 Uptime: 16m Memory: 3.71 GiB used: 1.24 GiB (33.5%) Init: SysVinit runlevel: 2 Compilers:
gcc: 11.2.0 Packages: 1624 Shell: Bash v: 5.1.8 inxi: 3.3.0
Marked as solved. Thanks to everyone who responded, especially hevidevi and HoaS.
So I updated my system via Synaptic, and after applying the changes this error message popped up. Is it anything to worry about? I rebooted the computer and it booted just fine, and is using the newest kernel.
That seems to have fixed it. Thanks hevidevi.
I'm going to wait a day or two before marking it as solved.
Okay, here is some new info. I don't think my portable drive is dead after all. I was backing up my files last night to my wife's portable drive that was working when I remembered I wanted the drive to be formatted as ext4, just like my portable drive was. So this morning I did that, and lo and behold, the drive was no longer writable. So then I formatted it again, back to ntfs, and then it was writable again. How can I make these drives writable as ext4? I did this with ascii no problem (at least on my portable drive). Why isn't it working with Miyo/Devuan 5?
So I deleted the partition, created a new one, and then formatted it. Still can't write to it. Tomorrow I'm taking a hammer to it, so if it isn't dead yet, it sure will be tomorrow.
Also, after a semi-long search I found my wife's portable drive. It is one year younger, and much less used than mine (also a WD brand). I can read and write to that one, so I'm pretty sure mine is dead.
Thanks for your help HoaS (and also Altoid).
I'll try reformatting it later when I have some free time and see what happens.
Here's the output:
ron@ron:~$ sudo -i
[sudo] password for ron:
root@ron:~# mount /dev/sdc1 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
root@ron:~# touch /mnt/test
touch: cannot touch '/mnt/test': Read-only file system
Apparently when it is first plugged in, it appears to be read and write, but when I try to do something, it switches to read only. Two examples:
1) After plugging it in, if I right click in it (after browsing to it), the Create Folder and Create File options are not greyed out. But when I click either one of them, I get an error message that says it is read only and after that those two options are greyed out.
2) After plugging it in, if I open a simple text file on it (with Pluma), the file appears to be editable, but once I make the first change, it becomes read only (I notice this in the title bar of Pluma).
After doing one of the above two, I get the following from the sudo hdparm -r /dev/sdc command (which is weird because I can still see it and open files on it):
$ sudo hdparm -r /dev/sdc
[sudo] password for ron:
/dev/sdc: No such file or directory
Does this suggest the drive is going bad?
ron@ron:~$ sudo hdparm -r /dev/sdc
/dev/sdc:
readonly = 0 (off)
So how do I go about getting it to be read and write?
Starting over:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1389.547030] add /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
KERNEL[1389.548485] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
KERNEL[1389.548702] add /devices/virtual/workqueue/scsi_tmf_6 (workqueue)
KERNEL[1389.548969] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6 (scsi)
KERNEL[1389.549028] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/scsi_host/host6 (scsi_host)
KERNEL[1389.549037] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
KERNEL[1389.549048] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
UDEV [1389.549695] add /devices/virtual/workqueue/scsi_tmf_6 (workqueue)
UDEV [1389.551244] add /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
UDEV [1389.552097] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
UDEV [1389.552475] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6 (scsi)
UDEV [1389.552832] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/scsi_host/host6 (scsi_host)
UDEV [1389.553134] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
UDEV [1389.555279] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
KERNEL[1390.558442] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0 (scsi)
KERNEL[1390.558491] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
KERNEL[1390.558514] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device)
KERNEL[1390.558682] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 (scsi_disk)
KERNEL[1390.558758] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg3 (scsi_generic)
KERNEL[1390.558803] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg)
UDEV [1390.559216] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0 (scsi)
UDEV [1390.559618] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1390.560264] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1390.560583] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg3 (scsi_generic)
UDEV [1390.560877] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device)
UDEV [1390.561434] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg)
KERNEL[1390.573484] add /devices/virtual/bdi/8:32 (bdi)
UDEV [1390.573697] add /devices/virtual/bdi/8:32 (bdi)
KERNEL[1390.625690] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc (block)
KERNEL[1390.625768] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
KERNEL[1390.627859] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1390.812088] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc (block)
UDEV [1391.023795] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
UDEV [1391.024599] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
KERNEL[1391.169704] change /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
UDEV [1391.234629] change /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
sda, sdb, etc., etc. Boy I feel real dumb, I know this. Anyway nothing happened until I put sudo before the command, then the following came up:
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user]
[VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user] file ...
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[162.006144] add /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
KERNEL[162.007127] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
KERNEL[162.007160] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
UDEV [162.011054] add /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
KERNEL[162.019548] add /devices/virtual/workqueue/scsi_tmf_6 (workqueue)
KERNEL[162.020203] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6 (scsi)
KERNEL[162.020351] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/scsi_host/host6 (scsi_host)
UDEV [162.020393] add /devices/virtual/workqueue/scsi_tmf_6 (workqueue)
KERNEL[162.020484] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
KERNEL[162.020531] add /bus/usb/drivers/usb-storage (drivers)
KERNEL[162.020573] add /module/usb_storage (module)
UDEV [162.020831] add /bus/usb/drivers/usb-storage (drivers)
UDEV [162.021138] add /module/usb_storage (module)
KERNEL[162.022923] add /bus/usb/drivers/uas (drivers)
KERNEL[162.023104] add /module/uas (module)
UDEV [162.023114] add /bus/usb/drivers/uas (drivers)
UDEV [162.023127] add /module/uas (module)
UDEV [162.023235] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
UDEV [162.025726] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5 (usb)
UDEV [162.026196] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6 (scsi)
UDEV [162.026588] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/scsi_host/host6 (scsi_host)
UDEV [162.026907] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0 (usb)
KERNEL[163.041331] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0 (scsi)
KERNEL[163.041387] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
KERNEL[163.041413] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device)
KERNEL[163.041960] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 (scsi_disk)
KERNEL[163.041991] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg3 (scsi_generic)
UDEV [163.042104] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0 (scsi)
KERNEL[163.042333] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg)
UDEV [163.042815] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [163.043656] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device)
UDEV [163.043668] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [163.043873] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg3 (scsi_generic)
UDEV [163.044464] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg)
KERNEL[163.064113] add /devices/virtual/bdi/8:32 (bdi)
UDEV [163.064386] add /devices/virtual/bdi/8:32 (bdi)
KERNEL[163.114499] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc (block)
KERNEL[163.114521] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
KERNEL[163.115830] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [163.291568] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc (block)
UDEV [163.497124] add /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
UDEV [163.497928] bind /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0 (scsi)
KERNEL[163.683472] change /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
UDEV [163.735045] change /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/host6/target6:0:0/6:0:0:0/block/sdc/sdc1 (block)
I feel really dumb saying this, but regarding your second instruction, I don't know what you mean by "the letter assigned to the drive."
Thanks once again.
Okay, this is a noobish question. I just installed Miyo Linux and I'm having problems with a Seagate portable drive. I can plug it in but it's read only. It has worked before I installed Miyo, so I'm thinking it is a permission problem, although the drive is old and it's possible it's failing. FTR, I can write to my flash drive. How to check the permission? When I right click the drive's icon and select properties, then select the permissions tab, it says there "The permissions of "Seagate Backup" could not be determined."
Thanks for your quick response MiyoLinux. I also noticed a bunch of apps that begin with libxfce..... and I'm hesitant to delete those. Should I not touch those?
Running Miyo ceres. I installed Mate and deleted Openbox. Can I delete the Xfce power manager without any consequences? I ask because in my notes for the old version of Miyo it says don't deleted it (I'm assuming that instruction came from MiyoLinux but it's been so long ago I can't remember). However, I know it's not running and the Mate manager is.
Okay, so I installed it and so far things are well. Actually, they're better. A week ago I installed the current Devuan, and I was getting horrible screen tearing in my browser. On this Miyo (ceres) I'm not. 👍 Any idea what is the difference?