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.

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 @Green Baron it's "she" or Ruth btw

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!

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?

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

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

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.

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

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.

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

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

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 )

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

It means that after I restart the daemon I can no longer access the photo library on my phone. There was another reason why that I can't remember that I read on a webpage and it made sense when I read it but I can't for the life of me find that web page again. No method was given to restart the Daemon on that page it just said "restart the daemon" (which I had no idea how to do ) however I found that sending a job to the printer would say "please enter your password for the main keyring" and then it would be back up and running and I'd be able to take screenshots with no delay. If it sounds confusing, it is. I will try restarting the keyring daemon as you say and then let you know if I can access my 4s

The daemon never restarts properly. I discovered this only recently when trying to get stuff off my 4S. Only when I'd logged out or rebooted could I access the photo library. Then I found out it was only after killing and restarting the keyring daemon that this happened. Seems it happens on Gnome 3 too - https://unix.stackexchange.com/questions/335194/custom-keyboard-shortcut-delayed-on-gnome-3-22 However the bottom comment indicates a fix by removing a file related to cups - I'm not going to remove the file as such. Just see what it does, as the post could be a troll post to make you disable your printer.

I'm fairly new to linux over all.. I've used it many times over the years but never as a full time OS until about a year ago now I guess. I popped Ubuntu onto a spare disk and it just worked! ( even the screenshots back then ) So I got around to installing the correct graphics drivers and some games and apart from a brief love affair with elite dangerous I've been here ever since. The reason I've not used KDE, which I prefer, was when I tried installing it the installation went base over apex and totalled my install. I had no idea how to fix it from the command line and so I just went back and stuck with Unity Desktop. I don't particularly like it either. @Green Baron - I do infact have a shell script that kills the keyring daemon but as I say in my OP that brings on other problems such as access to USB attached phones etc. I have to log out and log back in to get the keyring up and running properly again which is not far off having to reboot just to access the latest pictures I took from my phone. ( I have an old 4S that I use while working to capture the interesting sights around my city - I'm a cycle courier so my main phone is attached to my handlebars in a drybag when working)

@Geonovast I just did the following: reinstalled gnome-screenshot re-enabled systems shortcut for screenshot to "printscrn" pressed printscrn - 30 second delay assigned customer shortcut "Scroll Lock" to Shutter pressed scroll lock - 30 second delay assigned custom shortcut "pause /break" to gedit pressed gedit - 30 second delay typed gnome-screenshot at the terminal - instant response typed shutter at the terminal - instant response typed gedit at the terminal - guess what? - instant response It's defintely something to do with the way that Unity is handling the shortcuts - but only screenshot and custom one. The system made shortcuts ( switch desktops, maximise minimise windows, do volume, summon calculator etc) they all work right away BAR screenshots.

It happens every time, LordFerret

Yeah I’ve tried everything to get Elite Dangerous and Fallout 4 running in Wine. I’ll keep on trying but at the moment they just don’t. Skyrim does so there’s that. But the only way to play the above two is dual boot. In a month though we get Ubuntu 18.04 at that time I will celebrate by buying a 500gb SSD and making a clean install of Ubuntu on it hopefully the screenshot issue will vanish and I can log my installs to work out what modules do it if any. with 18.04 Ubuntu is moving from unity desktop to gnome 3

What Car Magazine reckons £450 on your electricity bill every 10,000 miles so that's about 4.5 pence per mile depending on your supplier. Compare this to petrol or diesel which come in around 12 pence per mile. This is for charging at home.

Yeah I find win 10 a presumptuous upstart. It's nigh on impossible to stop it updating and restarting while you're working on stuff. Very annoyed that I had Win 7 professional but when I took the "free" upgrade I was downgraded to Win 10 Home and told I could upgrade to Pro for just $99. You can stop pro updating automatically. But I'm not spending that money just for that functionality. Anyhoo. I'm definitely liking Ubuntu these days. I installed it and it just worked and I get netflix via chrome ( though a netflix linux application would be better ) My only regret is that I can no longer play Elite Dangerous and Fallout 4. I can still reboot into windows but I don't like doing that just to play a game. I didn't encrypt my windows drive thankfully. It's just a gaming system so no need. I do actually have 3 physical drives in my system 1 TB Hard Drive with Ubuntu installed 256GB SSD with Windows 10 installed 3TB Hard Drive for "media". Ubuntu may need nfs-3g installed to allow ntfs drives to be mounted sudo apt-get install ntfs-3g

Ahh the dreaded dual boot. I find that the most reliable way to dual boot is to have two separate physical drives. Install one drive only in your system, install <insert OS here> and remove this drive. Install the other drive in your system and install <insert OS here > Add the first drive back into your system when restarting simply choose which drive to start up on - most modern motherboards will have a quick boot menu that you can use instead of messing around grub to dual boot. If you don't have a second physical drive and need to use partitioning then get a second physical drive! They're not expensive If you're on a laptop and don't have room for a second physical drive well, when I've done that I've taped the drive cover in place on the underside for quick removal and swap the physical drives over when I want to boot to alternate OS's I may have an irrational fear of using grub to dual boot ( I definitely do ) but my system works reliably and each OS is (as far as it's concerned) installed on the default drive.

Hello fellow aliens, If any of you are from Ubuntuland do you know how to solve the following problem: When I press the PrintScreen button there is a 30 second delay between the button being pressed and the shot being taken. In my settings the delay is turned off so it's not that. Research shows I'm not the only one with the issue and it's been going on since Ubuntu 12.04 It used to be fine on my machine until I installed something ( I'm not sure what or when ) I have: uninstalled gnome-screenshot disabled all screenshot shortcuts in settings installed shutter created custom shortcuts around the printscreen key that fire off shutter. But the problem is still present. I have found that if I do sudo killall gnome-keyring-daemon and then do something to fire up the keyring again eg start a print job then the delay is gone. The price of this though is that you can no longer do thinks like grab pictures off your iphone because the keyring is not restarted quite the same way as when you log in. To get that functionality back I have to log out, log back in and then of course the print screen delays are back. Does anyone know the cause of this and how to fix it?

Hey @Noryb64, welcome to the forums and have fun

Yes.. the linux steam client runs 32 bit KSP by default I created a desktop shortcut from steam - this has the command "steam steam://rungameid/220200" in it I then browsed to my Kerbal Space Program folder and renamed ksp.x86 to: ksp.x86.old Then I double clicked the steam desktop shortcut and Steam gave me an error message related to the ksp.x86 executable Also I had no idea that the in KSP the Unity 64bit support was a bit sketchy