Lonnie,

I was able to get up and running by starting over and choosing to make separate 
Unionfs and /mnt/kd partitions.

In case you're wondering, I did try your suggestions.  fdisk -l outputted the 
following:

Device         Boot    Start        End              Blocks           ID    
System
/dev/sda1     *        63            524159        262048+      6      FAT16
/dev/sda2               524288    2001887     738800        83    Linux

 I was not able to run e2fsck with the -y flag.  I got several errors while 
running it manually:

error reading block 196610 (invalid argument) while getting next inode from 
scan.
error reading block 196611 (invalid argument) while getting next inode from 
scan.
...

I ignored several of these and then aborted.  One possible clue that I saw 
during startup:

error mounting astlinux-1.1.6.run rootfs

It seems to me that although the new partition was not made, running 
initial-setup format combined must have done something.  I don't need two 
separate partitions but this works.  I can't think of any major drawbacks to 
this type of setup.

Thanks again,

Josh

> From: li...@lonnie.abelbeck.com
> Date: Wed, 2 Jul 2014 19:41:06 -0500
> To: astlinux-users@lists.sourceforge.net
> Subject: Re: [Astlinux-users] Can't Access tty after initial-setup format
> 
> Hi Josh,
> 
> I've personally never seen this, but such as that my advice is to boot into 
> the runnix shell...
> 
> boot: shell
> 
> Then try...
> ==============
> 
> runnix# fdisk -l
> 
> (just to see what is going on)
> 
> runnix#  e2fsck -y /dev/sda2
> 
> (ignore the missing mtab warning)
> 
> If you still get the same error, get more agressive with e2fsck to try to 
> resolve your issue.
> 
> (when done, reboot with)
> runnix# exit
> 
> ==============
> 
> Lonnie
> 
> 
> On Jul 2, 2014, at 7:10 PM, Josh wrote:
> 
> > Hello,
> > 
> > At the recommendation of John and Lonnie, I decided to install Astlinux 
> > 1.0-6575 to the internal flash storage on my Wyse R90L.  I followed the 
> > instructions on the wiki.  After using dd to zero the drive and copy the 
> > files, I can boot up and access the web interface.  Everything seems fine 
> > until I format the hard drive for persistent storage.  I had the same 
> > results doing this through the web interface and the CLI.  "initial-setup 
> > format combined /dev/sda" was successful, but when I rebooted, I see:
> > 
> > Fsck detected errors on /dev/sda2 (0)
> > /bin/sh: can't access tty; job control turned off
> > 
> > A picture of my screen is available here:
> > 
> > http://i57.tinypic.com/2hrg0h1.jpg
> > 
> > Does anyone have any ideas about what went wrong and what I can do to 
> > resolve the issue?
> > 
> > Thanks,
> > 
> > Josh
> 
> 
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> pay...@krisk.org.
                                          
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to