|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
save entropy problem
I'm running FreeBSD 7.0-p6 and over the weekend I received lots of messages from my server with the following content:
Code:
Cron <operator@paistram> /usr/libexec/save-entropy unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.3: No such file or directory mv: /var/db/entropy/saved-entropy.2: No such file or directory I'm using a 3ware 9500S-4LP RAID controller card in a 4 disk RAID 5 configuration. I'm also getting a lot of these errors on my nightly backup: Code:
Aug 30 06:00:35 paistram kernel: umass0: BBB reset failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB reset failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB reset failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB reset failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB reset failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[READ(offset=18432, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3151872, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3155968, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdodsfes/gCeOtR(S)A:I Rp[cWbRmIaTpE (rofeftsuertn=ed 316500 Aug 30 06:20:23 paistram kernel: 64, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3164160, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3168256, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3172352, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3176448, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3180544, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3184640, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3188736, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3192832, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3196928, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=3201024, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=11033600, length=4096)]error = 5 Aug 30 06:20:23 paistram kernel: g_vfs_done():msdosfs/CORSAIR[WRITE(offset=11037696, length=4096)]error = 5 This leads me to believe that the error is due to a faulty USB drive. Could this be the problem? I run a backup script to write a backup tar file to a USB drive every night (which is rotated). On Fridays we use the same USB for Fri, Sat & Sun. So maybe this USB drive has just died. |
|
||||
There does seem to be a faulty USB drive or USB port, but this shouldn't interfere with normal system operation unless a system partition (i.e. /var/) is mounted on it.
Your hard reset was probably the cause though, files may have been lost. One advice found through google: http://unix.derkeiler.com/Mailing-Li.../msg00322.html So make sure /var/db/entropy/ exists, clean out the contents.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PLEASE HELP SAVE BSD MAGAZINE | Kruzer | Off-Topic | 14 | 27th August 2009 05:10 PM |
how to save stackoverflow podcasts? | ephemera | Off-Topic | 4 | 19th July 2009 03:32 PM |
Doing a fresh install - what to save? | Bruco | FreeBSD General | 4 | 30th May 2009 01:49 PM |
Savemail panic, cannot save rejected email anywhere | Mantazz | FreeBSD Ports and Packages | 12 | 11th January 2009 03:03 AM |
Firefox PROTIP: getting back to a normal Save As Dialogue. | caesius | Guides | 5 | 15th October 2008 06:24 AM |