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 <span></span><br><br>On Tuesday, November 19, 2013, Jim Duuuude wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">(ala Mythbusters) "Well *THERE's* your problem!!"<br><br>Try the VIA release rather then the i686.<br><br>Jim<br><br><div>> From: <a href="javascript:_e({}, 'cvml', 'Benjamin@kb9lfz.com');" target="_blank">Benjamin@kb9lfz.com</a><br>
> To: <a href="javascript:_e({}, 'cvml', 'tim.sawyer@mac.com');" target="_blank">tim.sawyer@mac.com</a><br>> Date: Tue, 19 Nov 2013 00:07:43 -0500<br>> CC: <a href="javascript:_e({}, 'cvml', 'app_rpt-users@ohnosec.org');" target="_blank">app_rpt-users@ohnosec.org</a><br>
> Subject: Re: [App_rpt-users] e2fsck..... halted during boot<br>> <br>> Tim, et al:<br>> <br>> Here's what I'm doing, the same way I've done it before, which much<br>> success.<br>> <br>> The machine is a neoware thin client, CA-22, with 1GHz processor, 1GB<br>
> RAM, 256MB flash.<br>> <br>> on my allstar node 28569, same physical setup, using Limey Linux for<br>> i686. the distro VIA version did not work at all.<br>> <br>> I'm using DamnSmallLinux on a thumbdrive on the designated machine to<br>
> cfdisk the Disk-on-module, not compact flash or another USB thumbdrive,<br>> to delete what was on it, and format for FAT16. I tried also EXT2.<br>> <br>> If I had a USB to laptop IDE adapter with pins on it, I'd just connect<br>
> the DOM to it and see what the main machine says with gparted or the<br>> other disk utility program. <br>> <br>> DamnSmallLinux and Puppy Linux do not have dosfsck support. I've been<br>> trying to get TinyCore to work, but that is not being my friend today. I<br>
> have TinyCore that works fine for me on a few other thin client boxes<br>> with 128MB RAM and 65MB flash.<br>> <br>> anyway, I digress, I go right away into console when DSL boots.<br>> I "sudo su" then cd to the folders I have the Limey linux, or other<br>
> embedded Linux .img files are in.<br>> <br>> the command I have used before was "dd if=cfimg-1.1.4_i686 of=/dev/hda"<br>> I've tried using "dd if=cfimg-1.1.4_i686 of=/dev/hda bs=16k" as that<br>
> works for other embedded distro versions, but did not work here. I've<br>> never seen the e2fsck error before, even after reformatting the drive to<br>> be used.<br>> <br>> ~Benjamin, KB9LFZ<br>> <br>
> On Mon, 2013-11-18 at 20:32 -0800, Tim Sawyer wrote:<br>> > Never seen a e2fsck problem. I don’t know what but you’ve got something else wrong. Are you using the right CPU architecture?<br>> > --<br>> > Tim<br>
> > :wq<br>> > <br>> > On Nov 18, 2013, at 7:59 PM, Benjamin L. Naber <<a>benjamin@kb9lfz.com</a>> wrote:<br>> > <br>> > > tune2fs does not work either. Says could not find superblock.<br>
> > > <br>> > > on another linux machine, I typed in info tune2fs and it states it is<br>> > > for Linux file systems.<br>> > > <br>> > > I don't care about that. I'd like to disable the file system checking<br>
> > > altogether so I can at least get the thing to boot. <br>> > > <br>> > > presently, it still comes to a dead halt when the e2fsck warning comes<br>> > > up.<br>> > > <br>> > > Is there something I can modify in the SYSLINUX.cfg?<br>
> > > <br>> > > -or-<br>> > > <br>> > > When it does get stuck on the e2fsck checktime warning, how long does it<br>> > > *usually* take to let whatever program do it's job and then continue<br>
> > > booting?<br>> > > <br>> > > -or-<br>> > > when it does get stuck, beside mashing the power button and smoking a<br>> > > cigarette, is there a key sequence I can use to troubleshoot or force<br>
> > > the machine to continue booting?<br>> > > <br>> > > ~Benjamin, KB9LFZ<br>> > > <br>> > > <br>> > > On Mon, 2013-11-18 at 10:25 -0800, Joel wrote:<br>> > >> Benjamin L. Naber wrote:<br>
> > >>> this is coming up when trying to boot a new install of Limey Linux<br>> > >>> <br>> > >>> last time I checked, e2fsck is for EXT2 and other Linux extensions, not<br>> > >>> FAT.<br>
> > >>> <br>> > >>> Booting comes to a dead halt when the e2fsck checktime has been<br>> > >>> reached.<br>> > >>> <br>> > >>> Any way around this, or disable this checking when booting?<br>
> > >> <br>> > >> <br>> > >> 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...<br>
> > >> <br>> > >> 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!<br>
> </div> </div></div>
</blockquote><br><br>-- <br>Sent From My Iphone 5 On AT&Ts 4G LTE Network<br>