Uploading plugins fails - "an error occured"

[Gert VD]

Hi,

I have installed the jail succesfully (I think), now I am uploading a plugin, but when the upload proces bar appears , it suddenly disappears again and "an error occured" shows up.

This shows up down below:

Jun 26 20:58:11 freenas notifier: mkdir: archive: Read-only file system
Jun 26 20:58:11 freenas notifier: chown: archive/.freenas: No such file or directory
Jun 26 20:58:11 freenas notifier: chmod: archive/.freenas: No such file or directory
Jun 26 20:58:11 freenas notifier: ln: /var/tmp/firmware: No such file or directory

Probably something simple, but I would appreciate the help.

EDIT:

dmesg:

da0: 3843MB (7870464 512 byte sectors: 255H 63S/T 489C) cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: <MATSHITA DVD-RAM UJ890AS 1.00> Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c losed GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s). Trying to mount root from ufs:/dev/ufs/FreeNASs1a WARNING: /data was not properly dismounted GEOM_ELI: Device ada0p1.eli created. GEOM_ELI: Encryption: AES-XTS 256 GEOM_ELI: Crypto: software ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version 5 ZFS storage pool version 28 bridge0: Ethernet address: 02:29:27:99:f1:00 epair0a: Ethernet address: 02:00:c2:00:0b:0a epair0b: Ethernet address: 02:00:c2:00:0c:0b epair0a: link state changed to UP epair0b: link state changed to UP epair0a: promiscuous mode enabled alc0: promiscuous mode enabled [root@freenas ~]#

 

[dlavigne]

Was the system properly shutdown? You have a "WARNING: /data was not properly dismounted" which sounds like the system might need an fsck.

 

[Gert VD]

dlavigne,

thanks for your reply!
Yes, my system was not properly shutdown. I have used plugwise powercontrol, wich shuts down power according to a schedule. I supose this "fsck" is a command I must type in at the shell prompt?(total n00b here)
I will try this when back home.

ps: is there a better way for automated pause or shutdown for my NAS-system (laptop)?

Grts,
G

 

[Gert VD]

Tried fsck, with no positive result.

2 files, 2 used, 2829 free (21 frags, 351 blocks, 0.7% fragmentation) ***** FILE SYSTEM IS CLEAN ***** ** /dev/ufs/FreeNASs4 (NO WRITE) ** Last Mounted on /data ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 9 files, 1033 used, 39494 free (30 frags, 4933 blocks, 0.1% fragmentation) ** /dev/ufs/NASDisk1 (NO WRITE) ** Last Mounted on /mnt/NASDisk1 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no 24978 files, 149373 used, 76248937 free (297 frags, 9531080 blocks, 0.0% fragmen tation)

Also, when restarting freenas, I now get two IP-adresses: regular one & 0.0.0.0?

 

[dlavigne]

When performing fsck, use "fsck -y" to make sure inconsistencies get fixed.

Whatever you are using to shutdown the system, needs to pass the shutdown command. You can schedule this command yourself at the commandline or create a cron job to automate it.

 

[Gert VD]

Okay,
all this fsck -y did nothing. From what I could understand by googling "mkdir: archive: Read-only file system", there's a problem with my usb-stick that runs freenas(correct me when wrong). I had no idea of how to fix this command-wise, so I uninstalled the jail, unplugged the usb, replugged it, reboot the system, re-installed the jail and installed the plugin. No problem occured!
I will now make sure to correctly shutdown the system by trying to find out how this cron-buissines works. Exciting! hehe.

Thanks for your time and input!