[App_rpt-users] e2fsck..... halted during boot

[Jared Paxton]

Hello everyone. This is Jared and some of you who talk to me on air know me
as KD2ERF. BUT MY NEW CALL SIGN is KB2JIP

On Tuesday, November 19, 2013, Jim Duuuude wrote:

> (ala Mythbusters)  "Well *THERE's* your problem!!"
>
> Try the VIA release rather then the i686.
>
> Jim
>
> > From: Benjamin at kb9lfz.com <javascript:_e({}, 'cvml',
> 'Benjamin at kb9lfz.com');>
> > To: tim.sawyer at mac.com <javascript:_e({}, 'cvml',
> 'tim.sawyer at mac.com');>
> > Date: Tue, 19 Nov 2013 00:07:43 -0500
> > CC: app_rpt-users at ohnosec.org <javascript:_e({}, 'cvml',
> 'app_rpt-users at ohnosec.org');>
> > Subject: Re: [App_rpt-users] e2fsck..... halted during boot
> >
> > Tim, et al:
> >
> > Here's what I'm doing, the same way I've done it before, which much
> > success.
> >
> > The machine is a neoware thin client, CA-22, with 1GHz processor, 1GB
> > RAM, 256MB flash.
> >
> > on my allstar node 28569, same physical setup, using Limey Linux for
> > i686. the distro VIA version did not work at all.
> >
> > I'm using DamnSmallLinux on a thumbdrive on the designated machine to
> > cfdisk the Disk-on-module, not compact flash or another USB thumbdrive,
> > to delete what was on it, and format for FAT16. I tried also EXT2.
> >
> > If I had a USB to laptop IDE adapter with pins on it, I'd just connect
> > the DOM to it and see what the main machine says with gparted or the
> > other disk utility program.
> >
> > DamnSmallLinux and Puppy Linux do not have dosfsck support. I've been
> > trying to get TinyCore to work, but that is not being my friend today. I
> > have TinyCore that works fine for me on a few other thin client boxes
> > with 128MB RAM and 65MB flash.
> >
> > anyway, I digress, I go right away into console when DSL boots.
> > I "sudo su" then cd to the folders I have the Limey linux, or other
> > embedded Linux .img files are in.
> >
> > the command I have used before was "dd if=cfimg-1.1.4_i686 of=/dev/hda"
> > I've tried using "dd if=cfimg-1.1.4_i686 of=/dev/hda bs=16k" as that
> > works for other embedded distro versions, but did not work here. I've
> > never seen the e2fsck error before, even after reformatting the drive to
> > be used.
> >
> > ~Benjamin, KB9LFZ
> >
> > On Mon, 2013-11-18 at 20:32 -0800, Tim Sawyer wrote:
> > > Never seen a e2fsck problem. I don’t know what but you’ve got
> something else wrong. Are you using the right CPU architecture?
> > > --
> > > Tim
> > > :wq
> > >
> > > On Nov 18, 2013, at 7:59 PM, Benjamin L. Naber <benjamin at kb9lfz.com>
> wrote:
> > >
> > > > tune2fs does not work either. Says could not find superblock.
> > > >
> > > > on another linux machine, I typed in info tune2fs and it states it is
> > > > for Linux file systems.
> > > >
> > > > I don't care about that. I'd like to disable the file system checking
> > > > altogether so I can at least get the thing to boot.
> > > >
> > > > presently, it still comes to a dead halt when the e2fsck warning
> comes
> > > > up.
> > > >
> > > > Is there something I can modify in the SYSLINUX.cfg?
> > > >
> > > > -or-
> > > >
> > > > When it does get stuck on the e2fsck checktime warning, how long
> does it
> > > > *usually* take to let whatever program do it's job and then continue
> > > > booting?
> > > >
> > > > -or-
> > > > when it does get stuck, beside mashing the power button and smoking a
> > > > cigarette, is there a key sequence I can use to troubleshoot or force
> > > > the machine to continue booting?
> > > >
> > > > ~Benjamin, KB9LFZ
> > > >
> > > >
> > > > On Mon, 2013-11-18 at 10:25 -0800, Joel wrote:
> > > >> Benjamin L. Naber wrote:
> > > >>> this is coming up when trying to boot a new install of Limey Linux
> > > >>>
> > > >>> last time I checked, e2fsck is for EXT2 and other Linux
> extensions, not
> > > >>> FAT.
> > > >>>
> > > >>> Booting comes to a dead halt when the e2fsck checktime has been
> > > >>> reached.
> > > >>>
> > > >>> Any way around this, or disable this checking when booting?
> > > >>
> > > >>
> > > >> I've never used any of these AllStar distro's - but I have admin's
> Linux servers for over 15 years and am just starting to play with AllStar.
> With that in mind, I can offer the following more generic Linux info...
> > > >>
> > > >> CD-ROM images are always in the iso9660 filesystem format - which
> is completly different than FAT/EXT2/3/4/etc. Doesn't matter what OS was
> used to create the img - or burn the CD. That format is only on the optical
> disc (or local loopback of the image file if you install that way). Typical
> thumb-drive images I've seen have a small FAT filesystem that boots and
> mounts the install iso image as lookback. The installer, as part of system
> setup/install formats the local storage device (typically /dev/hda or
> /dev/sda) in a Linux file format. These days either EXT2 (non-journaled) or
> EXT3/4 for journaling. This has no relation to the install media!
> >
>


-- 
Sent From My Iphone 5 On AT&Ts 4G LTE Network
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20131119/218d087e/attachment.html>