<br><br><div class="gmail_quote">On Fri, Feb 1, 2013 at 4:52 PM, Jake <span dir="ltr"><<a href="mailto:jake@spaz.org" target="_blank">jake@spaz.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i can't even tell what drive is what on that thing. I thought there was a laptop drive mounted in an external enclosure, is that the only drive?<br>
<br>
why is it sdb? shouldn't it be sda if it's the boot drive?<br>
<br>
are SSD's more reliable than regular hard drives? What about a nice 3.5" desktop drive?</blockquote><div><br>What is meant to run on Minotaur.<br><br>I am happy to move the API to another device (it can work on pony). I also have a RaPi we could use, possibly also to handle the door-handling in general?<br>
<br>I am not really around Monday, but I could be around Tuesday evening.<br><br>d.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<br>
<br>
On Fri, 1 Feb 2013, Ben Kochie wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
I have a new server setup we can use. I may also have an extra ssd to<br>
replace SDB.<br>
<br>
Jonathan Lassoff <<a href="mailto:jof@thejof.com" target="_blank">jof@thejof.com</a>> wrote:<br>
On Fri, Feb 1, 2013 at 4:27 PM, Jake <<a href="mailto:jake@spaz.org" target="_blank">jake@spaz.org</a>> wrote:<br>
i can't even run fdisk to see the physical size of<br>
the drive.<br>
root@minotaur:/home/jake# fdisk /dev/sda<br>
bash: /sbin/fdisk: Input/output error<br>
<br>
<br>
It's sdb that's failing.<br>
<br>
but assuming we can find a nice hard drive to replace the<br>
one in there, can we just copy the failing drive?<br>
<br>
<br>
If we're very lucky, but I would guess not. <br>
<br>
I think minotaur is a good box for low-CPU but critical<br>
tasks like door opening and RFID alerting.<br>
<br>
<br>
I think so too, and I'm glad it exists, but it's also become a bit of<br>
a dumping ground for new projects that people want to talk to over the<br>
network.<br>
I'd much rather start offloading what we can onto raspberry pis, or<br>
ethershield-ed arduinos.<br>
<br>
Minotaur being down also breaks in-space DNS, methinks.<br>
<br>
Maybe I should hack up a backup resolver on pony and re-point DHCP?<br>
That's not the most reliable host either these days, with the UPS.<br>
<br>
--j <br>
<br>
<br>
On Fri, 1 Feb 2013, Jonathan Lassoff wrote:<br>
<br>
And... Minotaur's disk dies.<br>
I think we're way overloading this box that<br>
was intended as an out-of-band<br>
access host. :p<br>
<br>
--j<br>
<br>
On Fri, Feb 1, 2013 at 4:18 PM, Jake<br>
<<a href="mailto:jake@spaz.org" target="_blank">jake@spaz.org</a>> wrote:<br>
*** System restart required ***<br>
Last login: Thu Jan 31 22:56:43 2013<br>
from awesome.local<br>
jake@minotaur:~$ touch sdfkj<br>
touch: cannot touch `sdfkj': Read-only<br>
file system<br>
jake@minotaur:~$ mount<br>
/dev/mapper/minotaur-root on / type ext4<br>
(rw,errors=remount-ro)<br>
proc on /proc type proc<br>
(rw,noexec,nosuid,nodev)<br>
sysfs on /sys type sysfs<br>
(rw,noexec,nosuid,nodev)<br>
none on /sys/fs/fuse/connections type<br>
fusectl (rw)<br>
none on /sys/kernel/debug type debugfs<br>
(rw)<br>
none on /sys/kernel/security type<br>
securityfs (rw)<br>
udev on /dev type devtmpfs<br>
(rw,mode=0755)<br>
devpts on /dev/pts type devpts<br>
(rw,noexec,nosuid,gid=5,mode=<u></u>0620)<br>
tmpfs on /run type tmpfs<br>
(rw,noexec,nosuid,size=10%,<u></u>mode=0755)<br>
none on /run/lock type tmpfs<br>
(rw,noexec,nosuid,nodev,size=<u></u>5242880)<br>
none on /run/shm type tmpfs<br>
(rw,nosuid,nodev)<br>
/dev/sdb1 on /boot type ext2 (rw)<br>
/dev/mapper/minotaur-home on /home type<br>
ext4 (rw)<br>
rpc_pipefs on /run/rpc_pipefs type<br>
rpc_pipefs (rw)<br>
nfsd on /proc/fs/nfsd type nfsd (rw)<br>
<br>
mount: warning: /etc/mtab is not<br>
writable (e.g. read-only<br>
filesystem).<br>
It's possible that information<br>
reported by mount(8) is<br>
not<br>
up to date. For actual<br>
information about system mount<br>
points<br>
check the /proc/mounts file.<br>
<br>
jake@minotaur:~$<br>
<br>
______________________________<u></u>_________________<br>
Rack mailing list<br>
<a href="mailto:Rack@lists.noisebridge.net" target="_blank">Rack@lists.noisebridge.net</a><br>
<br>
<a href="https://www.noisebridge.net/mailman/listinfo/rack" target="_blank">https://www.noisebridge.net/<u></u>mailman/listinfo/rack</a><br>
<br>
<br>
<br>
<br></div></div>
______________________________<u></u>______________________________<u></u>________________<div class="im"><br>
Rack mailing list<br>
<a href="mailto:Rack@lists.noisebridge.net" target="_blank">Rack@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/rack" target="_blank">https://www.noisebridge.net/<u></u>mailman/listinfo/rack</a><br>
<br>
<br>
--<br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br>
</div></blockquote>
<br>_______________________________________________<br>
Rack mailing list<br>
<a href="mailto:Rack@lists.noisebridge.net">Rack@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/rack" target="_blank">https://www.noisebridge.net/mailman/listinfo/rack</a><br>
<br></blockquote></div><br>