Weblog entry #27 for Grimnar
See all weblog entries made by Grimnar.
Every time I do reboot, a random disk goes away. I got 3 mounted pluss my /dev/hda wich has my system on. Yesterday /dev/hdb was gone and now /dev/hdf is gone. But /dev/hdb is back in buisness. My setup has worked great for about 4 years now. Of course I have done some reinstall and such but it has been working flawlessy.
Samba is strange, cannot log in. proftpd gives me the same. (All failed when trying to start during boot). When a local user is trying to use screen, all I/he/she gets is: Directory '/var/run/screen' must have mode 777.
uh? So, what the hell is going on?
In my /var/log/samba there is a bunch of logs wich I never seen before. Very strange.
log.59.95.174.72 log.85.220.29.22 log.smbd.7.gz
log.59.95.179.66 log.85.220.30.225 log.softs
log.59.95.25.148 log.85.220.32.100 log.solberg
log.59.95.28.63 log.85.220.33.163 log.spacemachine
log.59.96.155.103 log.85.220.33.53 log.srv2000
log.60.161.14.59 log.85.220.36.210 log.srvvb
log.60.21.34.158 log.85.220.36.223 log.station4
log.60.237.165.105 log.85.220.42.66 log.sten
log.60.41.152.68 log.85.220.44.68 log.stiga
log.60.50.63.182 log.85.220.47.155 log.stokkes
On my mac Im used to run a app called onyx, wich will fix all the permissions on the system. Is there any program that will do the same on debian?
Comments on this Entry
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Those logfiles look normal, perhaps caused by a change to your samba configuration file - basically they are logs for each machine connecting to your server. Usually they are disabled though.
As for permissions - there isn't a standard tool to fix them up. Nor should they change randomly.
With drives disappearing/reappearing I'd be tempted to say you have a pending drive failure, or other hardware problem.
Run dmesg and look for disk errors with something like this:
dmesg |grep hd
[ Parent | Reply to this comment ]
[ Send Message | View dkg's Scratchpad | View Weblogs ]
It's also possible that your kernel modules are being loaded in unusual orders upon reboot, which means that the devices themselves could be renamed (e.g. /dev/hda becomes /dev/hde). Are you mounting your partitions by disk name or by filesystem UUID or label?
[ Parent | Reply to this comment ]
Two disks are connected through a addon pci-card. No raid. Maybe I should try a different 1) Pci-slot or a different "port" on the pci-card. See what happens.
About the samba logs, this is the first time for it logs other computers. And that said, I all the sudden see other computers on my lan as well. Never seen that before. So maybe that happend on the last samba update?
I will check out smartmontools right now, see if that can tell me something.
Recently I have been hearing high pitched noice from my disks. Not very good:(
This is my /etc/fstab
#
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda2 /mnt/opt1 ext3 defaults,errors=remount-ro 0 1
/dev/hdb5 /mnt/opt2 ext3 defaults,errors=remount-ro 0 1
/dev/hde /mnt/opt3 ext3 defaults,errors=remount-ro 0 1
/dev/hdf /mnt/opt4 ext3 defaults,errors=remount-ro 0 1
/dev/hdb6 none swap sw 0 0
#/dev/sdb1 /mnt/western ext3 auto user,noauto 0 0
[ Parent | Reply to this comment ]
[ Send Message | View dkg's Scratchpad | View Weblogs ]
to run a bunch of short tests on all your disks, just do:
for disk in /dev/hd? ; do smartctl -t short "$disk" doneThere should be some messages printed about what time you should expect the tests to complete. once the tests have completed (probably 5 minutes max for most short tests, but depends on the disks), you can read the info with:
for disk in /dev/hd? ; do
echo "===${disk}==="
smartctl -a "$disk"
done > diskreports.txt You should then be able to read the diskreports.txt file to see what the disks have to say for themselves. For a single disk, of course, the commands are even simpler:
smartctl -t short /dev/hdX ## wait until the suggested time smartctl -a /dev/hdXBy the way, you should only have one line in /etc/fstab with the last field set to 1. From fstab(5):
The sixth field, (fs_passno), is used by the fsck(8) program to deter�
mine the order in which filesystem checks are done at reboot time. The
root filesystem should be specified with a fs_passno of 1, and other
filesystems should have a fs_passno of 2. Filesystems within a drive
will be checked sequentially, but filesystems on different drives will
be checked at the same time to utilize parallelism available in the
hardware. If the sixth field is not present or zero, a value of zero
is returned and fsck will assume that the filesystem does not need to
be checked.
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
/dev/hda
http://pastebin.com/m6bccea2b
/dev/hdb
http://pastebin.com/m23be724c
During boot, I noticed the disks wich im missing are located by the ide-controller
(Promise PDC220268 Ultra100 TX2 V2.20.0.15) but when they are supposed to be mountet they do not exist.
[ Parent | Reply to this comment ]
I took my system down and rearranged the disks from IDE 1 on the pci IDE-controller too IDE 2. Now the disks are here! muhaha. /dev/hdh and /dev/hdg
Maybe I should run some tests on them as well. Before I brake anything!
[ Parent | Reply to this comment ]
/dev/hdh
http://pastebin.com/m314738a0
/dev/hdg
http://pastebin.com/m3155e44d
[ Parent | Reply to this comment ]
The PCI card I'm using uses the CMD648 driver, and previously I would sometimes have to type 'mount /dev/hde1' and 'mount /dev/hdf1' after a reboot or power on.
I changed my entry for hde1 and hdf1 to 2 and 3 respectively, and has always mounted on reboot since. They originally were set to 0.
linux:~ # cat /etc/fstab
/dev/hda2 / reiserfs acl,user_xattr 1 1
/dev/hda1 swap swap pri=42 0 0
/dev/hde1 /srv/ftp/pub auto auto 0 2
/dev/hdf1 /srv/ftp/dvd auto auto 0 3
[ Parent | Reply to this comment ]