Root Mount Error

jaredadams

running the command does not put the line in the file.

going to load up an ubuntu vm and hope it passes usb through and can actually read my usb cf reader

stephenw10

@jaredadams:

running the command does not put the line in the file.

Does it create an empty file?

Steve

jaredadams

the file was empty before i ran that command.

it stayed empty afterwards.

ubuntu cannot read the CF. WTF

jaredadams

got it to boot in safe mode, trying to add those two lines to the loader.conf file now that i have a vi editor.

gonna go brush up onmy vi…. google here i come.

edit

read only file system! wq! doesnt even work.

jaredadams

SOLVED

1. Boot pfsense in safemode
2. Once booted fully enter the shell
3. i changed folders to /boot
4. run command

 mount -u /

5. run command

vi loader.conf

6. enter two lines of code supplied by Steve (THANKS!)

@stephenw10:

hw.ata.ata_dma="0"
hw.ata.wc="0"

7. save
8. exit shell
9. reboot

stephenw10

You should put custom loader options in /boot/loader.conf.local, it gets copied across a firmware update where as loader.conf may not be.

I'm surprised those lines weren't already present to be honest. What image are you using exactly?

Steve

jaredadams

I'm using the nano 512MB image vga console on a 1GB card.

There is no loader.conf.local. Should there be one? Should I make it?

stephenw10

Yes, create it.

I see no 'safe mode' option when I boot.
It's a bit odd. Is it possible that the 512MB image is using a different boot loader config? Are you using VGA and keyboard or serial console?

Steve

Edit: I see you're using VGA. Too late to read properly, need sleep!

jaredadams

Should i create it and add the two lines just like the other one? You're saying that even if i update that any changes an update might do will not have any effect on the loader?

dLockers

@jaredadams:

"it" = ?
"config file" = ?

I assume you're referring to what Steve just told me, but just like in the other thread you gave no indication what those things are.

In case anyone else finds this thread, this is what works for me regarding the MaxTerm 8300B, with a 4GB CompactFlash card (SanDisk, if it makes any difference).

1.) Install on the CF card as normal
2.) Boot into safe mode (Option 4 IIRC - you need VGA or console access)
3.) Go to WebConfigurator
4.) Diagnostics > Edit File
5.) Enter '/boot/loader.conf' for the file
6.) The file is blank currently, add 'ahci_load="YES"'
7.) Reboot, should work fine.

I have tried adding ata_dma before and it didn't seem to work, however try adding:

hw.ata.ata_dma="0"
hw.ata.wc="0"

If you still have issues.

stephenw10

When 2.1 comes out or some critical security flaw is found prompting a 2.0.2 release then you can update to that by simply clicking the update button in the GUI.
The update process will never overwrite loader.conf.local but it may (or may not) alter loader.conf. Usually it would not since that's not how the NanoBSD filesystem works.
It's easier to keep track of your own alterations by putting them in a different file anyway.

It looks from reading this with fresh(er) eyes that the Nano+VGA images do not have DMA disabled by default, which can be a problem as you have found.

Steve

jaredadams

@dLockers:

@jaredadams:

"it" = ?
"config file" = ?

I assume you're referring to what Steve just told me, but just like in the other thread you gave no indication what those things are.

In case anyone else finds this thread, this is what works for me regarding the MaxTerm 8300B, with a 4GB CompactFlash card (SanDisk, if it makes any difference).

1.) Install on the CF card as normal
2.) Boot into safe mode (Option 4 IIRC - you need VGA or console access)
3.) Go to WebConfigurator
4.) Diagnostics > Edit File
5.) Enter '/boot/loader.conf' for the file
6.) The file is blank currently, add 'ahci_load="YES"'
7.) Reboot, should work fine.

I have tried adding ata_dma before and it didn't seem to work, however try adding:

hw.ata.ata_dma="0"
hw.ata.wc="0"

If you still have issues.

@jaredadams:

SOLVED

1. Boot pfsense in safemode
2. Once booted fully enter the shell
3. i changed folders to /boot
4. run command
 mount -u / 
5. run command
vi loader.conf
6. enter two lines of code supplied by Steve (THANKS!)

@stephenw10:

hw.ata.ata_dma="0"
hw.ata.wc="0"

7. save
8. exit shell
9. reboot

Now THATS how you write a resolution post. With the way I named it, this thread will more than likely show up in searches in the future. Glad we gave a resolution.