January 22, 20179 yr When I reboot I can't access the web GUI without using the killall emhttp nohup /usr/local/sbin/emhttp & I can then access the GUI. However all my plugins, dockers and settings are gone! Once I re-add plugins, etc. The configurations seem to come back but only after re-installing them. I have read around and used some google-fu but I can't figure it out... Here is my syslog: ErrorWarningSystemArrayLogin Jan 22 12:50:41 Tower root: plugin: creating: /boot/config/plugins/NerdPack/NerdPack-2016.10.20-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/archive/NerdPack-2016.10.20-x86_64-1.txz Jan 22 12:50:41 Tower root: plugin: creating: /boot/config/plugins/NerdPack/NerdPack-2016.10.20-x86_64-1.md5 - downloading from URL https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/archive/NerdPack-2016.10.20-x86_64-1.md5 Jan 22 12:50:41 Tower root: plugin: running: anonymous Jan 22 12:50:42 Tower nerdpack: Processing Packages... Jan 22 12:50:42 Tower nerdpack: All packages processed... Jan 22 12:51:15 Tower emhttp: cmd: /usr/local/emhttp/plugins/NerdPack/scripts/packagemanager --download Jan 22 12:51:15 Tower nerdpack: Processing Packages... Jan 22 12:51:15 Tower nerdpack: Downloading perl-5.22.2-x86_64-1.txz package... Jan 22 12:51:17 Tower nerdpack: perl-5.22.2-x86_64-1.txz package download sucessful! Jan 22 12:51:17 Tower nerdpack: Installing perl-5.22.2 package... Jan 22 12:51:20 Tower nerdpack: utempter-1.1.6 used by plugin: preclear.disk Jan 22 12:51:20 Tower nerdpack: All packages processed... Jan 22 12:51:32 Tower kernel: i2c /dev entries driver Jan 22 12:52:25 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=244188659 blks Jan 22 12:52:25 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 22 12:52:25 Tower root: = crc=1 finobt=1, sparse=0 Jan 22 12:52:25 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 22 12:52:25 Tower root: = sunit=0 swidth=0 blks Jan 22 12:52:25 Tower root: naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Jan 22 12:52:25 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Jan 22 12:52:25 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 22 12:52:25 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 22 12:52:25 Tower emhttp: shcmd (1494): mkdir -p /mnt/disk2 Jan 22 12:52:26 Tower emhttp: shcmd (1495): set -o pipefail ; mount -t btrfs,xfs,reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Jan 22 12:52:26 Tower kernel: XFS (md2): Mounting V5 Filesystem Jan 22 12:52:26 Tower kernel: XFS (md2): Ending clean mount Jan 22 12:52:26 Tower emhttp: shcmd (1496): xfs_growfs /mnt/disk2 |& logger Jan 22 12:52:26 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=244188659 blks Jan 22 12:52:26 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 22 12:52:26 Tower root: = crc=1 finobt=1 spinodes=0 Jan 22 12:52:26 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 22 12:52:26 Tower root: = sunit=0 swidth=0 blks Jan 22 12:52:26 Tower root: naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Jan 22 12:52:26 Tower root: log =internal bsize=4096 blocks=476930, version=2 Jan 22 12:52:26 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 22 12:52:26 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 22 12:52:26 Tower emhttp: shcmd (1498): chmod 0777 '/mnt/disk2' Jan 22 12:52:26 Tower emhttp: shcmd (1499): chown 'nobody':'users' '/mnt/disk2' Please help!
January 22, 20179 yr You can't kill emhttp and then restart it. You need to fix the underlying problem. Post your diagnostics zip.
January 22, 20179 yr Author You can't kill emhttp and then restart it. You need to fix the underlying problem. Post your diagnostics zip. Of course. Thank you. Attached. tower-diagnostics-20170122-1313.zip
January 22, 20179 yr Jan 22 12:31:10 Tower emhttp: Warning: Flash device not mounted! Jan 22 12:26:15 Tower kernel: FAT-fs (sda1): bogus number of reserved sectors Jan 22 12:26:15 Tower kernel: FAT-fs (sda1): Can't find a valid FAT filesystem You might want to pop the flash drive into your desktop and let it run the file system checks on it. With these errors, unRaid is never going to save your configuration info. You also have an issue on disk2 where it has file system errors. (But concentrate on the flash before worrying about this) You also inadvertently found an issue with Fix Common Problems, because its not complaining about the flash drive....
January 22, 20179 yr Author Do I need to format the flash drive as FAT? Also Does it matter if it is USB 2 or 3?
January 22, 20179 yr Do I need to format the flash drive as FAT? Also Does it matter if it is USB 2 or 3? Flash has to be FAT / FAT32 Nothing else will work properly USB 2/3 should matter in theory, but some mobo's have better compatibility with USB 2
January 22, 20179 yr Author THAT WAS IT! Thanks so much guys. Especially you squid. I really appreciate it. By the way Fix Common Problems is AWESOME!
January 22, 20179 yr THAT WAS IT! Thanks so much guys. Especially you squid. I really appreciate it. By the way Fix Common Problems is AWESOME! Thanks... Checked my code and FCP does check for the ability to write to the flash, and it passed somehow on your system... Its one of those tests thats a real PITA for me to actually test on my system though...
January 22, 20179 yr Author Yeah I was being dumb and using a 128gb drive... formatted as NTFS... lol
January 22, 20179 yr Yeah I was being dumb and using a 128gb drive... formatted as NTFS... lol You are able to format a flash >32Gig as FAT32 if you jump through some hoops. (Google will help out here), but its major overkill... My main server uses an 8GB stick and its a whopping 450Meg in use...
Archived
This topic is now archived and is closed to further replies.