Samba not starting

[bnicu]

Hy,
I am using freenas 8.2-RELEASE-p3, and started to get some problems with the samba service:
/usr/sbin/service samba restart
Bus error
Bus error
Performing sanity check on Samba configuration: Bus error
FAILED

I have a raidz2 configuration, and it worked fine until yesterday.
Can this be a hardware issue?

 

[cyberjock]

It could be. Unfortunately, with only a Bus error message it's hard to pinpoint the exact cause. It could be any of a number of hardware issues as well as a software issue. Your best bet is to start running diagnostics on your hardware and hopefully you can determine the cause. If you cannot find a hardware problem, then you could try another USB key and a clean install and see if the error continues.

PS- FreeNAS 8.2 RELEASE p3 doesn't exist ;) There's a difference between FreeNAS version and FreeBSD version. FreeNAS is built on FreeBSD version 8.2p3.

 

[bnicu]

It could be. Unfortunately, with only a Bus error message it's hard to pinpoint the exact cause. It could be any of a number of hardware issues as well as a software issue. Your best bet is to start running diagnostics on your hardware and hopefully you can determine the cause. If you cannot find a hardware problem, then you could try another USB key and a clean install and see if the error continues.

PS- FreeNAS 8.2 RELEASE p3 doesn't exist ;) There's a difference between FreeNAS version and FreeBSD version. FreeNAS is built on FreeBSD version 8.2p3.

I have replaced the cables, and the stick that had the freenas installation and now it works. I am running a scrub now and it appears that some drives had some errors, but i guess i will move the files and then pray for no more.

pool: share
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
config:

NAME STATE READ WRITE CKSUM
share ONLINE 0 0 0
raidz2 ONLINE 0 0 0
gptid/9a4d59ba-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 8 256K repaired
gptid/9addfc0c-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 1 32K repaired
gptid/9b69cbd6-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 5 160K repaired
gptid/9bfb0efb-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 2 64K repaired
gptid/9c8b9454-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 0
gptid/9d19fb16-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 2 64K repaired

Is it possible that the motherboard or hdd's are to blame?

 

[cyberjock]

It's tough to identify the exact cause. Your best bet is just watch the computer for the next 2 weeks or so and see what weird stuff happens. Hopefully it was the USB key and/or the cables and the problem won't come back.

 

[bnicu]

It's tough to identify the exact cause. Your best bet is just watch the computer for the next 2 weeks or so and see what weird stuff happens. Hopefully it was the USB key and/or the cables and the problem won't come back.

Yep. Thank you. This is the finished scrub report, just in case:
scrub: scrub completed after 1h45m with 13 errors on Mon Jul 30 09:02:46 2012
config:

NAME STATE READ WRITE CKSUM
share ONLINE 0 0 13
raidz2 ONLINE 0 0 26
gptid/9a4d59ba-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 342 10.7M repaired
gptid/9addfc0c-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 114 3.56M repaired
gptid/9b69cbd6-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 174 5.38M repaired
gptid/9bfb0efb-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 212 6.62M repaired
gptid/9c8b9454-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 160 5M repaired
gptid/9d19fb16-6b5f-11e1-8c04-5404a6859e3d ONLINE 0 0 130 4.06M repaired

as long as it says repaired...

 

[cyberjock]

I'd do another scrub in 2 weeks if you get no other errors. If you get no errors (repaired is fine) then I'd say the system is fine and you fixed the problem. It could have just been a lose cable. :P