IRC log for #gllug on 20170117

08:09.38yaMattif it acts differently between ext4 and NTFS that says to me it's not a hardware thing, it's something about your machines configuration
08:10.56DSkiWell, I have a 3TB SATA drive, formatted with gpt and EXT5 and works fine, but the USB 4TB acting as I describe. Could it be a motherboard problem or software?
09:16.26yaMattext5?!
09:16.51yaMattmy feeling is it's software
09:17.02DSkiEXT4 (a typo)
09:17.24DSkiOK, I will raise a ticket with the distro I use to look into it.
09:18.39DSkiYou don't think it's related to capacity? I don't want to get a 4TB+ new HDD for SATA and for it to be effectively, an expensive brick.
09:19.11yaMattiirc ext4 supports up to something like 16PB
09:19.24DSkiOK
09:20.04yaMattah, 16TB (depending on block size)
09:20.28yaMattthe only thing I can think of is ext considers the disk unsafe for some reason and is mounting it as read-only
09:20.44yaMattthere's probably some output in journalctl or dmesg depending on your setup
09:21.09DSkiThe external drive has a sort of workaround, it formats to owner as root, so change owner to the user, which allows writing to it, but it is still being constantly hammered as if it's a BluRay (large device according to syslog)
09:23.40yaMatthammered? so constantly seeking?
09:24.21DSkiYes, the access light on teh USB3 drive is constantly lashing ergo constant access.
09:24.34DSkiEven though it's supposed to be idling.
09:26.12yaMattthat is really weird, it sounds like the machine thinks the disk is faulty
09:26.51DSkiIt sound;t be faulty, it's brand new.
09:27.16DSkiShould I take it out if the enclosure and try the disk that way?
09:27.55DSkiMeans I invaidate any warranty
09:28.32yaMattearly failures are common
09:28.41DSkiok
09:28.50yaMattif it is faulty then taking it out of the case is the worst thing to do
09:28.52DSkiI've never had an early failure.
09:29.04yaMattI would try a different machine if possible
09:29.19DSkiOK, will try that. :)
09:29.29yaMattjust to exclude that machine from having some weird configuration issue
09:29.35yaMattsomething ideally with a different distro
09:29.56DSkiIt#s jsut very strange because it seems to be working normal when formatted to NTFS, but dosn't like Linux formats
09:32.48yaMattNTFS support has come a long way on Linux, but I don't think it's complete, it may be hiding the issues that ext can detect
09:33.17yaMattit's quite common for a disk to be mounted read-only if it doesn't like the reliability of it
09:33.38yaMattI saw it with a colleagues SSD after he read and wrote millions of tiny files to disk
09:33.45yaMattit would only mount read-only
09:37.44DSkiOK
09:38.00DSkiI will investigate the USB drive further.
09:39.23DSkiSSD, I always worry about that, I have read the horror stories of drive not working suddenly, I have an SSD for the OS only.
09:40.16DSki2min for boot to Linux login screen in HDD, 15 seconds with SSD. Massive difference.
09:47.20wethrinYeah, don't use SSDs for things where there's lots of small writes to the drive (logging systems, f'rexample)
09:51.33DSkiI made sure to prevent a TMP fpartition from being used on the SSD, don't want to wear out the drive
10:00.09yaMattI use SSD pretty much everywhere
10:00.21yaMattthe only failure I've seen was that guy who was writing millions of files
10:01.08yaMattthough I hear a lot of horror stories about SSDs that just stop working, unlike spinning rust that fails a bit
10:01.58yaMattbut I back up all my devices to my NAS
10:07.06yaMattalthough I checked on my desktop yesterday and it said the last backup was 2 weeks ago, it's supposed to run every day
10:07.09DSkiThe OS drive replacable, the data is not. :)
10:07.37DSkiI worry about the user data more.
10:07.48DSkiAt least SSD's ahve got cheaper in recent years.
10:08.31DSkiUsing an SSD for the OS is like night and day, very impressive speed.
10:09.32yaMattdefinitely
10:10.47yaMattI do need to put more disks in to my NAS
10:11.29yaMattan expensive hobby :)
10:11.48DSkiI wish I could afford a NAS, I swap out drives every so often instead.
10:11.57DSkiI agree, it's expensive.
11:03.52DSkiyaMatt, Tested the USB drive on another Linux machine, same problems, so a software problem, or the brand new drive has a problem.
11:05.21yaMattthat mwans you can rule out a software problem unless there's something common between the 2 systems
11:05.25yaMattmeans*
11:05.54DSkiWell, they are the same distro, just different machines, which is why I can't be 100% certain.
11:06.45yaMattah, right
11:06.46DSkiI resurrected an old machine for children to play on,saved me learning another Linux version, so quick install.
11:07.06yaMattdid you try looking in journalctl/dmesg?
11:08.04DSkiOn my normal work machine yes, not on the machine I jsut tested on, should I look at it on the old machine?
11:09.21yaMattna, just the first one is fine
11:09.24yaMattwhat did it say?
11:12.41DSkiWhat syslog says is in this pastebin, same text every time the drive is connected. > http://pastebin.com/WX2sei3u
11:15.09yaMattnothing wrong there
11:15.16yaMattlooks like it should just be readable at /run/media/someuser/TestDrive
11:15.28yaMattand writable
11:16.18yaMattwhat does running the mount command say?
11:17.35DSkiAs it is being used by "someuser" the drive should not be constantly accessed light? None of my other USB3 (slammer capacity) drives have the access light on off even though you're not moving files around.
11:19.53DSkiThis is what it looks like with NTFS formatted on the same drive. http://pastebin.com/HMZhFnVV
11:20.59yaMattsimilarly looks fine, I wonder if it's just the light on the front looks like that
11:21.21yaMattI found this page on how to look at disk io https://unix.stackexchange.com/questions/55212/how-can-i-monitor-disk-io
11:22.22DSkiWhen I copied stuff under NTFS format to test, the drive didn't constantly have the light blinking, suggesting it wasn't being constantly accessed when not being used.
11:22.27DSkiIt's baffling,
11:22.33yaMattah, yes, you said
11:23.13yaMattlooks like you need to run 'iostat -x 1' (without '), you may need to install iostat
11:24.10DSkiOK, will do that later today, need to do some work :)
11:24.31DSkiBTW, do you know how to save these conversations texts in "Konversation"?
11:28.41yaMattI'm afraid I've not used Konversation before
11:29.03DSkiOK, no problem.
11:45.23DSkiInstalled package to get iostat to work.
11:46.23DSkiResult of the iostat in this pastebin, the suspect USB3 drive is sde > http://pastebin.com/TF94wvwj
11:56.01yaMattdoes look pretty active to me
11:57.47DSkiSame kind of activity on both computers I jsut tested the drive on.
11:58.40yaMattI wonder if it's ext4 still formatting the disk
11:58.50yaMattwould be useful to see what processes are accessing the disk
11:58.57yaMattcan't find a good tool for it though
12:02.15yaMattcould try the unix part of stackoverflow
12:05.50DSkiI'm not as knwledgable on the ins and outs of Linux.
12:07.11yaMattI mean, I really don't know I'm afraid, I would recommend posting your problem to https://unix.stackexchange.com/
12:07.43DSkiOK, I will give that a try.
12:07.52DSkiThanks for all your help.
12:09.11yaMattno problem, I hope you find a solution
12:10.18DSkiSometimes there are Linux issues that get to you, although hsving used WIndows in the past, that wasn't any better - especially as it is locked down / propiatory.
12:11.18yaMattI find it rare that linux does something without telling you something
12:11.30yaMattime Windows does that a lot
12:12.53DSkiThat is true, you can find out a LOT of what is going on in Linux by looking at /proc :) ....... can't do that in Windows. And upgrading hard drives is a TONNE easier in Linux, no stupid shifting of drive letters and everything breaking because of it.
13:04.38*** join/#gllug bencevans (~quassel@2001:bc8:4400:2100::b:f0d)
13:04.55*** join/#gllug yaMatt (~yaMatt@copperwaite.net)
13:53.56*** join/#gllug Leeds (~Leeds@42-3-157-207.static.netvigator.com)
14:20.41*** join/#gllug ChoHag (~mking@punctual.borderer.volia.net)
22:42.58*** join/#gllug mindbendr (~neveragai@bourbon.biscuit.org.uk)
23:18.09*** join/#gllug Leeds (~Leeds@42-3-157-207.static.netvigator.com)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.