| 04:33.07 | *** join/#utah tiwula (~lane@174-23-25-131.slkc.qwest.net) |
| 10:42.39 | *** join/#utah emcnabb (~emcnabb@hs-nc-1fff767f54-29977-1.tingfiber.com) |
| 14:12.18 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 15:26.33 | *** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 15:38.31 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 17:22.32 | shalkie | Good Friday Morning! |
| 17:36.26 | romanovic | good morning! |
| 17:42.43 | shalkie | Looks like a lovely weekend for romping in the hills. :) |
| 18:06.45 | *** join/#utah youtah (~youtah@50-198-176-9-static.hfc.comcastbusiness.net) |
| 18:06.46 | *** mode/#utah [+v youtah] by ChanServ |
| 18:11.59 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 18:35.27 | shalkie | Where are you going to go play this weekend youtah ? |
| 19:08.46 | *** join/#utah youtah (~youtah@50-198-176-9-static.hfc.comcastbusiness.net) |
| 19:08.46 | *** mode/#utah [+v youtah] by ChanServ |
| 20:13.36 | *** join/#utah maquis (~maquis@172.58.77.28) |
| 20:13.58 | maquis | wanders in after a very very very long time away... |
| 20:14.47 | spangborn | bienvenido a homestar runner dot com |
| 20:16.18 | maquis | so... out of curiosity... what would you do if a machine that has been working perfectly fine for months, and was working fine last night, suddenly today is giving an Input/Output error for every command except pwd and cding to a directory that is known to exist? |
| 20:16.40 | maquis | ls gives an I/O error, dmesg gives an I/O error, sudo gives I/O error.... |
| 20:16.50 | maquis | /bin/sh gives I/O error.... |
| 20:17.28 | maquis | From what I can tell, no updates have run in the time since it was working last night. |
| 20:17.46 | maquis | The machine does still respond to pings, but won't accept ssh/scp requests. |
| 20:18.18 | maquis | interestingly, cd works fine if the destination directory is known to be good. It gives an I/O error if I attempt to cd to a known non-existant directory. |
| 20:18.39 | maquis | This is... of course... purely hypothetical... *cough* |
| 20:30.10 | maquis | looks like the commands that work correctly are shell built-ins. unfortunately, while kill is a zsh built-in command, ps is not... and my conky doesn't list pids. |
| 20:31.33 | spangborn | disk full? |
| 20:34.16 | maquis | spangborn: I don't think it should be, but I haven't found a good way to check. If I can't think of any good options over the next bit (won't be able to really focus on this for the next couple hours), I will probably reboot into a live-usb later this evening. Just trying to make sure i don't lose any useful info by rebooting... |
| 20:34.18 | klys | well I would offline the thing immediately and plug it in secondary to do a backup |
| 20:34.31 | klys | hope your fsck succeeds |
| 20:34.43 | maquis | klys: yeah. :) |
| 20:35.03 | spangborn | fsck everything |
| 20:54.14 | jlp_znc | maquis: long time no see. sounds like a disk failure to me. almost like the disk came unplugged. |
| 20:55.50 | jlp_znc | cd might still work if the directory structure is cached. if ls doesn't work, you might try "echo *" as a replacement. you can cat files entirely in shell with "while read line; do echo $line; done < file" and see what you get. to check disk full, you can try writing something to disk with e.g. "echo hi > newfile" |
| 22:41.57 | maquis | jlp_znc: interesting. I think I may just have to cut my losses and reboot into a live-usb. Just hoping my last few blender files from the past couple weeks will be recoverable. Everything else on this machine could be lost without issue, but I'd be sad to lose my blender work. |
| 23:09.41 | *** join/#utah tiwula (~lane@174-23-25-131.slkc.qwest.net) |