BlackCat
-
Posts
93 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by BlackCat
-
-
Everyone's go file is different, but usually all you would need to do is comment out any lines in the go script that start addons, to return it to its 'factory' state. You comment them out by placing a # (pound symbol) at the start of the line. I would make a backup of your flash drive first.
In UnMENU, you would turn off the Auto Install on reboot for any package you don't want running on the next boot.
I know I haven't been very helpful here, but hopefully given a few 'tools' to try. It's going to be a trial and error process.
Rob thanks for the tips, it gives me a good starting point. While, I am doing this I probably should remove my parity drive? That way if I screw something up it doesn't start a rebuild or something that screws up my data, or is something of that nature only triggered manually?
Nevermind: Found this http://lime-technology.com/forum/index.php?topic=9794.0
Well I uninstalled SNAP and my errors went away. I would still like to know what the following errors mean for future reference if anyone knows:
Errors:
Jan 25 10:26:30 Tower apcupsd[4296]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded
Jan 25 10:26:30 Tower apcupsd[4296]: NIS server startup succeeded
Jan 25 10:26:31 Tower kernel: inotifywait[5269]: segfault at a96d7f80 ip b78c2638 sp bfc6bd94 error 6 in ld-2.7.so[b78bc000+1c000] (Errors)
Jan 25 10:26:31 Tower kernel: inotifywait[5271]: segfault at a96f0f80 ip b78db638 sp bffc2d64 error 6 in ld-2.7.so[b78d5000+1c000] (Errors)
Jan 25 10:26:36 Tower ntpd[4812]: synchronized to 207.171.7.151, stratum 2
Jan 25 10:26:36 Tower ntpd[4812]: time reset -0.531180 s
SNAP uses inotifywait to detect events. That package is installed in lots of other machines so I can't tell you what might be happening there. I know unMenu has a different version of inotifywait on it's packages management page. SNAP includes and installs an inotify package if one is not found to be installed in /usr/bin/inotifywait. It might be worth investigating which is installed.
Well when SNAP was installed the package manager said that inotify tools was installed but not downloaded. However, when I looked in the /boot/packages, inotify-tools-3.8-i486-1 was in there. Doesn't that mean that it is downloaded as well? Now that I have uninstalled SNAP, package manager says that inotify tools is not downloaded, but I still see inotify-tools-3.8-i486-1 in /boot/packages.
Also, I pulled out my Hitachi drive and attached it to my laptop to see if the drive had become corrupt since UnRaid wasn't showing that it could be mounted. But once attached to my laptop the drive works fine. So I put it back into unraid, with snap uinistalled, but still there is no mount option in unmenu and i have the ntfs-3g - NTFS read/write filesystem driver installed.
Any ideas?
-
Everyone's go file is different, but usually all you would need to do is comment out any lines in the go script that start addons, to return it to its 'factory' state. You comment them out by placing a # (pound symbol) at the start of the line. I would make a backup of your flash drive first.
In UnMENU, you would turn off the Auto Install on reboot for any package you don't want running on the next boot.
I know I haven't been very helpful here, but hopefully given a few 'tools' to try. It's going to be a trial and error process.
Rob thanks for the tips, it gives me a good starting point. While, I am doing this I probably should remove my parity drive? That way if I screw something up it doesn't start a rebuild or something that screws up my data, or is something of that nature only triggered manually?
Nevermind: Found this http://lime-technology.com/forum/index.php?topic=9794.0
Well I uninstalled SNAP and my errors went away. I would still like to know what the following errors mean for future reference if anyone knows:
Errors:
Jan 25 10:26:30 Tower apcupsd[4296]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded
Jan 25 10:26:30 Tower apcupsd[4296]: NIS server startup succeeded
Jan 25 10:26:31 Tower kernel: inotifywait[5269]: segfault at a96d7f80 ip b78c2638 sp bfc6bd94 error 6 in ld-2.7.so[b78bc000+1c000] (Errors)
Jan 25 10:26:31 Tower kernel: inotifywait[5271]: segfault at a96f0f80 ip b78db638 sp bffc2d64 error 6 in ld-2.7.so[b78d5000+1c000] (Errors)
Jan 25 10:26:36 Tower ntpd[4812]: synchronized to 207.171.7.151, stratum 2
Jan 25 10:26:36 Tower ntpd[4812]: time reset -0.531180 s
-
Those minor issues are nothing, or harmless. The segfaults on the other hand *are* a problem, but unfortunately I have no experience with inotifywait, so I'll defer to someone else with more experience there.
Hopefully someone will know. I figured the minor issues probably weren't anything, but I couldn't remember which issues I was seeing before everything got funky.
In case you had not found it, that vertical line character is the 'pipe' symbol, the shift of the backslash key.
I had not found it. I was not even sure what it was called when looking. I'll add that into my new command line knowledge. Of course now I see the command on the keyboard, I looked and looked, figures.
Well, I just finished examining all 3 syslogs, and while I ambitiously had hoped to find problems and offer fixes, --- I can't! Except for the segfault, there is nothing wrong with your core system. I could not help getting a little jealous of how fast your system is, but you probably don't consider *that* a problem!
Thanks for looking through all those logs. It's good to hear the system working well pending the segfault. As far as the speed, yea no problems here running air video , The server is actually faster than my laptop, haha. For better or worse I ended up taking the backwards route to upgrading.
Earlier, I agree there must have been a malfunction. When it could not find "/boot/config/network.cfg", that probably meant that the flash drive was down, and that explains why you could not save syslogs to it then. You do have a number of addons loaded, I suspect there is an issue with one of them. You might try returning to a clean system, then adding addons back one at a time, and retesting whatever you had previously been attempting to do.
The flash drive being down makes sense because I saw a bunch of info fly by about mounting a usb device at start-up. My Unraid flash drive was the only usb device attached. Previous to restarting and having those errors, I installed the ntfs-3g package through unMenu. I was thinking that it might help the system readi my Hitachi NTFS drive. Although I knnew I shouldn't need to install it based on the description. I also installed the monthly parity check package at that time. I had been forgetting to install it and remembered right then. Not thinking about the fact I was having problems already, I installed it. As far as returning to a clean install, can I just unistall my packages through unMenu and SNAP via the command line? Or do I need to wipe the usb device and start clean that way?
-
So my parity check completed with zero errors. Looking at the system log I have a few minor issues and 2 Errors. I have attached the system log. I could use some help decoding them thanks.
Minor Issues:
Jan 25 10:26:19 Tower kernel: NET: Registered protocol family 16
Jan 25 10:26:19 Tower kernel: ACPI: bus type pci registered
Jan 25 10:26:19 Tower kernel: PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
Jan 25 10:26:19 Tower kernel: PCI: MCFG area at e0000000 reserved in E820
Jan 25 10:26:19 Tower kernel: PCI: Using MMCONFIG for extended config space
Jan 25 10:26:19 Tower kernel: PCI: Using configuration type 1 for base access
Jan 25 10:26:19 Tower kernel: bio: create slab <bio-0> at 0
Jan 25 10:26:19 Tower kernel: ACPI: EC: Look up EC in DSDT
Jan 25 10:26:19 Tower kernel: ACPI Warning for \_SB_._OSC: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) (Minor Issues)
Jan 25 10:26:19 Tower kernel: \_SB_:_OSC evaluation returned wrong type
Jan 25 10:26:19 Tower kernel: _OSC request data:1 6
Jan 25 10:26:19 Tower kernel: ACPI: Executed 1 blocks of module-level executable AML code
Jan 25 10:26:19 Tower kernel: ACPI: Interpreter enabled
Jan 25 10:26:19 Tower kernel: ACPI: (supports S0 S1 S5)
Jan 25 10:26:19 Tower kernel: ACPI: Using IOAPIC for interrupt routing
Jan 25 10:26:19 Tower kernel: ACPI Warning: Incorrect checksum in table [OEMB] - A0, should be 9D (20090903/tbutils-314) (Minor Issues)
Jan 25 10:26:19 Tower kernel: ACPI: No dock devices found.
Jan 25 10:26:19 Tower kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jan 25 10:26:19 Tower kernel: md: recovery thread has nothing to resync (unRAID engine)
Jan 25 10:26:20 Tower emhttp: shcmd (12): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp)
Jan 25 10:26:20 Tower emhttp: _shcmd: shcmd (12): exit status: 1 (Other emhttp)
Jan 25 10:26:20 Tower emhttp: shcmd (13): cp /etc/exports- /etc/exports (Other emhttp)
Jan 25 10:26:20 Tower emhttp: shcmd (14): mkdir /mnt/user (Other emhttp)
Jan 25 10:26:20 Tower emhttp: shcmd (15): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions (Other emhttp)
Jan 25 10:26:21 Tower emhttp: shcmd (16): killall -HUP smbd (Minor Issues)
Jan 25 10:26:21 Tower emhttp: shcmd (17): /etc/rc.d/rc.nfsd restart | logger (Other emhttp)
Jan 25 10:26:22 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX (Network)
Jan 25 10:26:22 Tower ifplugd(eth0)[1441]: Link beat detected. (Network)
Errors:
Jan 25 10:26:30 Tower apcupsd[4296]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded
Jan 25 10:26:30 Tower apcupsd[4296]: NIS server startup succeeded
Jan 25 10:26:31 Tower kernel: inotifywait[5269]: segfault at a96d7f80 ip b78c2638 sp bfc6bd94 error 6 in ld-2.7.so[b78bc000+1c000] (Errors)
Jan 25 10:26:31 Tower kernel: inotifywait[5271]: segfault at a96f0f80 ip b78db638 sp bffc2d64 error 6 in ld-2.7.so[b78d5000+1c000] (Errors)
Jan 25 10:26:36 Tower ntpd[4812]: synchronized to 207.171.7.151, stratum 2
Jan 25 10:26:36 Tower ntpd[4812]: time reset -0.531180 s
-
Well I tried using CTRL+ALT+DEL to shutdown (i do have the power down script installed), but it did not work. I ended up just holding the power button to power off.
Here is what I got on the command line using CTRL+ALT+DEL:
The system is going down for reboot NOW!
Sending processes the TERM signal
^[[4~Jan 25 14:24:11 Tower shutdown[1470]: shutting down for system reboot
Jan 25 14:24:11 Tower init: Switching to runlevel: 6
INIT: Sending processes the KILL signal
Running shutdown script /etc/rc.d/rc.6:
Saving system time to the hardware clock (UTC).
Unmounting remote filesystems.
/etc/rc.d/rc.inet1.conf: line 18: /boot/config/network.cfg: No such file or directory
/etc/rc.d/rc.inet1.conf: line 19: /var/tmp/network.cfg: No such file or directory
INIT: no more processes left in this runlevel
Once I shut down, I found that Unraid did not save my system log after I use the following commands in the troubleshooting section:
cp /var/log/syslog /boot/syslog-2011-01-24.txt
chmod a-x /boot/syslog-2011-01-24.txt
So I have attached the two system logs for yesterday that unraid did save on its own in the log folder.
Edit:
So I took out the Hitachi drive and booted the system. No weird network errors on the screen. Right now I am running a read-only parity check to see if anything was fouled up.
-
You are having system problems that require some help I think. You probably need to post in the unraid support thread. Once your system is reliable again we can get SNAP going for you.
Already beat you to it . Thanks for the help.
-
They usually have large sheets of nice filter material in the isle where they have furnace filters. If you can find them or your particular home depot doesn't have them buy the best large furnace filter you can buy then use that material inside the filter. Hey, it's all suppose to do one thing. Block dust from going through it.
Thanks , I'll have to take another look, hopefully this weekend.
-
The best thing you can do to keep dust out of your server is to keep it off the floor. Getting it even one or two feet off the ground will mitigate dust build up dramatically. I generally only clean out my server every 6 months or so, and I've got no dust filters at all.
Thanks for the advice. It is up off the floor on the coffee table/tv stand, but I'm still getting quit a bit of dust. I have to clean the filters I have in the front and back of the case about every two weeks.
-
I would just goto home depot and get some dust filters and make your own. They are cheap as heck too. Even some of that material on the forced hot air heater filters would work good. Traps just about everything and lets all the air through. I haven't setup my complete server yet but I do plan on using some kind of filters on my 5in3's cages.
Thanks for the suggestion. Where is the dust filter material in home depot? I had looked for it before but just got the run around at the store.
-
Ok so this started in the SNAP thread, but now my problems seem to be larger than that. I figure I probably should move my problems over here, but here is the thread in case you are interested. http://lime-technology.com/forum/index.php?topic=5904.210, starting around reply#217,.
My version of unraid is 4.5.6. I can't get to my system log to post it. I saved it to the usb but I have no way of shutting down my server that I know of. I can't get in via telnet or webGUI. Also, I ran the "tail -f --lines=100 /var/log/syslog" command and now I just have a blinking command prompt. No root@tower to be seen.
I was trying to get SNAP working and get it to mount my NTFS drive correctly. Created the share, but it wasn't showing up so then the following happened:
I installed the ntfs add-on from the unraid menu thinking well maybe it would help, even though I shouldn't need it. So I restarted and now the last two lines on my command screen are:
/etc/rc.d/rc/inet1.conf : line 18: /boot/config/network.cfg: No such file or directory
/etc/rc.d/rc.inet1.conf: line 19: /var/tmp/network.ctfg: No such file or directory
There are a bunch of lines above those that I don't recognize either.
At log-in on the server console it didn't ask for my password and let me in after root.
I can't access the server from telnet or the web interface. I haven't yet set a static ip so Im sure that doesnt help since the router went down for a minute during reboot.
Edit:
Just tried /etc/rd.d/rc.inetd restart and I get
-bash: /etc/rd.d/rc.inetd: No such file or directory
Tried: smbstatus get
/var/cache/samba/locking.tdb not initialised
This is normal if an SMB client has never connected to your sever.
-Which is false since I have been sharing my movies this way across my home network
Ugh Angry
Testparm:
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Can't find include file /etc/samba/smb-names.conf
Can't find include file /boot/config/smb-extra.conf
Can't find include file /etc/samba/smb-shares.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
passdb backend = smbpasswd
syslog = 0
syslog only = Yes
unix extensions = No
loadprinters = No
printcap name = /dev/null
disable spoolss = Yes
show add printer wizard = No
use sendfile = Yes
msdfs root = Yes
Then:
There is something not right for sure. Is your array still functional? Any weird messages in syslog? If the array parts are working then maybe the drive, cable or something like that is bad.
How do I dump a syslog from the command line?(Found this in the troubleshooting guide) I have a monitor and keyboard hooked up to the server. I can't get to things any other way. What is the powerdown command? I have the script installed but last time I tried CTRL+ALT+DEL it didn't like that.
OK time to stop touching stuff I ran: tail -f --lines=100 /var/log/syslog
and now I just have a blinking command prompt at the bottom of the screen.
Seems like I am having issues poping up after having the same thing happen as this post:
http://lime-technology.com/forum/index.php?topic=8489.0
My unRaid 4.5.6 installation currently seems to be stuck attempting to power down. Here is how the issue came to be:
After setting up my data drives, I installed a parity drive. After several days, I ended up doing a forced reboot (I don't remember the circumstances now - I think it may have been a networking setting change). Everything seemed to be working fine for a little while after that, but then I lost connectivity to the array (via web, telnet, and samba)...
*SideNote: How do I create that line in the command between syslog and more? See Below
cat /var/log/syslog | more
This is were I left off.
-
There is something not right for sure. Is your array still functional? Any weird messages in syslog? If the array parts are working then maybe the drive, cable or something like that is bad.
How do I dump a syslog from the command line?(Found this in the troubleshooting guide) I have a monitor and keyboard hooked up to the server. I can't get to things any other way. What is the powerdown command? I have the script installed but last time I tried CTRL+ALT+DEL it didn't like that.
OK time to stop touching stuff I ran: tail -f --lines=100 /var/log/syslog
and now I just have a blinking command prompt at the bottom of the screen.
Seems like I am having issues poping up after having the same thing happen as this post:
http://lime-technology.com/forum/index.php?topic=8489.0
My unRaid 4.5.6 installation currently seems to be stuck attempting to power down. Here is how the issue came to be:
After setting up my data drives, I installed a parity drive. After several days, I ended up doing a forced reboot (I don't remember the circumstances now - I think it may have been a networking setting change). Everything seemed to be working fine for a little while after that, but then I lost connectivity to the array (via web, telnet, and samba)...
*SideNote: How do I create that line in the command between syslog and more? See Below
cat /var/log/syslog | more
-
Well I found this post: http://lime-technology.com/forum/index.php?topic=5961.0 I hoping the file system on that hard drive didn't get corrupted and thats why I can't mount it.
Also, something else is going on and now things are really messy. I installed the ntfs add-on from the unraid menu thinking well maybe it would help, even though I shouldn't need it. So I restarted and now the last two lines on my command screen are:
/etc/rc.d/rc/inet1.conf : line 18: /boot/config/network.cfg: No such file or directory
/etc/rc.d/rc.inet1.conf: line 19: /var/tmp/network.ctfg: No such file or directory
There are a bunch of lines above those that I don't recognize either.
At log-in on the server console it didn't ask for my password and let me in after root.
I can't access the server from telnet or the web interface. I haven't yet set a static ip so Im sure that doesnt help since the router went down for a minute during reboot.
Edit:
Just tried /etc/rd.d/rc.inetd restart and I get
-bash: /etc/rd.d/rc.inetd: No such file or directory
Tried: smbstatus get
/var/cache/samba/locking.tdb not initialised
This is normal if an SMB client has never connected to your sever.
-Which is false since I have been sharing my movies this way across my home network
Ugh
Testparm:
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Can't find include file /etc/samba/smb-names.conf
Can't find include file /boot/config/smb-extra.conf
Can't find include file /etc/samba/smb-shares.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
passdb backend = smbpasswd
syslog = 0
syslog only = Yes
unix extensions = No
loadprinters = No
printcap name = /dev/null
disable spoolss = Yes
show add printer wizard = No
use sendfile = Yes
msdfs root = Yes
-
Well I found this post: http://lime-technology.com/forum/index.php?topic=5961.0 I hoping the file system on that hard drive didn't get corrupted and thats why I can't mount it.
Also, something else is going on and now things are really messy. I installed the ntfs add-on from the unraid menu thinking well maybe it would help, even though I shouldn't need it. So I restarted and now the last two lines on my command screen are:
/etc/rc.d/rc/inet1.conf : line 18: /boot/config/network.cfg: No such file or directory
/etc/rc.d/rc.inet1.conf: line 19: /var/tmp/network.ctfg: No such file or directory
There are a bunch of lines above those that I don't recognize either.
At log-in on the server console it didn't ask for my password and let me in after root.
I can't access the server from telnet or the web interface. I haven't yet set a static ip so Im sure that doesnt help since the router went down for a minute during reboot.
Edit:
Just tried /etc/rd.d/rc.inetd restart and I get
-bash: /etc/rd.d/rc.inetd: No such file or directory
Ugh
-
Go to the Disk Management page.
I don't see a mount option, I attached a screen shot.
-
You certainly are getting lots of odd errors.
What version of unraid are you using?
What version of windows?
Do you have unmenu installed? If so, attempt to mount the drive from unmenu. Does that work?
Unraid version: 4.5.6
Windows XP Pro SP2
I have unmenu installed, How do I mount a drive through unmenu? I have to leave for the dentist in a few minutes so I quickly scanned through unmenu and the help, but I failed to find how to do this. Thanks for the help.
-
snap.sh -a Zebra JP2930HQ12T2KH
should add the device to the snap.list file and then SNAP will mount and share the device when it's detected. The devices are detected at boot time or when one is inserted or pulled out. To manually make SNAP check for devices you can do a snap.sh -u
I did snap.sh -a JBODEx1 JP2930HQ12T2KH and when I rebooted my snap.list problem went away, but I can not find the drive share. I tried to type in \\tower\JBODEx1 in the address bar in my windows explore and it asks for my user name and password. I enter root for user and my password, but it is not accepted. I don't see it in the /mnt directory either. I went through the thread and tried a few commands to find more info I posted below:
Tower login: root
Password:
Linux 2.6.32.9-unRAID.
root@Tower:~# cd /boot/config/snap
root@Tower:/boot/config/snap# snap.sh -listDeviceConfigurationInfo
unRAID=No SNAP=Yes 3818 /dev/sdd /dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP2930HQ12T2KH
unRAID=Yes SNAP=No 3610 /dev/sda /dev/disk/by-id/ata-ST32000542AS_5XW1NWJY
unRAID=Yes SNAP=No 3760 /dev/sdc /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0324519
unRAID=Yes SNAP=No 3701 /dev/sdb /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0423649
unRAID=No SNAP=Yes 3818 /dev/sdd /dev/disk/by-id/scsi-SATA_Hitachi_HDS7210_JP2930HQ12T2KH
unRAID=Yes SNAP=No 3610 /dev/sda /dev/disk/by-id/scsi-SATA_ST32000542AS_5XW1NWJY
unRAID=Yes SNAP=No 3760 /dev/sdc /dev/disk/by-id/scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0324519
unRAID=Yes SNAP=No 3701 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0423649
unRAID=No SNAP=No 3916 /dev/sde /dev/disk/by-id/usb-Lexar_JD_FireFly_MHTTKFX5WL9V6JOB8BEY-0:0
root@Tower:/boot/config/snap# snap.sh -u
root@Tower:/boot/config/snap# snap.sh -m JBODEx1
basename: missing operand
Try `basename --help' for more information.
Partition doesn't exist, cannot be mounted.
root@Tower:/boot/config/snap# snap.sh -s JBODEx1
No such device exists: JBODEx1-part1
root@Tower:/boot/config/snap# cd /mnt
root@Tower:/mnt# dir
disk1/ disk2/ user/
root@Tower:/mnt# cd /user
-bash: cd: /user: No such file or directory
root@Tower:/mnt# mount
fusectl on /sys/fs/fuse/connections type fusectl (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sde1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)
/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)
/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)
shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)
root@Tower:/mnt# smbclient -N -L localhost
Anonymous login successful
Domain=[MY_HOME] OS=[unix] Server=[samba 3.4.5]
Sharename Type Comment
--------- ---- -------
flash Disk
Movies Disk Movie_Library
IPC$ IPC IPC Service (Media server)
Anonymous login successful
Domain=[MY_HOME] OS=[unix] Server=[samba 3.4.5]
Server Comment
--------- -------
TOSHIBA_LAPTOP Jackie's Computer
LAPTOP-JB JBs-Laptop
TOWER Media server
Workgroup Master
--------- -------
MY_HOME TOWER
root@Tower:/mnt# testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section ""
Processing section "[Movies]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = MY_HOME
server string = Media server
map to guest = Bad User
null passwords = Yes
passdb backend = smbpasswd
syslog = 0
syslog only = Yes
unix extensions = No
load printers = No
printcap name = /dev/null
disable spoolss = Yes
show add printer wizard = No
force user = root
create mask = 0711
directory mask = 0711
guest only = Yes
guest ok = Yes
use sendfile = Yes
map hidden = Yes
map system = Yes
msdfs root = Yes
path = /boot
read only = No
create mask = 0777
directory mask = 0777
map archive = No
map hidden = No
map system = No
[Movies]
comment = Movie_Library
path = /mnt/user/Movies
read only = No
root@Tower:/mnt#
-
No one has tried to minimize dust coming into their case through these harddrive cages?
-
Hang in there. inotify package gets copied to the /boot/packages folder when snap.sh -install is run, and also /boot/config/snap/snap.sh -b is added to the /boot/config/go file. When the system is started up the /boot/config/go file is run and when that happens snapNotify.sh is started. snapNotify.sh will install the inotify package if it's not already installed.
So, if you have not rebooted your machine then it's possible that /boot/config/snap/snap.sh -b hasn't been run yet. You can run that manually this time if you want. Then check if SNAP is running.
Ok, so I rebooted again this morning. I'm not sure why it was any different this time than the last since I had rebooted after I installed the first time. Any at the end of the boot I am seeing:
cat: /boot/config/snap/snap.list: No such file or directory
/boot/config/snap/snap.sh: All shares mounted
cat: /boot/config/snap/snap.list: No such file or directory
So I went ahead entered the snap.sh -listDeviceConfigurationInfo and I get the following:
Tower login: root
Linux 2.6.32.9-unRAID.
root@Tower:~# cd /boot/config/snap
root@Tower:/boot/config/snap# snap.sh -listDeviceConfigurationInfo
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=No SNAP=No 3819 /dev/sdd /dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP29 30HQ12T2KH
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3611 /dev/sda /dev/disk/by-id/ata-ST32000542AS_5XW1NWJY
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3761 /dev/sdc /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WCA ZA0324519
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3702 /dev/sdb /dev/disk/by-id/ata-WDC_WD20EARS-00MVWB0_WD-WCA ZA0423649
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=No SNAP=No 3819 /dev/sdd /dev/disk/by-id/scsi-SATA_Hitachi_HDS7210_JP2930 HQ12T2KH
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3611 /dev/sda /dev/disk/by-id/scsi-SATA_ST32000542AS_5XW1NWJY
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3761 /dev/sdc /dev/disk/by-id/scsi-SATA_WDC_WD20EARS-00_WD-WC AZA0324519
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=Yes SNAP=No 3702 /dev/sdb /dev/disk/by-id/scsi-SATA_WDC_WD20EARS-00_WD-WC AZA0423649
grep: /boot/config/snap/snap.list: No such file or directory
grep: /boot/config/snap/snap.list: No such file or directory
unRAID=No SNAP=No 3917 /dev/sde /dev/disk/by-id/usb-Lexar_JD_FireFly_MHTTKFX5WL9 V6JOB8BEY-0:0
root@Tower:/boot/config/snap#
What is the snap.list file that I am missing? And how do I fix it? Thanks again for the help.
-
Well I did run: root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration
BUT I see I forgot to add the next command line prompt.
After entering snap.sh -listDeviceConfiguration in the correct location
I am returned to the root@Tower:/boot/config/snap# prompt without seeing any device list.
I have attached my snapNotify and snapSambaNotify they both say, Error occured - inotify not installed
Would this be because I did not unzip the inotify-tools-3.8-i486-1.tgz file?
Hopefully that helps with the understanding of my problem, not that I'm understanding some basics.
I still need some help with this since it looks like my inotify tools didn't install. Should I run the uninstall command and then try to install SNAP again? Do I unzip the inotify-tools-3.8-i486-1.tgz file before running the install command? Can I install the missing items without uninstalling SNAP? I read through the thread all over again, but I didn't see (maybe i missed something) that shed some light on this.
-
~ stands for the home directory. for the user root it is /root
so, if you type "cd /root" or "cd ~" you get to the same directory
Ah, thanks. So then what I still don't quite understand is if I'm in the root directory (root@Tower:~#) and I type cd.. I get the command prompt root@Tower:/# this is the same thing as root@Tower:~# because you can't go up any directories past the root level?
No. They are different, "/" is not the same as "/root". If you are logged in as root, then "~" is the same as "/root". So, "/" is not "/root".
You were in "/root" (which is the same as "~" for user 'root'), then did a "cd ..", so you're then in "/".
The "/" is the root filesystem.
The "/root" is the home directory for user 'root'.
Most unix shells allow for "~" to be an abbreviation for the home directory for the current user.
Do not confuse root filesystem for root home directory.
Ok that helps to explain things. Thanks for the clarification.
-
~ stands for the home directory. for the user root it is /root
so, if you type "cd /root" or "cd ~" you get to the same directory
Ah, thanks. So then what I still don't quite understand is if I'm in the root directory (root@Tower:~#) and I type cd.. I get the command prompt root@Tower:/# this is the same thing as root@Tower:~# because you can't go up any directories past the root level? Sorry for the "dumb" questions I know this is basic knowledge for 90% of the people here.
Now I see my misunderstanding in my first post about GBH2's comment about what directory to look in. I was looking to the left of boot and not up to the # to see what directory I should be in.
Thanks for the help.
you can find the snap.sh file in the directory /boot/config/snap, so you first have to go there "cd /boot/config/snap"
or you can just use "/boot/config/scnap/snap.sh ...." from anywhere you like.
Well I did run: root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration
BUT I see I forgot to add the next command line prompt.
After entering snap.sh -listDeviceConfiguration in the correct location
I am returned to the root@Tower:/boot/config/snap# prompt without seeing any device list.
I have attached my snapNotify and snapSambaNotify they both say, Error occured - inotify not installed
Would this be because I did not unzip the inotify-tools-3.8-i486-1.tgz file?
Hopefully that helps with the understanding of my problem, not that I'm understanding some basics.
-
What is the difference between root@Tower:~# and just root@Tower:? I can get to root@Tower:/# by using "cd .." but I don't know how to get to just root@Tower:, any pointers?
Here is what I have done:
Tower login: root
Linux 2.6.32.9-unRAID.
root@Tower:~# cd ..
root@Tower:/# cd ..
root@Tower:/# snap.sh -listDeviceConfiguration
-bash: snap.sh: command not found
root@Tower:/#
root@Tower:/#
Also should I have unzipped the "inotify-tools-3.8-i486-1.tgz" file? I thought that UnRaid will unzip the *.tgz files on install so I didn't unzip it.
-
Ok I need some help. I install SNAP and the console said it was installed However, I missed this post:
I installed at root@Tower:~#, how do I even get to root@Tower:?Great Application! It really adds some extra utility to unRAID.
For completely clueless people like me, you may want to consider including a few things in the first post:
Must Format and Mount - can be done through unMENU - Disk Management
Scroll down to disk and select "Format to reiserfs"
then select mount as Read only / Writable
-- and --
Be sure you're at: root@Tower:/boot/config/snap# and not root@Tower:~#
to enter snap.sh -a [serialnumber] [sharename] and other snap.sh commands
Thanks!
So I turned off the server to install my internal drive and i cannot get the device list. Here is what I tried
Tower login: root
Linux 2.6.32.9-unRAID.
root@Tower:~# cd /boot/config/snap/snap.sh -listDeviceConfigurationInfo
-bash: cd: /boot/config/snap/snap.sh: Not a directory
root@Tower:~# snap.sh -listDeviceConfiguration
-bash: snap.sh: command not found
root@Tower:~# /boot/config/snap.sh -listDeviceConfigurationInfo
-bash: /boot/config/snap.sh: No such file or directory
root@Tower:~# cat /boot/config/snap/snap.list
cat: /boot/config/snap/snap.list: No such file or directory
root@Tower:~# cd /boot/config/snap
root@Tower:/boot/config/snap# dir
hotPlugAfterShareEvent.sh* snap.log* snapNotify.log*
inotify-tools-3.8-i486-1.tgz* snap.sh* snapNotify.sh*
snap-global-template* snapEvents.sh* snapSambaNotify.log*
snap-xdrive-template* snapEventss.log* snapSambaNotify.sh*
root@Tower:/boot/config/snap# cd /boot
root@Tower:/boot# cd ..
root@Tower:/# /boot/config/snap# snap.sh -listDeviceConfigurationInfo
-bash: /boot/config/snap#: No such file or directory
root@Tower:/# cd ..
root@Tower:/# /boot/config/snap.sh -listDeviceConfigurationInfo
-bash: /boot/config/snap.sh: No such file or directory
root@Tower:/# /boot/config/snap# snap.sh -listDeviceConfigurationInfo
-bash: /boot/config/snap#: No such file or directory
root@Tower:/# cd /boot/config/snap
root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration
root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration
I attached my syslog after my install on reboot, unfortunately I did not think to get the syslog before rebooting because I thought I had installed it correctly. I have read through the thread a few times,I'm not sure what to do from here. Did I screw something up when I installed at root@Tower:~#? I know the hard drive is seen by the system because I can pick it from the device assignment page. Thanks
-
in short
so i type in
snap.sh -a [1502825] [?]
or
snap.sh -a [WMAZA1502825] [?]
Don't put the [ and ] brackets when you use it. Those are used to illustrate that it's a parameter you provide but you shouldn't actually include them.
It would be helpful if you added this note to the front page. I'm a complete noob so I wasn't sure if the brackets were suppose to be there or not either. Just a suggestion. Now time to try and get this up and running on my machine.
Server Issues after having hard drive mounting problems in SNAP
in General Support (V5 and Older)
Posted
Thanks for the help. I'll run a memory test on it later today. I had done one just a few weeks ago and let it run for 24 hrs with no issues, so guess we will see if something has come up.