System freeze after adding second HDD

[mihajzm]

Hello,

on bought new HDD and installed latest snapshot LinuxMCE-8.10-23261 (before I was running the 7.10 version).
All was installed and running without problems. As all my data was on the old HDD, I have connected
it to the system. On Orbiter I selected to use it without LinuxMCE structure (only show files). Everything seemed to be OK. But after a while the system freezes. I though the power supply is not enough. Therefore I replaced it with new 500W ATX Power Supply. But the situation was the same. Then I examined the logs an found that the HDD is mounted several times till the system freeze.

What can I do with it?

Here is the log before the system freeze.

Sep 25 13:50:47 dcerouter kernel: [   84.023315] Bluetooth: Core ver 2.13
Sep 25 13:50:47 dcerouter kernel: [   84.026961] NET: Registered protocol family 31
Sep 25 13:50:47 dcerouter kernel: [   84.026973] Bluetooth: HCI device and connection manager initialized
Sep 25 13:50:47 dcerouter kernel: [   84.026981] Bluetooth: HCI socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.088034] Bluetooth: L2CAP ver 2.11
Sep 25 13:50:47 dcerouter kernel: [   84.088044] Bluetooth: L2CAP socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.143563] Bluetooth: RFCOMM socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.144163] Bluetooth: RFCOMM TTY layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.144178] Bluetooth: RFCOMM ver 1.10
Sep 25 13:50:47 dcerouter kernel: [   84.147535] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 25 13:50:47 dcerouter kernel: [   84.147548] Bluetooth: BNEP filters: protocol multicast
Sep 25 13:50:47 dcerouter kernel: [   84.226954] Bridge firewalling registered
Sep 25 13:50:47 dcerouter kernel: [   84.283001] Bluetooth: SCO (Voice Link) ver 0.6
Sep 25 13:50:47 dcerouter kernel: [   84.283014] Bluetooth: SCO socket layer initialized
Sep 25 13:50:47 dcerouter kernel: [   84.712130] NET: Registered protocol family 17
Sep 25 13:51:03 dcerouter kernel: [  100.568060] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:03 dcerouter kernel: [  100.576658] EXT3 FS on sdb1, internal journal
Sep 25 13:51:03 dcerouter kernel: [  100.576675] EXT3-fs: recovery complete.
Sep 25 13:51:03 dcerouter kernel: [  100.577481] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:51:42 dcerouter kernel: [  139.606754] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:42 dcerouter kernel: [  139.608577] EXT3 FS on sdb1, internal journal
Sep 25 13:51:42 dcerouter kernel: [  139.608599] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:51:46 dcerouter kernel: [  143.477474] kjournald starting.  Commit interval 5 seconds
Sep 25 13:51:46 dcerouter kernel: [  143.479190] EXT3 FS on sdb1, internal journal
Sep 25 13:51:46 dcerouter kernel: [  143.480098] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:52:52 dcerouter kernel: [  209.358722] kjournald starting.  Commit interval 5 seconds
Sep 25 13:52:52 dcerouter kernel: [  209.360905] EXT3 FS on sdb1, internal journal
Sep 25 13:52:52 dcerouter kernel: [  209.361960] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:52:58 dcerouter kernel: [  215.489889] kjournald starting.  Commit interval 5 seconds
Sep 25 13:52:58 dcerouter kernel: [  215.491557] EXT3 FS on sdb1, internal journal
Sep 25 13:52:58 dcerouter kernel: [  215.492472] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:56:06 dcerouter kernel: [  402.983011] kjournald starting.  Commit interval 5 seconds
Sep 25 13:56:06 dcerouter kernel: [  402.984808] EXT3 FS on sdb1, internal journal
Sep 25 13:56:06 dcerouter kernel: [  402.985690] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:56:39 dcerouter kernel: [  435.874535] kjournald starting.  Commit interval 5 seconds
Sep 25 13:56:39 dcerouter kernel: [  435.876286] EXT3 FS on sdb1, internal journal
Sep 25 13:56:39 dcerouter kernel: [  435.877164] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:57:27 dcerouter kernel: [  484.025657] kjournald starting.  Commit interval 5 seconds
Sep 25 13:57:27 dcerouter kernel: [  484.027377] EXT3 FS on sdb1, internal journal
Sep 25 13:57:27 dcerouter kernel: [  484.028627] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 13:58:00 dcerouter kernel: [  517.532721] kjournald starting.  Commit interval 5 seconds
Sep 25 13:58:00 dcerouter kernel: [  517.534426] EXT3 FS on sdb1, internal journal
Sep 25 13:58:00 dcerouter kernel: [  517.535304] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:00:42 dcerouter kernel: [  679.085509] kjournald starting.  Commit interval 5 seconds
Sep 25 14:00:42 dcerouter kernel: [  679.087292] EXT3 FS on sdb1, internal journal
Sep 25 14:00:42 dcerouter kernel: [  679.088207] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:02:18 dcerouter kernel: [  775.677016] kjournald starting.  Commit interval 5 seconds
Sep 25 14:02:18 dcerouter kernel: [  775.679203] EXT3 FS on sdb1, internal journal
Sep 25 14:02:18 dcerouter kernel: [  775.680149] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:03:39 dcerouter kernel: [  856.277193] kjournald starting.  Commit interval 5 seconds
Sep 25 14:03:39 dcerouter kernel: [  856.278931] EXT3 FS on sdb1, internal journal
Sep 25 14:03:39 dcerouter kernel: [  856.279806] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:05:24 dcerouter kernel: [  960.863534] kjournald starting.  Commit interval 5 seconds
Sep 25 14:05:24 dcerouter kernel: [  960.865426] EXT3 FS on sdb1, internal journal
Sep 25 14:05:24 dcerouter kernel: [  960.866304] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:06:12 dcerouter kernel: [ 1009.312164] kjournald starting.  Commit interval 5 seconds
Sep 25 14:06:12 dcerouter kernel: [ 1009.313889] EXT3 FS on sdb1, internal journal
Sep 25 14:06:12 dcerouter kernel: [ 1009.314769] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:07:01 dcerouter kernel: [ 1058.135445] kjournald starting.  Commit interval 5 seconds
Sep 25 14:07:01 dcerouter kernel: [ 1058.137207] EXT3 FS on sdb1, internal journal
Sep 25 14:07:01 dcerouter kernel: [ 1058.138088] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:11:58 dcerouter kernel: [ 1355.339290] kjournald starting.  Commit interval 5 seconds
Sep 25 14:11:58 dcerouter kernel: [ 1355.341073] EXT3 FS on sdb1, internal journal
Sep 25 14:11:58 dcerouter kernel: [ 1355.341953] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:12:55 dcerouter kernel: [ 1411.865639] kjournald starting.  Commit interval 5 seconds
Sep 25 14:12:55 dcerouter kernel: [ 1411.867363] EXT3 FS on sdb1, internal journal
Sep 25 14:12:55 dcerouter kernel: [ 1411.868264] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:14:24 dcerouter kernel: [ 1500.876184] kjournald starting.  Commit interval 5 seconds
Sep 25 14:14:24 dcerouter kernel: [ 1500.878034] EXT3 FS on sdb1, internal journal
Sep 25 14:14:24 dcerouter kernel: [ 1500.878899] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:15:28 dcerouter kernel: [ 1565.538548] kjournald starting.  Commit interval 5 seconds
Sep 25 14:15:28 dcerouter kernel: [ 1565.540691] EXT3 FS on sdb1, internal journal
Sep 25 14:15:28 dcerouter kernel: [ 1565.541574] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:16:00 dcerouter kernel: [ 1597.475716] kjournald starting.  Commit interval 5 seconds
Sep 25 14:16:00 dcerouter kernel: [ 1597.477449] EXT3 FS on sdb1, internal journal
Sep 25 14:16:00 dcerouter kernel: [ 1597.478330] EXT3-fs: mounted filesystem with ordered data mode.
Sep 25 14:19:29 dcerouter kernel: [ 1806.240143] kjournald starting.  Commit interval 5 seconds
Sep 25 14:19:29 dcerouter kernel: [ 1806.242025] EXT3 FS on sdb1, internal journal
Sep 25 14:19:29 dcerouter kernel: [ 1806.242906] EXT3-fs: mounted filesystem with ordered data mode.

[mihajzm]

Some progress:

I have disabled Pluto Automounter  (New Automounter Filesystem (autofs) - /etc/auto.PlutoStorageDevices).
Then I have added line to fstab to mount the second drive at boot.

Now the system works without hang-up (freezing)

What can be issue. It's not HW related. The Automounter mount the drive in endless loop till the system hangs-up.

[tschak909]

AAARRRGGGGHHHH!!!!!!

*thwap-mihajzm-hard*

You are not supposed to disable the automounter at all, and will lose a number of features as a result.

Believe it or not, what you are seeing in the system logs is expected behaviour. The system will dynamically mount and unmount the drive as needed.

-Thom

[mihajzm]

I know that, but I was hopeless. When let the automounter to do it's work and add second HDD, the system hangs-up in about 20-30 minutes.
When I have used the 7.10 version (on the same HW) I have not such a problem. At now I let it so, I cannot afford to restart the whole system every hour.