| 1 |
On 27 October 2015 17:36:00 CET, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
>On Tuesday 27 October 2015 15:16:26 J. Roeleveld wrote: |
| 3 |
> |
| 4 |
>> If a disk is umounted/removed, something needs to be logged |
| 5 |
>somewhere. |
| 6 |
>> Might even be a comment from the scsi-subsystem or the SATA driver. |
| 7 |
>> |
| 8 |
>> I usually only grep the log to try to find specific messages. |
| 9 |
>> If I know the time-period something weird happened in, I tend to go |
| 10 |
>through |
| 11 |
>> the unfiltered log for that period. |
| 12 |
> |
| 13 |
>I have been scanning dmesg and /var/log/messages by eye and not noticed |
| 14 |
> |
| 15 |
>anything. I'll keep doing it though. |
| 16 |
|
| 17 |
What does your fstab look like? |
| 18 |
|
| 19 |
And maybe some more info, like which kernel version. Mount version. |
| 20 |
And maybe check for some weird crontab entry somewhere? |
| 21 |
|
| 22 |
You could also rule out the use of umount by replacing it with a wrapper script that logs every call with as much info as is possible? |
| 23 |
|
| 24 |
-- |
| 25 |
Joost |
| 26 |
-- |
| 27 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives