On Fri, Feb 1, 2013 at 4:27 PM, Jake <span dir="ltr"><<a href="mailto:jake@spaz.org" target="_blank">jake@spaz.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i can't even run fdisk to see the physical size of the drive.<br>
root@minotaur:/home/jake# fdisk /dev/sda<br>
bash: /sbin/fdisk: Input/output error<br></blockquote><div><br></div><div>It's sdb that's failing.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
but assuming we can find a nice hard drive to replace the one in there, can we just copy the failing drive?<br></blockquote><div><br></div><div>If we're very lucky, but I would guess not. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think minotaur is a good box for low-CPU but critical tasks like door opening and RFID alerting.</blockquote><div><br></div><div>I think so too, and I'm glad it exists, but it's also become a bit of a dumping ground for new projects that people want to talk to over the network.</div>
<div>I'd much rather start offloading what we can onto raspberry pis, or ethershield-ed arduinos.</div><div><br></div><div>Minotaur being down also breaks in-space DNS, methinks.</div><div><br></div><div>Maybe I should hack up a backup resolver on pony and re-point DHCP? That's not the most reliable host either these days, with the UPS.</div>
<div><br></div><div>--j </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On Fri, 1 Feb 2013, Jonathan Lassoff wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And... Minotaur's disk dies.<br>
I think we're way overloading this box that 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 <<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 from awesome.local<br>
jake@minotaur:~$ touch sdfkj<br>
touch: cannot touch `sdfkj': Read-only file system<br>
jake@minotaur:~$ mount<br>
/dev/mapper/minotaur-root on / type ext4 (rw,errors=remount-ro)<br>
proc on /proc type proc (rw,noexec,nosuid,nodev)<br>
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)<br>
none on /sys/fs/fuse/connections type fusectl (rw)<br>
none on /sys/kernel/debug type debugfs (rw)<br>
none on /sys/kernel/security type securityfs (rw)<br>
udev on /dev type devtmpfs (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 (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 (rw,nosuid,nodev)<br>
/dev/sdb1 on /boot type ext2 (rw)<br>
/dev/mapper/minotaur-home on /home type ext4 (rw)<br>
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)<br>
nfsd on /proc/fs/nfsd type nfsd (rw)<br>
<br>
mount: warning: /etc/mtab is not writable (e.g. read-only<br>
filesystem).<br>
It's possible that information reported by mount(8) is<br>
not<br>
up to date. For actual information about system mount<br>
points<br>
check the /proc/mounts file.<br>
<br>
jake@minotaur:~$<br>
______________________________<u></u>_________________<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>
</blockquote>
</div></div></blockquote></div><br>