error messages

D.P.W. · 2018-02-20 16:56

Dai_trying wrote:

As you do not appear to have apt running any processes I would have to leave this one for the dev team as it looks like their updater you are using and I have no experience with it.

Ok thanks for trying will the dev team see my message on this forum or do i need to contact them ? if so how ?
Thanks again for your time and effort.

Dai_trying · 2018-02-20 17:01

You're welcome, and I'm sure the dev team will read this and respond when they can, if you don't get any reply after a while you could email them, but they are usually quite attentive to forum posts.

q4osteam · 2018-02-20 17:23

@D.P.W.
Please run following commands in terminal:
$ df -h
$ sudo apt-get check
$ sudo dpkg --audit
and post output here to analyze

D.P.W. · 2018-02-21 15:40

q4osteam wrote:

@D.P.W.
Please run following commands in terminal:
$ df -h
$ sudo apt-get check
$ sudo dpkg --audit
and post output here to analyze

I have done as you asked this is what i got
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 382M 5.8M 377M 2% /run
/dev/sda2 28G 4.9G 22G 19% /
tmpfs 1.9G 16M 1.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/sda3 262G 133M 248G 1% /home
tmpfs 382M 8.0K 382M 1% /run/user/1000

david@laptop:~$ sudo apt-get check
Reading package lists... Done
Building dependency tree
Reading state information... Done

david@laptop:~$ sudo dpkg --audit
david@laptop:~$

as you can see for the last command i did not get anything at all i would also like to add that to get Q4OS to start up i had to do this again

fsck /dev/sda2 then reboot

q4osteam · 2018-02-21 16:07

Looks good, now run commands:
$ mount
$ check-apt-busy
$ sudo sh /usr/share/apps/q4os_system/bin/qapt_fix.sh
and post output here to analyze

D.P.W. · 2018-02-21 16:31

q4osteam wrote:

Looks good, now run commands:
$ mount
$ check-apt-busy
$ sudo sh /usr/share/apps/q4os_system/bin/qapt_fix.sh
and post output here to analyze

this is what i got

david@laptop:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1939524k,nr_inodes=484881,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=391052k,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=2461)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sda3 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=391048k,mode=700,uid=1000,gid=1000)

david@laptop:~$ check-apt-busy for this one i got nothing

david@laptop:~$ sudo sh /usr/share/apps/q4os_system/bin/qapt_fix.sh
[sudo] password for david:
Waiting for package system to be released ..
Seems ready, will be checked once more.
Now safe ready.
Done.
Checking package system ..
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package system ok.

q4osteam · 2018-02-21 16:49

Looks good as well, now run:
$ /opt/program_files/q4os-update-manager/bin/updatemgr.exu
and report back

$ /usr/share/apps/q4os_system/bin/qapt_lock.exu --lock
are you able to lock apt using the command above ?

D.P.W. · 2018-02-21 17:00

q4osteam wrote:

Looks good as well, now run:
$ /opt/program_files/q4os-update-manager/bin/updatemgr.exu
and report back
$ /usr/share/apps/q4os_system/bin/qapt_lock.exu --lock
are you able to lock apt using the command above ?

i get this message do i click on yes or no

The following packages were automatically installed and are no longer required:
libc-dev-bin (2.24-11+deb9u1)
linux-libc-dev (4.9.65-3+deb9u2)
manpages-dev (4.10-2)

D.P.W. · 2018-02-21 17:04

q4osteam wrote:

Looks good as well, now run:
$ /opt/program_files/q4os-update-manager/bin/updatemgr.exu
and report back
$ /usr/share/apps/q4os_system/bin/qapt_lock.exu --lock
are you able to lock apt using the command above ?

i get this when i type in the second command

david@laptop:~$ /usr/share/apps/q4os_system/bin/qapt_lock.exu --lock
Locked OK
Waiting for stdin

q4osteam · 2018-02-21 19:07

Ok, reboot and run in terminal:
$ sudo apt-get autoremove
your system should be fine now.

D.P.W. · 2018-02-22 16:27

q4osteam wrote:

Ok, reboot and run in terminal:
$ sudo apt-get autoremove
your system should be fine now.

Hi after doing the above i got this is it what i should have got ?

Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
libc-dev-bin linux-libc-dev manpages-dev
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 8,783 kB disk space will be freed.
W: Not using locking for read only lock file /var/lib/dpkg/lock
W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - Setu pAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/cache/apt/archives/partial failed - SetupAPTPart ialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/cache/apt/archives/lock
Do you want to continue? [Y/n] y
dpkg: error: unable to access dpkg status area: Read-only file system
W: Problem unlinking the file /var/log/apt/eipp.log.xz - FileFd::Open (30: Read- only file system)
W: Could not open file /var/log/apt/eipp.log.xz - open (17: File exists)
W: Could not open file '/var/log/apt/eipp.log.xz' - EIPP::OrderInstall (17: File exists)
E: Could not create temporary file for /var/lib/apt/extended_states - mkstemp (3 0: Read-only file system)
E: Failed to write temporary StateFile /var/lib/apt/extended_states
E: Sub-process dpkg --set-selections returned an error code (2)
E: Couldn't record the approved state changes as dpkg selection states

D.P.W. · 2018-02-22 16:50

D.P.W. wrote:

q4osteam wrote:
Ok, reboot and run in terminal:
$ sudo apt-get autoremove
your system should be fine now.
Hi after doing the above i got this is it what i should have got ? also i can no longer open synaptic package or libre office how do i get them working again ?
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
libc-dev-bin linux-libc-dev manpages-dev
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 8,783 kB disk space will be freed.
W: Not using locking for read only lock file /var/lib/dpkg/lock
W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - Setu pAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/cache/apt/archives/partial failed - SetupAPTPart ialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/cache/apt/archives/lock
Do you want to continue? [Y/n] y
dpkg: error: unable to access dpkg status area: Read-only file system
W: Problem unlinking the file /var/log/apt/eipp.log.xz - FileFd::Open (30: Read- only file system)
W: Could not open file /var/log/apt/eipp.log.xz - open (17: File exists)
W: Could not open file '/var/log/apt/eipp.log.xz' - EIPP::OrderInstall (17: File exists)
E: Could not create temporary file for /var/lib/apt/extended_states - mkstemp (3 0: Read-only file system)
E: Failed to write temporary StateFile /var/lib/apt/extended_states
E: Sub-process dpkg --set-selections returned an error code (2)
E: Couldn't record the approved state changes as dpkg selection states

q4osteam · 2018-02-23 20:36

Looks more like a hardware issue. If you want to try to investigate it more, run following commands, one right after each other:
$ sudo apt-get check
$ sudo apt-get autoremove
$ mount
and post output here. We will check it and post back.

We would also recommend you to boot from the live media and run hard drive scan from terminal:
$ sudo badblocks -s /dev/sda
it will scan the hard drive for physically damaged blocks.

D.P.W. · 2018-02-25 16:24

q4osteam wrote:

Looks more like a hardware issue. If you want to try to investigate it more, run following commands, one right after each other:
$ sudo apt-get check
$ sudo apt-get autoremove
$ mount
and post output here. We will check it and post back.
We would also recommend you to boot from the live media and run hard drive scan from terminal:
$ sudo badblocks -s /dev/sda
it will scan the hard drive for physically damaged blocks.

This is the results of hard drive scan i have only pasted the top and bottom half if i am looking at it right no damage was found so does that mean my hard drive is ok ?

Checking for bad blocks (read-only test): 0.00% done, 0:00 elapsed. (0/0/0 err 55293544done, 11:35 elapsed. (0/0/0 errors)
55293545done, 11:37 elapsed. (1/0/0 errors)
55293546done, 11:40 elapsed. (2/0/0 errors)
55293547done, 11:43 elapsed. (3/0/0 errors)
55293548done, 11:45 elapsed. (4/0/0 errors)
55293549done, 11:48 elapsed. (5/0/0 errors)
55293550done, 11:51 elapsed. (6/0/0 errors)
55293551done, 11:53 elapsed. (7/0/0 errors)
55293552done, 11:56 elapsed. (8/0/0 errors)
55293553done, 11:59 elapsed. (9/0/0 errors)
55293554done, 12:01 elapsed. (10/0/0 errors)
55293555done, 12:04 elapsed. (11/0/0 errors)
55293556done, 12:07 elapsed. (12/0/0 errors)
55293557done, 12:09 elapsed. (13/0/0 errors)
55293558done, 12:12 elapsed. (14/0/0 errors)
55293559done, 12:15 elapsed. (15/0/0 errors)
55293560done, 12:17 elapsed. (16/0/0 errors)
55293561done, 12:20 elapsed. (17/0/0 errors)
55293562done, 12:23 elapsed. (18/0/0 errors)
63743868done, 14:17 elapsed. (19/0/0 errors)
63743869done, 14:19 elapsed. (20/0/0 errors)

272621827one, 2:01:06 elapsed. (303/0/0 errors)
272657496one, 2:01:10 elapsed. (304/0/0 errors)
272657497one, 2:01:13 elapsed. (305/0/0 errors)
272657498one, 2:01:16 elapsed. (306/0/0 errors)
272657499one, 2:01:18 elapsed. (307/0/0 errors)
272659816one, 2:01:22 elapsed. (308/0/0 errors)
272659817one, 2:01:24 elapsed. (309/0/0 errors)
272659818one, 2:01:27 elapsed. (310/0/0 errors)
272659819one, 2:01:30 elapsed. (311/0/0 errors)
272659820one, 2:01:33 elapsed. (312/0/0 errors)
272659821one, 2:01:36 elapsed. (313/0/0 errors)
272659822one, 2:01:38 elapsed. (314/0/0 errors)
272659823one, 2:01:41 elapsed. (315/0/0 errors)
272661516one, 2:01:45 elapsed. (316/0/0 errors)
272661517one, 2:01:47 elapsed. (317/0/0 errors)
272661518one, 2:01:50 elapsed. (318/0/0 errors)
272661519one, 2:01:53 elapsed. (319/0/0 errors)
272661520one, 2:01:55 elapsed. (320/0/0 errors)
272661521one, 2:01:58 elapsed. (321/0/0 errors)
272661522one, 2:02:01 elapsed. (322/0/0 errors)
272661523one, 2:02:03 elapsed. (323/0/0 errors)
done
adminq@debian:~$

D.P.W. · 2018-02-25 17:21

q4osteam wrote:

Looks more like a hardware issue. If you want to try to investigate it more, run following commands, one right after each other:
$ sudo apt-get check
$ sudo apt-get autoremove
$ mount
and post output here. We will check it and post back.
We would also recommend you to boot from the live media and run hard drive scan from terminal:
$ sudo badblocks -s /dev/sda
it will scan the hard drive for physically damaged blocks.

This is what i got when i ran the above commands

Reading package lists... Done
Building dependency tree
Reading state information... Done
david@laptop:~$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
david@laptop:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1939524k,nr_inodes=484881,mo
de=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmod
e=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=391052k,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relat
ime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xa
ttr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatim
e,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,re latime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime ,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,de vices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,fr eezer)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,mem ory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blki o)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpu set)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,time out=0,minproto=5,maxproto=5,direct,pipe_ino=11543)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sda3 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=391048k,mode=7 00,uid=1000,gid=1000)
david@laptop:~$

bin · 2018-02-26 09:06

Forgive me for butting in on this, but the original post was identical to an issue I had on my machine a few weeks back. The drive had developed some bad sectors and was mounting read only. Smartmontools was ideal for testing the drive which I have wiped and reinstalled, which should ignore bad sectors, but no way will it be used for anything other than experimenting with installs.

I would seriously suggest that replacing the drive might save a whole lot of back and forth over an issue that cannot be resolved by the current approach

@D.P.W Out of interest, have you modified your /etc/fstab file at any time?

q4osteam · 2018-02-26 09:54

Looks like your harddrive is sometimes mounted read only. The command 'sudo apt-get autoremove' failed for the first time, while second time passed well. It would show some kind of hardware problem. Please follow bin's advice from his post above https://www.q4os.org/forum/viewtopic.ph … 174#p12174

D.P.W. · 2018-02-26 09:56

bin wrote:

Forgive me for butting in on this, but the original post was identical to an issue I had on my machine a few weeks back. The drive had developed some bad sectors and was mounting read only. Smartmontools was ideal for testing the drive which I have wiped and reinstalled, which should ignore bad sectors, but no way will it be used for anything other than experimenting with installs.
I would seriously suggest that replacing the drive might save a whole lot of back and forth over an issue that cannot be resolved by the current approach
@D.P.W Out of interest, have you modified your /etc/fstab file at any time?

Hi i have not knowingly modified my etc/fstab file unless it has been done while following instructions sent to me via this forum.
Have you looked at my hard drive scan results ? am i right in saying that no faults have been found ?

q4osteam · 2018-02-26 10:15

D.P.W. wrote:

Have you looked at my hard drive scan results ? am i right in saying that no faults have been found ?

Yes, found no faults, but it doesn't mean it's faultless.

jackdanielsesq · 2018-02-26 10:40

DPW

Looks like a truncated file system - you need to run gparted, et al, .. repair/reformat the file system
Then setup a partition somewhere where there was little activity - end of the drive & install the O/S
Some of us do not always have the luxury of running out to Newegg or Prime for that new HHD/SSD
I have repaired many of our servers this way ... I am currently on such a HHD - its perfect
Only MSFT cares about C:\ - Unix not so much

Regards

Jack

D.P.W. · 2018-02-26 10:40

q4osteam wrote:

Looks like your harddrive is sometimes mounted read only. The command 'sudo apt-get autoremove' failed for the first time, while second time passed well. It would show some kind of hardware problem. Please follow bin's advice from his post above https://www.q4os.org/forum/viewtopic.ph … 174#p12174

Hi thank you all for your advice i do not have a spare hard drive but i do have a 32GB memory stick can i plug this into my laptop and install/run Q4OS from it ? so i can test it out before getting a new hard drive.

jackdanielsesq · 2018-02-26 10:42

Hi ...

See my previous post

Regards

Jack

D.P.W. wrote:

q4osteam wrote:
Looks like your harddrive is sometimes mounted read only. The command 'sudo apt-get autoremove' failed for the first time, while second time passed well. It would show some kind of hardware problem. Please follow bin's advice from his post above https://www.q4os.org/forum/viewtopic.ph … 174#p12174
Hi thank you all for your advice i do not have a spare hard drive but i do have a 32GB memory stick can i plug this into my laptop and install/run Q4OS from it ? so i can test it out before getting a new hard drive.

D.P.W. · 2018-02-26 10:51

jackdanielsesq wrote:

DPW
Looks like a truncated file system - you need to run gparted, et al, .. repair/reformat the file system
Then setup a partition somewhere where there was little activity - end of the drive & install the O/S
Some of us do not always have the luxury of running out to Newegg or Prime for that new HHD/SSD
I have repaired many of our servers this way ... I am currently on such a HHD - its perfect
Only MSFT cares about C:\ - Unix not so much
Regards
Jack

Hi how do i do the above ?

Q4OS Forum

#26 2018-02-20 16:56

Re: error messages

#27 2018-02-20 17:01

Re: error messages

#28 2018-02-20 17:23

Re: error messages

#29 2018-02-21 15:40

Re: error messages

#30 2018-02-21 16:07

Re: error messages

#31 2018-02-21 16:31

Re: error messages

#32 2018-02-21 16:49

Re: error messages

#33 2018-02-21 17:00

Re: error messages

#34 2018-02-21 17:04

Re: error messages

#35 2018-02-21 19:07

Re: error messages

#36 2018-02-22 16:27

Re: error messages

#37 2018-02-22 16:50

Re: error messages

#38 2018-02-23 20:36

Re: error messages

#39 2018-02-25 16:24

Re: error messages

#40 2018-02-25 17:21

Re: error messages

#41 2018-02-26 09:06

Re: error messages

#42 2018-02-26 09:54

Re: error messages

#43 2018-02-26 09:56

Re: error messages

#44 2018-02-26 10:15

Re: error messages

#45 2018-02-26 10:40

Re: error messages

#46 2018-02-26 10:40

Re: error messages

#47 2018-02-26 10:42

Re: error messages

#48 2018-02-26 10:51

Re: error messages

Board footer