SS4200e boots fine from LiveUSB, not after install to disk

[Antwon]

I've got an Intel SS4200e with an IDE DOM that I've temporarily connected a video card to.

I've burned the latest (9.3.0.2.1310) LiveUSB image to a USB drive using ImageWriter and then booted up the SS4200e, and that works fine, I get to the console and everything is good. When I select option 9 to install to disk (and then select the IDE DOM with option 1), everything appears to run as it should until I do a reboot. It runs through its bootup process and when it should reach the console menu, it displays: *Console Menu Disabled*. I try connecting to it on 192.168.1.250 and get nothing.

Now here is another curious aspect: hitting the print screen key to bring up the login, allows me to log in as root, but only with a blank password. It won't take the nas4free password.

So I've tried a couple of different USB drives and tried the previous version, all to no avail. How do I go about troubleshooting this?

Keep in mind that I'm a Windows admin and this is part of me branching out, so I while I may not know a whole lot about Linux, I am at least a technical individual.

[daoyama]

thank you for reporting.

Did you remove LiveUSB before rebooting?
Did you access GUI with LiveUSB?
If you can reach GUI, run from "Advanced|Execute command".
If not possible, please upload screen capture image of below result or write text here.

Please run this command before rebooting from GUI or console menu #6.

gpart show
glabel status
df -h
diskinfo -v ada0

Note: please replace ada0 with your install destination disk.

[armandh]

I will assume the embedded OS
once you believe the OS is transferred, yes you remove the live OS
be sure the IDE flash is in the primary IDE socket
I have had boards that do NOT boot from the secondary IDE socket

at the beginning the boot process is all real mode
there is a certain reliance on hardware compatibility
I have had good luck with these 512 Mb flash drives
http://www.logicsupply.com/components/s ... h-modules/

[Antwon]

Thanks for the replies! Unfortunately I didn't get a chance to continue troubleshooting this morning before work, but I can still answer a couple of those questions:

@daoyama
Did you remove LiveUSB before rebooting?
--Yes, I shutdown the NAS, removed the LiveUSB, and then powered the NAS back on.
Did you access GUI with LiveUSB?
--I did not think to try this, I'll give it a go tonight.

I will also get you the results of those commands tonight.

@armandh
I will assume the embedded OS
--Yes, embedded OS. Sorry for not clarifying.
once you believe the OS is transferred, yes you remove the live OS
--Yes, see above.
be sure the IDE flash is in the primary IDE socket
--Yes, there is only one IDE socket, so I can assume that it is the primary. Though I can verify in the BIOS tonight.
at the beginning the boot process is all real mode
--I'm not sure I understand what you are asking here. It does give me the options of the different modes during startup, I've been using option 1: Normal mode.

I'll get back with more info tonight when I get home. Thanks guys!

[armandh]

the beginning of the boot process is real mode [possibly called normal?]
the CPU finding the boot files and acting accordingly.
later in the boot process, things switch to protected mode
real modes rely upon hardware compatibility as there is not yet any OS to fix such issues.
protected mode has the OS to sort things out.

for example
USB sticks that contain a self loading driver will not work for the boot process as there is not yet an OS to load the driver.
these need to be reformatted into an ordinary FAT file to work as a boot medium.

[Antwon]

@armandh

Thanks for the clarification. It is possible that the DOM just isn't compatible. This is the one I bought: http://www.ebay.com/itm/Industrial-Disk ... 2a3b32e3a7

@daoyama

Looks like the web interface works just fine when booting from USB. I was able to run the commands after booting from the LiveUSB, here are the results:

Code: Select all

$ gpart show
=>      63  62377921  ada0  MBR  (29G)
        63   1654632     1  freebsd  [active]  (807M)
   1654695   8401995     2  freebsd  (4.0G)
  10056690  52307640     3  freebsd  (25G)
  62364330     13654        - free -  (6.7M)

=>      63  15658945  da0  MBR  (7.5G)
        63    853965    1  freebsd  [active]  (417M)
    854028   1052667    2  freebsd  (514M)
   1906695     28665    3  freebsd  (14M)
   1935360  13723648       - free -  (6.6G)

=>      0  1654632  ada0s1  BSD  (807M)
        0     1985          - free -  (992k)
     1985  1638400       1  freebsd-ufs  (800M)
  1640385    14247          - free -  (7M)

=>      0  8401995  ada0s2  BSD  (4.0G)
        0       89          - free -  (44k)
       89  8388608       2  freebsd-swap  (4.0G)
  8388697    13298          - free -  (6.5M)

=>       0  52307640  ada0s3  BSD  (25G)
         0      1038          - free -  (519k)
      1038  52305920       1  freebsd-ufs  (25G)
  52306958       682          - free -  (341k)

=>     0  853965  da0s1  BSD  (417M)
       0    1985         - free -  (992k)
    1985  851968      1  freebsd-ufs  (416M)
  853953      12         - free -  (6.0k)

=>      0  1052667  da0s2  BSD  (514M)
        0     2036         - free -  (1M)
     2036  1048576      2  freebsd-swap  (512M)
  1050612     2055         - free -  (1.0M)

=>    0  28665  da0s3  BSD  (14M)
      0   2041         - free -  (1M)
   2041  24576      1  freebsd-ufs  (12M)
  26617   2048         - free -  (1.0M)

------------

$ glabel status
                  Name  Status  Components
ufsid/54baf92cc4bbdd4a     N/A  ada0s1a
           ufs/embboot     N/A  ada0s1a
ufsid/54bd5e3cd455f80a     N/A  ada0s3a
              ufs/data     N/A  ada0s3a
ufsid/54baf9c6b159d095     N/A  da0s1a
          ufs/liveboot     N/A  da0s1a

------------

$ df -h
Filesystem    Size    Used   Avail Capacity  Mounted on
/dev/xmd0     119M     33M     86M    28%    /
devfs         1.0k    1.0k      0B   100%    /dev
/dev/xmd1     719M    246M    472M    34%    /usr/local
procfs        4.0k    4.0k      0B   100%    /proc
/dev/xmd2     123M    684k    113M     1%    /var
tmpfs          64M     32k     64M     0%    /var/tmp

-------------

$ diskinfo -v ada0
ada0
	512         	# sectorsize
	31937527808 	# mediasize in bytes (29G)
	62377984    	# mediasize in sectors
	0           	# stripesize
	0           	# stripeoffset
	66008       	# Cylinders according to firmware.
	15          	# Heads according to firmware.
	63          	# Sectors according to firmware.
	984081900122	# Disk ident.

Thank you for helping me, I do appreciate it!

[armandh]

I have had brands other than my favorite [above linked] go bad
give it the sniff test for burnt phenolic

[daoyama]

Looks like the web interface works just fine when booting from USB. I was able to run the commands after booting from the LiveUSB, here are the results:

Thank you.
Your installation layout seems good no problem.
What size of memory do you use?
It may fail on out of memory when extracting compressed archive.

After console menu disabled, you should see backlog by pressing "Scroll Lock" key and
PageUP/Down, cursor keys.
Do you see somthing error? (around "Creating 2nd memory disk")

This is VM's result but you can see like this:

20150121A.png

Also you may login from 2nd console by pressing "PrintScreen/SysRq" key.
login as root and password is empty.
If success, please check your conditions by same command(gpart etc).
Additionally, please run "top -b" and post the lines starting from "Mem:" and "Swap:".

Thanks,

[Juniorc]

Hi,

Could you please make sure that your

/cf/boot/device.hints

contains:

Code: Select all

# SS4200 - Find PATA
hint.ata.0.at="isa"
hint.ata.0.port="0x1F0"
hint.ata.0.irq="14"

Without it FreeBSD will not find your DOM.

Cheers,

[Antwon]

I've only got 512MB of RAM and it looks like it errors out after 'Creating 2nd Memory Disk'. I see the following:

Code: Select all

Booting with low memory
Creating 2nd memory disk for x64-embedded
swapon: /dev/: Block device required
mount: /dev: Block device required
/mnt/mdlocal.xz (1/1)
/usr/bin/xz: /mnt/mdlocal.xz: No such file or directory
umount: /mnt: not a file systemroot directory
mount: /dev/xmd1: Invalid argument
ldconfig: warning: /usr/local/lib: No such file or directory
Loading configuration files.

And then it goes on a long list of different files that aren't found.

So more memory would fix this? Why would it boot just fine using the LiveUSB but not with the DOM?

@Juniorc

I'll check that tonight when I get home.