Boot Failure - Openindiana w/ Napp-it - Full Root?

F

fastedd27

n00b
Joined
Feb 1, 2011
Messages
14
Came home the other day to a Napp-it Gui that would not load. Login would appear but when i attempted I would get the following

Set default permissions and reading disk and pool parameter, please wait..
in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.
rm: /var/web-gui/_log/group/*~127.0.0.1.txt: No such file or directory Content-type: text/html (sub array2file ) Datei /var/web-gui/_log/group/server2~127.0.0.1.txt konnte nicht geschrieben werden.)
Fragen Sie bei Bedarf Ihren Systembetreuer Content-type: text/html
Software error:

(sub array2file ) Datei /var/web-gui/_log/group/server2~127.0.0.1.txt konnte nicht geschrieben werden.) at /var/web-gui/data/wwwroot/cgi-bin/admin-lib.pl line 423.

For help, please send mail to this site's webmaster, giving this error message and the time and date of the error.
[Thu Jan 30 08:16:40 2014] admin.pl: (sub array2file ) Datei /var/web-gui/_log/group/server2~127.0.0.1.txt konnte nicht geschrieben werden.) at /var/web-gui/data/wwwroot/cgi-bin/admin-lib.pl line 423.

I attempted to reboot from the OI desktop...it shutdown fine but would not come back up.



I went to google and here searching for a fix and found that it is most likely due to a full root. I saw a few brief posts saying to use a live disk to import the root and try to eliminate some logs. This is what i get when I do that.


I was expecting to get to the actual desktop environment and not a recovery console and I'm lost.

If someone can take the time to walk me thru this...i would greatly appreciate it!
I have been stumbling thru zfs for s few years but please treat me like a noob in your instructions as im not far off lol
 
Last edited:
What I would try:

-first retry after a full power off/on

- If the current boot environment is damaged:
select the next older be during setup and set it to default on success

- if one of the disks of the datapool blocks hardware
remove all dislks from your datapool and try to boot

-if your rpool is full
try to delete unneeded boot environments, optionally boot from a live cd/dvd

-if your bootdisk is damaged
check the disk on Windows with a tool from the disk manufacturer
reinstall os, napp-it and import your pool

optionally use a new systemdisk
 
Thanks for the reply!

Tried the power off/on several times.
I think the boot is ok... it was still running and usable until i rebooted...so I think I will try to free up some space. I assume that by boot environments you mean these


Thats great if I can do that versus trying to dig around for log files.
What ones should I start with? oldest first I assume? and now the big question...how do I do that from that selection screen?

I had tried the live disk but I only get to what is shown in the 3 pic of my original post and dont know how to proceed...I know my login/pass but not after that.


Thanks for your time and help
 
bump...
anyone out there have time to walk me through deleting a boot environment? Just need to free up some space so I can boot and backup
really dont want to walk away from the sql database sitting on this root...too many months since a backup :(
 
ok so I have kept working on this and could never get the live disk to boot to the desktop gui. When I attempt this with or without the root mirror attached i get the following and my old root login and password still work.

I would attempt the beadm command but I dont know how to get to a place where I can use it
I will but cussing at this thing for the remainder of the weekend...so if someone can give me further direction I would greatly appreciate it
 
fastedd27 said:
ok so I have kept working on this and could never get the live disk to boot to the desktop gui. When I attempt this with or without the root mirror attached i get the following and my old root login and password still work.

I would attempt the beadm command but I dont know how to get to a place where I can use it
I will but cussing at this thing for the remainder of the weekend...so if someone can give me further direction I would greatly appreciate it
Click to expand...

have you tried it at the prompt in the picture?
 
Thanks to everyone that responded...solutions I found are below.

The reason I kept coming to system maintenance login when using live disk is that I was using a usb dvd rom. Once I connected directly to a sata port i booted all the way into the live desktop.

I was then able to delete a boot environment, but that was only a few megs. It was enough to boot into command prompt (Desktop would not come up still). I imported the rpool and deleted an old sabnzbd install I had floating around. That was enough to get me back into the desktop on next reboot. I the ran disk usage analyzer and tracked down a 5 gig core file in /var/fm/fmd

So all is good for now...if anyone has any suggestions to avoid this in the future..please share.
 
You must log in or register to reply here.
Back
Top