From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 8 14:26:24 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C25B31065672 for ; Tue, 8 Apr 2008 14:26:24 +0000 (UTC) (envelope-from robert.lyall@thecrossbordergroup.com) Received: from relay01.mail.uk1.eechost.net (relay01.mail.uk1.eechost.net [217.69.40.69]) by mx1.freebsd.org (Postfix) with ESMTP id 577DC8FC0A for ; Tue, 8 Apr 2008 14:26:24 +0000 (UTC) (envelope-from robert.lyall@thecrossbordergroup.com) Received: from [217.36.48.225] (helo=Robert) by relay01.mail.uk1.eechost.net with esmtpa (Exim 4.68) (envelope-from ) id 1JjEQ2-0003RL-SU for freebsd-hardware@freebsd.org; Tue, 08 Apr 2008 15:03:27 +0100 Message-ID: <004e01c89981$63573670$2401a8c0@london.thecrossbordergroup.com> From: "Robert Lyall" To: Date: Tue, 8 Apr 2008 15:03:57 +0100 Organization: Cross Border Limited MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Auth-Info: robert.lyall@thecrossbordergroup.com (login) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Iomega NAS 'unlocking' question X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Lyall List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2008 14:26:24 -0000 Hi Just to get a couple of things out of the way: 1. I'm new to FreeBSD. Please be gentle with me. 2. I'm not sure this is the right list - I'll go elsewhere if you = suggest a more appropriate list. Anyway, to business: I've got an old Iomega NAS 410u device. It's a = rack-mount i386 1u file server with 4 disks Raid-0. It runs freeBSD but = famously (on Iomega forums anyway) is pretty much locked down. All = access is by web interface. If there's a problem Iomega (for a price) = sends you out a new disk 1 with a fresh OS.=20 I've sawn a hole(!) in the case to access usb ports, key/mouse = connections and VGA. With a keyboard and monitor connected the device = goes through startup and fails with a lot of 'read-only file system's = and 'enter full pathname of shell'. I can't enter anything as it does = not allow any keyboard input after the bios is finished loading. I'd = like to 'unlock' this device and make it useful again. Fair enough I = hear you say; get the FreeBSD install cds and off you go. Problem is I = also want the data that remains on the disks, so I don't want to = 'disturb' the filesystem. When the device started to fail, it at least = managed to startup but with messages about services (afp, Samba, and = Apache) failing except nfs and ftp. Anyway it doesn't even do that now.=20 What I want to know for starters is has anyone had experience of this = kind of thing before? Or where do I find (I've put the disk1 on a = FreeNAS server so it's accessible) the config files Iomega would have = altered to forbid keyboard and therefore shell access to the machine? Thanks in advance for your help Rob Lyall =20 =20