Skip to main content

Timeline for USB HDD not working on linux

Current License: CC BY-SA 3.0

25 events
when toggle format what by license comment
May 23, 2017 at 12:40 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Feb 2, 2015 at 22:50 answer added Klaatu von Schlacker timeline score: 2
Sep 28, 2014 at 19:52 answer added dervishe timeline score: 0
Sep 18, 2014 at 4:54 answer added unixmiah timeline score: 0
Sep 10, 2014 at 19:04 comment added eyoung100 My hunch was correct. You need to go into your kernel config and under Filesystem Support enable HFS and HFS+.
Sep 10, 2014 at 18:45 comment added user2747949 @ECarterYoung The output is squashfs 26695 1
Sep 9, 2014 at 17:09 comment added eyoung100 Post the output of sudo lsmod | grep hfs I have a hunch that the newer Debian based kernels are compiled w/o hfs filesystem support
Aug 23, 2014 at 9:08 comment added user2747949 @slm unfortunately, the same problem occurs on the latest Ubuntu LiveCD too. Also, the kernel logs are the same.
Aug 22, 2014 at 22:42 history tweeted twitter.com/#!/StackUnix/status/502949064988954624
Aug 22, 2014 at 19:56 comment added slm If it's working on 2 computers, then I'd agree it's likely not the cable or the HDD, but the OS. Just crossing possibilities off the list. As to why I would probably get a liveCD and boot one of the systems with that to confirm. I would expect Knoppix or an Ubuntu LiveCD would be able to see it.
Aug 22, 2014 at 19:04 comment added user2747949 @slm The HDD works on Windows too; I have power cycled the machines many times but I didn't swap out the cable because I don't have another compatible one. However since it works on other OSs I don't think the cable could be the cause. As a last resort, I may contact Western Digital and ask for a replacement, but the HDD is out of warranty by now so I'll probably have to buy a new one. The problem is that I don't even know if it's just a problem about it.
Aug 22, 2014 at 18:29 comment added slm @user2747949 - if that's the case then it's either a recent update to the OS'es or something about the HDD. To split the tie, does the HDD work in anything other than the OSX box? Also I assume you've swapped out the cable and power cycled the Linux boxes in your tests?
Aug 22, 2014 at 18:16 comment added user2747949 @slm I understand what you mean, but I'm afraid it can't be like that. I've always used that hard drive with both the Debian PC and the Raspberry Pi without any problem, so why would it give problems now if it's a BIOS issue?
Aug 22, 2014 at 17:38 history edited user2747949 CC BY-SA 3.0
added 492 characters in body
Aug 22, 2014 at 17:32 comment added slm With little messaging to go on it's likely an issue b/w your system's BIOS + the USB HDD. The device isn't showing up to the kernel in any meaningful way. it's not really the kernel's issue. I have many devices around the house that just don't work under Linux but work perfectly fine with Windows + OSX.
Aug 22, 2014 at 17:30 history edited slm CC BY-SA 3.0
added 92 characters in body
Aug 22, 2014 at 17:24 comment added user2747949 @derobert yes, I get the same messages. And no, the drive is not password protected.
Aug 22, 2014 at 17:20 comment added derobert Also, does this drive have a password enabled on it with the WD utility?
Aug 22, 2014 at 17:18 comment added derobert Do you get the same messages in your Debian PC's kernel log as you do on the RPi?
Aug 22, 2014 at 17:13 history edited user2747949 CC BY-SA 3.0
added 242 characters in body
Aug 22, 2014 at 17:05 comment added derobert When you plug it in, what are the lines added to /var/log/kern.log (or to dmesg)?
Aug 22, 2014 at 17:03 history edited user2747949 CC BY-SA 3.0
added 624 characters in body
Aug 22, 2014 at 17:00 comment added drs What's the output of lsusb? (edit your question with this output)
Aug 22, 2014 at 16:57 review First posts
Aug 22, 2014 at 17:00
Aug 22, 2014 at 16:57 history asked user2747949 CC BY-SA 3.0