PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000100)

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000100)

Postby Palmore » Sun Sep 14, 2014 8:09 pm

I just got ArchLinux running on my PogoPlug Series 4 POGO-V4-A3-01

I tossed NTFS-3g, Samba4, udevil and webmin on the box, everything is working great.

I have a Seagate 3TB Expansion drive hooked up, formatted NTFS.
This drive is accessible, its shared out via smb, everything is great in the world.

I plugged in my 5TB Expansion drive (also formated NTFS) and shortly after the pogoplug becomes unresponsive.

If I boot up with the 5TB plugged in, I get ping replies from it briefly as it boots but it shortly becomes unresponsive.
If I boot up with OUT it plugged in, everything is great, until 5-10 seconds after I plug in the 5TB drive (I'm assuming as udevil tries to auto-mount the disk)

The disk has been plugged into a Windows box for the past 2 weeks with no issues, I plugged it back in, ran chkdsk with no errors.

I'm still wet behind the ears when it comes to linux, I know enough to be dangerous and thats it.

What logs can I check and what could be causing this?

Any assistance is greatly appreciated.

Thank you.
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Mon Sep 15, 2014 2:05 am

Just an update as I try and trouble shoot this.

I dual boot Ubuntu on my laptop, so I booted up and made sure I could see the disk and access data in a flavor of *nix with out it crashing the system. I was able to access the drive and see data.

I noticed the disk was MBR even though it was a 5TB partition, so I dug up Paragon Partition Manager and converted the partition to a GPT partition, made sure I could still see and access my data in Windows and rushed the drive back to my Pogoplug, hooked it up, and about 30 seconds after the pogoplug stops responding to pings.

/var/log contains nothing of use sadly, as in its logging hardly anything.

Is it possible to turn on verbosity of udevil or arch linux itself to see whats going on?

Thank you
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby moonman » Mon Sep 15, 2014 7:19 am

Try a 32-bit linux on your pc and see if your 5TB works there. If it works then i dunno. I have no 5TB volume to test. Might be the time to switch to ext filesystem.

Try disabling udevil, open up 2 ssh sessions. In one watch your dmesg
$this->bbcode_second_pass_code('', 'watch -n 1 'dmesg | tail'')

In the other mount the drive manually.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Mon Sep 15, 2014 2:20 pm

I will give that a try tonight, is there a quick way to disable udevil and keep it from auto-mounting during my testing?

I did try plugging the drive into my Patriot Memory Javelin S4 (it crashed the device with in 10 minutes and would not boot back up with it plugged in)

So then I plugged it into my vSphere 5.1 box, pushed it through USB pass-thru to a Windows VM, and shortly after the ESX host became unresponsive (but the VMs continued to run, it just crashed the management agents)

But again, I tested with 2 Windows 8.1 desktops, 1 Windows 8.1 Laptop and Ubunutu 14 on my Laptop and not an issue lol

I will test tonight and let you know what I find.
Thank you very much
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby WarheadsSE » Mon Sep 15, 2014 5:17 pm

vs watch dmesg | tail, I might suggest ` journalctl -f `
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Mon Sep 15, 2014 6:55 pm

If I am assuming correct

systemctl stop devmon@root.service

will kill the udevil service and stop auto mounting of disks

I will try 3 SSH sessions
1 - watch -n 1 'dmesg | tail'
2 - journalctl -f
3 - Manually mount the 5TB disk


If there is no joy, looks like I'll have to find 5TB of space on my network and move everything off the disk and re-format EXT3. Thats not going to be fun lol.

I will update tonight once I get a chance to do some testing and hopefully pull some logs.

Thank you all very much for your input and assistance.
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Tue Sep 16, 2014 1:02 am

Ok, here are my logs

dmesg
$this->bbcode_second_pass_code('', 'Every 1.0s: dmesg | tail Mon Sep 15 20:34:43 2014

[81529.724549] [<c0009db0>] (handle_IRQ) from [<c0531258>] (__irq_usr+0x38/0xa0)
[81529.731656] ---[ end trace 2f8ee2277200441d ]---
[81529.737040] scsi 3:0:0:0: Direct-Access Seagate Expansion Desk 0739 PQ
: 0 ANSI: 6
[81529.764513] sd 3:0:0:0: [sdc] Spinning up disk...
[81529.770497] sd 3:0:0:0: Attached scsi generic sg2 type 0
[81535.229534] .........ready
[81543.311433] sd 3:0:0:0: [sdc] 1220942645 4096-byte logical blocks: (5.00 TB/4
.54 TiB)
[81543.320146] sd 3:0:0:0: [sdc] Write Protect is off
[81543.334094] sd 3:0:0:0: [sdc] Mode Sense: 2b 00 10 08
[81543.338917] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supp
orts DPO and FUA')

journalctl -f
$this->bbcode_second_pass_code('', '[root@plug01 ~]# journalctl -f
-- Logs begin at Wed 1969-12-31 19:00:06 EST. --
Sep 15 20:28:49 plug01 sshd[8639]: Accepted password for root from 10.0.0.199 port 57151 ssh2
Sep 15 20:28:49 plug01 sshd[8639]: pam_unix(sshd:session): session opened for user root by (uid=0)
Sep 15 20:28:49 plug01 systemd-logind[131]: New session c3 of user root.
Sep 15 20:28:49 plug01 systemd[1]: Starting Session c3 of user root.
Sep 15 20:28:49 plug01 systemd[1]: Started Session c3 of user root.
Sep 15 20:30:47 plug01 sshd[8679]: Accepted password for root from 10.0.0.199 port 57324 ssh2
Sep 15 20:30:47 plug01 sshd[8679]: pam_unix(sshd:session): session opened for user root by (uid=0)
Sep 15 20:30:47 plug01 systemd-logind[131]: New session c4 of user root.
Sep 15 20:30:47 plug01 systemd[1]: Starting Session c4 of user root.
Sep 15 20:30:47 plug01 systemd[1]: Started Session c4 of user root.
Sep 15 20:33:59 plug01 kernel: usb 3-2: new SuperSpeed USB device number 3 using xhci_hcd
Sep 15 20:34:00 plug01 kernel: scsi3 : uas
Sep 15 20:34:00 plug01 kernel: ------------[ cut here ]------------
Sep 15 20:34:00 plug01 kernel: WARNING: CPU: 0 PID: 21 at drivers/usb/storage/uas.c:625 uas_submit_urbs.constprop.23+0x560/0x59c [uas]()
Sep 15 20:34:00 plug01 kernel: Modules linked in: uas mv_cesa ipv6
Sep 15 20:34:00 plug01 kernel: CPU: 0 PID: 21 Comm: khubd Not tainted 3.16.2-1-ARCH #1
Sep 15 20:34:00 plug01 kernel: [<c000f040>] (unwind_backtrace) from [<c000c588>] (show_stack+0x10/0x14)
Sep 15 20:34:00 plug01 kernel: [<c000c588>] (show_stack) from [<c001b7bc>] (warn_slowpath_common+0x70/0x90)
Sep 15 20:34:00 plug01 kernel: [<c001b7bc>] (warn_slowpath_common) from [<c001b878>] (warn_slowpath_null+0x1c/0x24)
Sep 15 20:34:00 plug01 kernel: [<c001b878>] (warn_slowpath_null) from [<bf06d1e8>] (uas_submit_urbs.constprop.23+0x560/0x59c [uas])
Sep 15 20:34:00 plug01 kernel: [<bf06d1e8>] (uas_submit_urbs.constprop.23 [uas]) from [<bf06d390>] (uas_queuecommand+0x16c/0x22c [uas])
Sep 15 20:34:00 plug01 kernel: [<bf06d390>] (uas_queuecommand [uas]) from [<c0365eec>] (scsi_dispatch_cmd+0x98/0x230)
Sep 15 20:34:00 plug01 kernel: [<c0365eec>] (scsi_dispatch_cmd) from [<c036d0fc>] (scsi_request_fn+0x2e4/0x514)
Sep 15 20:34:00 plug01 kernel: [<c036d0fc>] (scsi_request_fn) from [<c02a6874>] (__blk_run_queue+0x34/0x44)
Sep 15 20:34:00 plug01 kernel: [<c02a6874>] (__blk_run_queue) from [<c02ae198>] (blk_execute_rq_nowait+0xa0/0x148)
Sep 15 20:34:00 plug01 kernel: [<c02ae198>] (blk_execute_rq_nowait) from [<c02ae298>] (blk_execute_rq+0x58/0xe4)
Sep 15 20:34:00 plug01 kernel: [<c02ae298>] (blk_execute_rq) from [<c036b668>] (scsi_execute+0xb8/0x138)
Sep 15 20:34:00 plug01 kernel: [<c036b668>] (scsi_execute) from [<c036b76c>] (scsi_execute_req_flags+0x84/0xf8)
Sep 15 20:34:00 plug01 kernel: [<c036b76c>] (scsi_execute_req_flags) from [<c036eb00>] (scsi_probe_and_add_lun+0x178/0x9c8)
Sep 15 20:34:00 plug01 kernel: [<c036eb00>] (scsi_probe_and_add_lun) from [<c036f734>] (__scsi_scan_target+0xdc/0x564)
Sep 15 20:34:00 plug01 kernel: [<c036f734>] (__scsi_scan_target) from [<c036fe38>] (scsi_scan_host_selected+0x108/0x1dc)
Sep 15 20:34:00 plug01 kernel: [<c036fe38>] (scsi_scan_host_selected) from [<c036ff90>] (do_scsi_scan_host+0x84/0x8c)
Sep 15 20:34:00 plug01 kernel: [<c036ff90>] (do_scsi_scan_host) from [<c0370110>] (scsi_scan_host+0x178/0x1e0)
Sep 15 20:34:00 plug01 kernel: [<c0370110>] (scsi_scan_host) from [<bf06c4a8>] (uas_probe+0x278/0x2a8 [uas])
Sep 15 20:34:00 plug01 kernel: [<bf06c4a8>] (uas_probe [uas]) from [<c03ec0d0>] (usb_probe_interface+0x16c/0x21c)
Sep 15 20:34:00 plug01 kernel: [<c03ec0d0>] (usb_probe_interface) from [<c034825c>] (driver_probe_device+0x110/0x244)
Sep 15 20:34:00 plug01 kernel: [<c034825c>] (driver_probe_device) from [<c0346934>] (bus_for_each_drv+0x5c/0x8c)
Sep 15 20:34:00 plug01 kernel: [<c0346934>] (bus_for_each_drv) from [<c0348118>] (device_attach+0x70/0x88)
Sep 15 20:34:00 plug01 kernel: [<c0348118>] (device_attach) from [<c0347800>] (bus_probe_device+0x84/0xb0)
Sep 15 20:34:00 plug01 kernel: [<c0347800>] (bus_probe_device) from [<c0345cac>] (device_add+0x420/0x51c)
Sep 15 20:34:00 plug01 kernel: [<c0345cac>] (device_add) from [<c03ea234>] (usb_set_configuration+0x540/0x774)
Sep 15 20:34:00 plug01 kernel: [<c03ea234>] (usb_set_configuration) from [<c03f36c0>] (generic_probe+0x2c/0x78)
Sep 15 20:34:00 plug01 kernel: [<c03f36c0>] (generic_probe) from [<c03ebf4c>] (usb_probe_device+0x24/0x3c)
Sep 15 20:34:00 plug01 kernel: [<c03ebf4c>] (usb_probe_device) from [<c034825c>] (driver_probe_device+0x110/0x244)
Sep 15 20:34:00 plug01 kernel: [<c034825c>] (driver_probe_device) from [<c0346934>] (bus_for_each_drv+0x5c/0x8c)
Sep 15 20:34:00 plug01 kernel: [<c0346934>] (bus_for_each_drv) from [<c0348118>] (device_attach+0x70/0x88)
Sep 15 20:34:00 plug01 kernel: [<c0348118>] (device_attach) from [<c0347800>] (bus_probe_device+0x84/0xb0)
Sep 15 20:34:00 plug01 kernel: [<c0347800>] (bus_probe_device) from [<c0345cac>] (device_add+0x420/0x51c)
Sep 15 20:34:00 plug01 kernel: [<c0345cac>] (device_add) from [<c03e143c>] (usb_new_device+0x1d0/0x354)
Sep 15 20:34:00 plug01 kernel: [<c03e143c>] (usb_new_device) from [<c03e2cd0>] (hub_thread+0xd88/0x1264)
Sep 15 20:34:00 plug01 kernel: [<c03e2cd0>] (hub_thread) from [<c0039fd4>] (kthread+0xbc/0xd8)
Sep 15 20:34:00 plug01 kernel: [<c0039fd4>] (kthread) from [<c0009590>] (ret_from_fork+0x14/0x24)
Sep 15 20:34:00 plug01 kernel: ---[ end trace 2f8ee2277200441c ]---
Sep 15 20:34:00 plug01 kernel: ------------[ cut here ]------------
Sep 15 20:34:00 plug01 kernel: WARNING: CPU: 0 PID: 86 at drivers/usb/storage/uas.c:286 uas_try_complete.isra.13+0x10c/0x12c [uas]()
Sep 15 20:34:00 plug01 kernel: Modules linked in: uas mv_cesa ipv6
Sep 15 20:34:00 plug01 kernel: CPU: 0 PID: 86 Comm: systemd-journal Tainted: G W 3.16.2-1-ARCH #1
Sep 15 20:34:00 plug01 kernel: [<c000f040>] (unwind_backtrace) from [<c000c588>] (show_stack+0x10/0x14)
Sep 15 20:34:00 plug01 kernel: [<c000c588>] (show_stack) from [<c001b7bc>] (warn_slowpath_common+0x70/0x90)
Sep 15 20:34:00 plug01 kernel: [<c001b7bc>] (warn_slowpath_common) from [<c001b878>] (warn_slowpath_null+0x1c/0x24)
Sep 15 20:34:00 plug01 kernel: [<c001b878>] (warn_slowpath_null) from [<bf06bd34>] (uas_try_complete.isra.13+0x10c/0x12c [uas])
Sep 15 20:34:00 plug01 kernel: [<bf06bd34>] (uas_try_complete.isra.13 [uas]) from [<bf06c034>] (uas_data_cmplt+0x54/0x1b4 [uas])
Sep 15 20:34:00 plug01 kernel: [<bf06c034>] (uas_data_cmplt [uas]) from [<c03e4ba4>] (__usb_hcd_giveback_urb+0x60/0xd8)
Sep 15 20:34:00 plug01 kernel: [<c03e4ba4>] (__usb_hcd_giveback_urb) from [<c040eb0c>] (xhci_irq+0x730/0x152c)
Sep 15 20:34:00 plug01 kernel: [<c040eb0c>] (xhci_irq) from [<c03e4138>] (usb_hcd_irq+0x24/0x38)
Sep 15 20:34:00 plug01 kernel: [<c03e4138>] (usb_hcd_irq) from [<c0059440>] (handle_irq_event_percpu+0x34/0x248)
Sep 15 20:34:00 plug01 kernel: [<c0059440>] (handle_irq_event_percpu) from [<c00596a4>] (handle_irq_event+0x50/0x84)
Sep 15 20:34:00 plug01 kernel: [<c00596a4>] (handle_irq_event) from [<c005bd18>] (handle_level_irq+0x98/0x16c)
Sep 15 20:34:00 plug01 kernel: [<c005bd18>] (handle_level_irq) from [<c0058d58>] (generic_handle_irq+0x20/0x34)
Sep 15 20:34:00 plug01 kernel: [<c0058d58>] (generic_handle_irq) from [<c0009db0>] (handle_IRQ+0x44/0xb0)
Sep 15 20:34:00 plug01 kernel: [<c0009db0>] (handle_IRQ) from [<c0531258>] (__irq_usr+0x38/0xa0)
Sep 15 20:34:00 plug01 kernel: ---[ end trace 2f8ee2277200441d ]---
Sep 15 20:34:00 plug01 kernel: scsi 3:0:0:0: Direct-Access Seagate Expansion Desk 0739 PQ: 0 ANSI: 6
Sep 15 20:34:00 plug01 kernel: sd 3:0:0:0: [sdc] Spinning up disk...
Sep 15 20:34:00 plug01 kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
Sep 15 20:34:13 plug01 kernel: .........ready
Sep 15 20:34:13 plug01 kernel: sd 3:0:0:0: [sdc] 1220942645 4096-byte logical blocks: (5.00 TB/4.54 TiB)
Sep 15 20:34:13 plug01 kernel: sd 3:0:0:0: [sdc] Write Protect is off
Sep 15 20:34:13 plug01 kernel: sd 3:0:0:0: [sdc] Mode Sense: 2b 00 10 08
Sep 15 20:34:13 plug01 kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Sep 15 20:34:44 plug01 kernel: sd 3:0:0:0: uas_eh_abort_handler c7bf22a0 tag 0, inflight: IN')

And that's where it crashes, I didn't even get a chance to mount the partition, unless systemctl stop devmon@root.service doesn't stop udevil from auto mounting.

2 Items caught my eye...

drivers/usb/storage/uas.c:286 uas_try_complete.isra.13+0x10c/0x12c [uas]

and

systemd-journal Tainted

A quick google of the first brings up...1 page.
A thread on these forums.

viewtopic.php?t=7697&p=42080

His last comments being.

$this->bbcode_second_pass_quote('', 'T')his is exactly backwards of what I've encountered before, where it was the Seagate that caused problems, so it seems to potentially affect any external USB drive. If you trigger the above crashes a number of times, the kernel itself will sometimes give up and panic (though, as luck would have it, it didn't happen on this trial).

Anyway - there's definitely an issue with external USB handling in 3.16 on ARM that wasn't present in previous kernels. Hope that gives kernel hackers some sort of clue.

I'll do some trials tomorrow with 3.16 on x86 just to see if anything similar occurs.

Rodney


In some of his prior posts he mentions version 3.15.8 not being plagued with this issue, assuming mine is related.

I am actually expecting a replacement USB stick to put in place of the temporary one I'm using to boot off of now, I'll have to toss 3.15.8 on it and see if I get the same results. Unless of course I am making incorrect assumptions?

Lastly, it would appear if its an issue with the actual hardware/drivers/OS as opposed to an NTFS or partition issue if I am reading everything correctly?

Thank you very much
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Tue Sep 16, 2014 10:20 pm

As a side note, where can I find prior builds of the kernel for this device?
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby moonman » Wed Sep 17, 2014 4:18 am

rollback.archlinux.org

Which is pretty slow. I think somebody mirrored 3.15.8 in the samba data corruption thread
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: PogoPlug Series 4 + NTFS Seagate Expansion 5TB (STBV5000

Postby Palmore » Wed Sep 17, 2014 2:20 pm

This has been solved, atleast a couple of valid work arounds.

The thread over at

viewtopic.php?f=53&t=7697&start=10

Has some good links to info on whats causing this, and some additional workarounds.

For now, I'm just using a USB 2.0 extension cable between the pogoplug and my HDD to force it to connect via USB 2.0.

The disk is online and accessible.

I will keep it like this until any needed kernel patches are applied in future releases
Palmore
 
Posts: 10
Joined: Sun Sep 14, 2014 7:57 pm


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 2 guests