Final result: After a remote debug session in the chat, including the poweroff of his spinning hdd, was made clear that not his hdd is spinning, but the ventillator of his nvidia card.
Problem was solved after installing the nVidia driver.
Extension: jbd2 means a kernel-based background task doing side-work on one of your linux filesystems, it surely doesn't do anything to your win partitions. More you can read about it here.
This is obviously extraordinary case - if you don't use your ubuntu, it shouldn't spin your disk. There is some background process, which may not be needed (or it is, but then is it a good question, what it does).
However, fortunately there is an easy and also a more complex way to hunt this problem down.
- Processes doing IO-intensive things are typically on the
top. So, type: top, and check what is on the top. Look for processes having the R (=running) state in the in the S(tate) column. Also you can use the ps uxa|grep R as a purely command-line solution for the same task. Although the top orders the processes by their cpu usage, and not by their I/O, in most cases also the I/O intensive processes are going into the top in the top, as a side-effect.
- There is a tool named blkiomon. Its parametrization is highly un-trivial, but you can get a much more direct info with it, who is spinning your disks and why.
The most probable causes of your problem are these:
- Some website is doing some nasty in a rarely visited chrome tab.
- You have not too many RAM and use some app using a lot. In this case, the cause of the spinning is the swap.
- If it is your Chrome (what may be also because (1) ), then you may consider switching to firefox with turned off electrolysis. It is the fastest possible way to have an useful browser with few RAM. The typical RAM-need of an e10s-free 32-bit firefox is lesser than 1G.
To the comments:
Which partitions are mounted and where, that you can check with the mount command. Unfortunately, it is filled with crap since some years, but to the end, you can see the list. Search for the lines like this:
/dev/sda7 on /media/archive type ext4 (rw,relatime,nobarrier,errors=remount-ro,commit=6935,data=ordered)
This means, that your /dev/sda7 is mounted into the directory /media/archive. Sda7 is the 7th partition of your first hard disk.
Extension: As your fdisk output shows, your SSD is your /dev/sdb1.