Calling occupants of interplanetary craft ( Or just Ubuntu Users)

[Green Baron]

1 minute ago, NewtSoup said:

I will try restarting the keyring daemon as you say and then let you know if I can access my 4s

I forgot "sudo ..."

[NewtSoup]

Just now, Green Baron said:

I forgot "sudo ..."

that's ok  I'd have got that one.  I'm at average user level not quite understanding how the whole operating system works yet though.  I can add and remove and purge software and install and remove drivers.

cant' find my 4s cable which makes no sense as it's always on my desk

[Green Baron]

No problem :-)

If you get error messages it would be nice to have those.

System logs in /var/log, e.g. daemon.log, messages, syslog, kern.log sometimes can contain info as well. Just saying. It is always good to have as much info as possible ...

[NewtSoup]

So I shut down the keyring using  sudo killall blah blah

I plug my 4S in and I get the following error:

No such interface 'org.gtk.vfs.Mount' on object at path /org/gtk/vfs/mount/1

Clicking on the "camera" icon representing the phone does :  Error initialising camera: -7: I/O problem

and I get no screenshots at all at the moment.

Now to restart the keyring daemon using the command you gave me - I get

 

sudo gnome-keyring-daemon --start --daemonize
	** (gnome-keyring-daemon:12388): WARNING **: couldn't create socket directory: /home/ruth/.cache/keyring-9J9MFZ: Permission denied
	** (gnome-keyring-daemon:12388): WARNING **: couldn't bind to control socket: /home/ruth/.cache/keyring-9J9MFZ/control: Permission denied
	

Print screen button is now working speedily and I CAN access my phone doing it that way.

I think this workaround will do.  I only need do it once per session and for me a gnome session can last a few weeks.( I hardly ever turn my pc off.. I probably should )

 

 

[NewtSoup]

Monkey Feathers!.. I've just had a 3TB drive go down :(.. unrelated to the screenshot issue though.

Going to have to let that drive cool and then see if I can get the stuff off it when I have a new storage drive

Just checked  - I bought it in 2013 so I guess it's lasted a while.

Hope I can get my picture archives off it

It's always a seagate drive that fries on me.  Must remember to not buy seagate

 

Edited March 13, 2018 by NewtSoup

[NewtSoup]

Here's interesting :

Google Chrome also takes about a minute to come to life after login and also if you shut it down and restart it.

 

However - having restarted the keyring Chrome starts immediately recovering all 15 tabs I had open in a few seconds

BUT it gives me a message saying "the default keyring was not unlocked on login.  Please enter your password to unlock the keyring"

I've been logged out of all web pages I was logged into but chrome has the passwords cached

[Geonovast]

44 minutes ago, NewtSoup said:

It's always a seagate drive that fries on me.  Must remember to not buy seagate

Odd.  I've had the opposite experience.  Seagate is the only brand I buy on purpose.

13 minutes ago, NewtSoup said:

Google Chrome also takes about a minute to come to life after login and also if you shut it down and restart it.

I'm going have to have investigate that.  FF always takes forever to start.... but it does that on my Windows work computer too.  All that started with the "New and faster" FF Quantum.. which is hilariously slower than its predecessor.  And now that it uses all threads, it likes to lag when KSP is running.

 

My mom gets the default keyring message all the time, I believe because she doesn't require a password to log in (Linux Mint again there).  I never get the message on any of my machines.

[NewtSoup]

Looking at Amazon ALL hard disks seem to have a 8-10% fail rate on new.  I bought two of these seagates at the same time - the first failed inside a year ( I should have sent it back but I didn't) the second has lasted 5 years.  Given that it's been powered up almost continuously for those 5 years I guess I should not complain too loudly.

 

[Green Baron]

Glad the screen shot workaround works. Hopefully Ubuntu or the Gnomies come up with a fix soon(tm).

WD Black have a nice reputation. 8-10% sounds ridiculously high. Since you're on Linux, a software raid 1 (two identical disks mirrored) costs some installation effort and another disk. Have a look at mdadm if you're interested ...

Yeah, changing magnetic media after 5 years (or when the first errors are being reported) is a good idea imo.

 

Edit: if you do it once in a session anyway then why not put the two lines in your login script, which should be /home/$USER/.profile ? But pls. check this, some distributions change the filenames. And don't forget to write a short documentation so that you don't forget to remove it when you update to a new version ;-)

Edited March 13, 2018 by Green Baron

[NewtSoup]

Looking at my logs errors have been being reported for ages.. just not in a way that was flagged to me.  I only discovered the /var/logs after you mentioned it today and had a look at some of syslog

They all carry the same theme

Mar 12 08:36:14 Ruth-Ubuntu kernel: [36214.405916] [UFW BLOCK] IN=enp6s0 OUT= MAC=01:00:5e:00:00:01:62:51:63:4b:c6:71:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Mar 12 08:38:19 Ruth-Ubuntu kernel: [36339.393648] [UFW BLOCK] IN=enp6s0 OUT= MAC=01:00:5e:00:00:01:62:51:63:4b:c6:71:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Mar 12 08:34:21 Ruth-Ubuntu udisksd[2341]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_W1F22D82: Error updating SMART data: sk_disk_smart_read_data: Input/output error (udisks-error-quark, 0)
Mar 12 08:39:01 Ruth-Ubuntu CRON[30496]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Mar 12 08:40:24 Ruth-Ubuntu kernel: [36464.382091] [UFW BLOCK] IN=enp6s0 OUT= MAC=01:00:5e:00:00:01:62:51:63:4b:c6:71:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Mar 12 08:42:29 Ruth-Ubuntu kernel: [36589.368910] [UFW BLOCK] IN=enp6s0 OUT= MAC=01:00:5e:00:00:01:62:51:63:4b:c6:71:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163650] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163658] ata2.00: failed command: SMART
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163667] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 5 pio 512 in
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163667]          res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163671] ata2.00: status: { DRDY }
Mar 12 08:44:24 Ruth-Ubuntu kernel: [36704.163676] ata2: hard resetting link
Mar 12 08:44:26 Ruth-Ubuntu udisksd[2341]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_W1F22D82: Error updating SMART data: sk_disk_smart_read_data: Input/output error (udisks-error-quark, 0)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.095633] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.096098] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.096110] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170531/psparse-550)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.096934] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.096944] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170531/psparse-550)
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.097177] ata2.00: configured for UDMA/133
Mar 12 08:44:26 Ruth-Ubuntu kernel: [36706.097198] ata2: EH complete

[Green Baron]

3 minutes ago, NewtSoup said:

[snip]

I/O error ? I recon its not the cable ? Outch ...

Edit: login as root and unmount the partitions and execute an fsck that fits your filesystem. E.g. e2fsck, ....

Assuming you have the system files on an own partition.

Edited March 13, 2018 by Green Baron

[NewtSoup]

4 minutes ago, Green Baron said:

I/O error ? I recon its not the cable ? Outch ...

Edit: login as root and unmount the partitions and execute an fsck that fits your filesystem. E.g. e2fsck, ....

Assuming you have the system files on an own partition.

Oh yea.. this is my "media" drive.  I have a collection of pictures on it that I'd like to get back otherwise most of the rest of the stuff can go.

For the moment though the drive has been completely removed until such time as I get a replacement disk.  There's 1.6 TB of stuff to recover and I don't want to waste what little life the drive may have left.

The computer has been difficult to reboot for a couple of months and i thought the motherboard was a bit flaky because if i left the whole thing to cool down it would restart fine. (Temps were all ok - I checked )

But today it refused to even POST with the Seagate drive plugged in when I restarted earlier ( shortly before the monkey feathers post ).  I suspect it's a paperweight now.  But as I say I'm not going to try and get it up and running until I have another drive I can decant its contents onto.

Time for work now so I probably wont' respond for about 6 hours.

[steve_v]

7 hours ago, NewtSoup said:

Looking at my logs errors have been being reported for ages

You do have smartmontools running self tests on your drives regularly, right?
What did the last test say about that drive?

On drive reliability in general, I've been running an 8 disk array in my home fileserver for forever, upgrading the members every now and then from 80GB to the current 4TB.
I see no real pattern WRT manufacturer, but I have encountered particularly flaky models. The early 2TB Barracuda LPs spring to mind, I had a 50% failure rate at 2 years.

Backblaze doesn't like the ST3000DM001 much either:

I've had plenty of WD drives fail too, but it does feel like Seagate has released more dodgy models.

I'm currently running the ST4000VX007 "surveillance" drives, and so-far no problems. Got a pretty sharp deal on them too.

Edited March 14, 2018 by steve_v

[NewtSoup]

29 minutes ago, steve_v said:

You do have smartmontools running self tests on your drives regularly, right?
What did the last test say about that drive?

Nope, tell me what they are and I'll install them.  Can't use something I don't know about

[steve_v]

4 minutes ago, NewtSoup said:

tell me what they are and I'll install them.

https://help.ubuntu.com/community/Smartmontools and possibly https://help.ubuntu.com/community/EmailAlerts.

[NewtSoup]

Done, thanks for that - also slapped on GSmartControl.

Good to know my system drive and 256gb SSD are in perfect health.  I'm not plugging the ST3000 back in until such time as I have a replacement drive :). 

So, my current upgrade goals are 500gb SSD to use as an ubuntu system drive and a new 3TB storage drive, or two of them to mirror.. but can't afford two at the moment. The SSD and a single drive are going to clean me out

 

[steve_v]

7 minutes ago, NewtSoup said:

but can't afford two at the moment.

I have 6 in a box under my desk, but you're a long way away.
Makes a good footrest, I can't even seem to give them away.

Edited March 14, 2018 by steve_v

[NewtSoup]

It's ok but thanks for thinking of me

For the big drive I don't need high performance.. just cast iron reliability.

My motherboard has a single mSata slot.  I wonder if I should put an mSata stick in it?

[Geonovast]

1 hour ago, steve_v said:

You do have smartmontools running self tests on your drives regularly, right?

Well, I do now!

32 minutes ago, steve_v said:

I have 6 in a box under my desk, but you're a long way away.
Makes a good footrest, I can't even seem to give them away.

If you're seriously looking to get rid of them, shoot me a PM.

 

10 minutes ago, NewtSoup said:

For the big drive I don't need high performance.. just cast iron reliability.

Maybe look at NAS specific drives?  I think they tend to spin slower and are supposed to be focused on reliability over speed.  Or so they say, anyway.

[steve_v]

4 minutes ago, NewtSoup said:

cast iron reliability

I'm not sure it actually exists anymore, outside of eyewateringly expensive enterprise drives. RAID1 is the go.
There were reliable drives once, I still have my first HDD, an 80MB Quantum ProDrive. And it still works perfectly after ~15 years in service and another 9 as  (literally!) a paperweight.

[NewtSoup]

my motherboard supports raid 0 1 5 and 10 it has a total of 6 SATA ports  two x 6gb/s and 4 x 3gb/s and has 2 6gb/s eSata port and a single mSata up by the processor.

just spotted that SSD's now go up to 4tb on amazon

I could have raid 10 using 6 of them for the cool price of  £7156.56

The worlds biggest SSD though is 15TB and costs $10,800 USD  Thats a lot of lolcat pictures!

[steve_v]

10 hours ago, NewtSoup said:

my motherboard supports raid 0 1 5 and 10 it has a total of 6 SATA ports

If you don't need access from Windows, Linux (software) mdraid is better than any BIOS raid I have seen.

Edited March 14, 2018 by steve_v

[NewtSoup]

Oh I'm just window shopping.

I'll be getting a single large capacity spinny drive for media and documents and a fast SSD for system and games.  I have a total of 30gb storage available to me with google so I'll just make sure my really important stuff ( pics of my son, programming projects, death star plans etc ) are backed up in the cloud

14 hours ago, Green Baron said:

Guys, before OP has all the features s/he uses up and running on a different DE the problem will long be solved, i think.

@Green Baron it's "she" or Ruth btw

Edited March 14, 2018 by NewtSoup

[NewtSoup]

Once again - Monkey Feathers!
 

Just did a system update, rebooted and got a blank screen ( not even post ) saying "please install bootable media" - this is what I thought was a flaky motherboard but when I took out my faulty 3gb drive it started up fine.

This time however having GSmartControl installed, I took a look at my main 1gb Linux drive
 

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       15084
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   071   068   025    Pre-fail  Always       -       8949
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2956
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       37140
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       2426
191 G-Sense_Error_Rate      0x0022   099   099   000    Old_age   Always       -       12002
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   038   000    Old_age   Always       -       32 (Min/Max 11/62)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       184
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       722
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       3116

 

and I get in the error log:

 
	Error 17 occurred at disk power-on lifetime: 15646 hours (651 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.
	  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 e0
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec ff 01 01 00 00 e0 00      00:00:00.120  IDENTIFY DEVICE
  a1 ff 01 01 00 00 e0 00      00:00:00.120  IDENTIFY PACKET DEVICE
  00 00 01 01 00 00 40 00      00:00:00.113  NOP [Abort queued commands]
  00 00 01 01 00 00 40 00      00:00:00.104  NOP [Abort queued commands]
  00 00 01 01 00 00 40 00      00:00:00.103  NOP [Abort queued commands]

I'm guessing error 17 is what was causing the motherboard to freak at post?
The rest of it - can someone help me interpret the data?

 

The drive is a Samsung Spinpoint HD103SJ - just in case that's important.

Edited March 18, 2018 by NewtSoup

[Zeiss Ikon]

Error 17 occurred two years of running time ago, and it's just now causing trouble?  "Insert bootable media" probably means your BIOS is trying to start from the wrong drive; your boot order may have gotten messed up when you pulled the 3 TB drive out of the system.