[Rack] something wrong with minotaur - read-only file system

Ben Kochie ben at nerp.net
Sat Feb 2 00:45:41 UTC 2013


I have a new server setup we can use.  I may also have an extra ssd to replace SDB.

Jonathan Lassoff <jof at thejof.com> wrote:

>On Fri, Feb 1, 2013 at 4:27 PM, Jake <jake at spaz.org> wrote:
>
>> i can't even run fdisk to see the physical size of the drive.
>> root at minotaur:/home/jake# fdisk /dev/sda
>> bash: /sbin/fdisk: Input/output error
>>
>
>It's sdb that's failing.
>
>
>> but assuming we can find a nice hard drive to replace the one in
>there,
>> can we just copy the failing drive?
>>
>
>If we're very lucky, but I would guess not.
>
>I think minotaur is a good box for low-CPU but critical tasks like door
>> opening and RFID alerting.
>
>
>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.
>I'd much rather start offloading what we can onto raspberry pis, or
>ethershield-ed arduinos.
>
>Minotaur being down also breaks in-space DNS, methinks.
>
>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.
>
>--j
>
>>
>>
>> On Fri, 1 Feb 2013, Jonathan Lassoff wrote:
>>
>>  And... Minotaur's disk dies.
>>> I think we're way overloading this box that was intended as an
>out-of-band
>>> access host. :p
>>>
>>> --j
>>>
>>> On Fri, Feb 1, 2013 at 4:18 PM, Jake <jake at spaz.org> wrote:
>>>       *** System restart required ***
>>>       Last login: Thu Jan 31 22:56:43 2013 from awesome.local
>>>       jake at minotaur:~$ touch sdfkj
>>>       touch: cannot touch `sdfkj': Read-only file system
>>>       jake at minotaur:~$ mount
>>>       /dev/mapper/minotaur-root on / type ext4
>(rw,errors=remount-ro)
>>>       proc on /proc type proc (rw,noexec,nosuid,nodev)
>>>       sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
>>>       none on /sys/fs/fuse/connections type fusectl (rw)
>>>       none on /sys/kernel/debug type debugfs (rw)
>>>       none on /sys/kernel/security type securityfs (rw)
>>>       udev on /dev type devtmpfs (rw,mode=0755)
>>>       devpts on /dev/pts type devpts
>>>       (rw,noexec,nosuid,gid=5,mode=**0620)
>>>       tmpfs on /run type tmpfs
>(rw,noexec,nosuid,size=10%,**mode=0755)
>>>       none on /run/lock type tmpfs
>>>       (rw,noexec,nosuid,nodev,size=**5242880)
>>>       none on /run/shm type tmpfs (rw,nosuid,nodev)
>>>       /dev/sdb1 on /boot type ext2 (rw)
>>>       /dev/mapper/minotaur-home on /home type ext4 (rw)
>>>       rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
>>>       nfsd on /proc/fs/nfsd type nfsd (rw)
>>>
>>>       mount: warning: /etc/mtab is not writable (e.g. read-only
>>>       filesystem).
>>>              It's possible that information reported by mount(8) is
>>>       not
>>>              up to date. For actual information about system mount
>>>       points
>>>              check the /proc/mounts file.
>>>
>>>       jake at minotaur:~$
>>>       ______________________________**_________________
>>>       Rack mailing list
>>>       Rack at lists.noisebridge.net
>>>      
>https://www.noisebridge.net/**mailman/listinfo/rack<https://www.noisebridge.net/mailman/listinfo/rack>
>>>
>>>
>>>
>>>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Rack mailing list
>Rack at lists.noisebridge.net
>https://www.noisebridge.net/mailman/listinfo/rack

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.noisebridge.net/pipermail/rack/attachments/20130201/29f8e31b/attachment-0001.html>


More information about the Rack mailing list