DVR doesn't recognize new eSATA drive

I just purchased a new eSATA drive (Western Digital 1 TB:  WDBABT0010HBK-NESN) and connected it to my Motorola QIP7232-P2 set-top box, but after following the on-screen prompts to enable more storage the DVR does not recognize the additional storage and still reflects the pre-eSATA drive usage %.
I've already disconnected and reconnected the eSATA drive and tried to "enable more storage" through the DVR, which included rebooting the set-top box, a few times already.
Thoughts?

Thanks, Armond!  I haven't tried replacing the SATA cable yet, but that may be the next logical step.
I tried disconnecting, reconnecting and rebooting the DVR at least a dozen times.  Finally, I was able to get the DVR to recognize the external storage (showing 100% capacity).
However, when the eSATA drive was connected and recognized the DVR wouldn't record any shows (neither scheduled nor live TV).  As soon as I disconnected the drive, recording would resume.  The error message I received in the "History" section of the DVR stated, "This show could not be recorded due to the channel being unavailable, not subscribed or other error."  Verizon Technical Support even sent me a refurbished DVR and that encountered the same problem.
Do you still think it's the cable?

Similar Messages

  • New DVR, Can't Recognize Existing ESata Drive/Prog​rams

    I had a Motorola 7216 DVR box that had an external ESata drive.  The box had three issues:  froze 2-3 times a day for maybe 30 seconds, sound "clipping" during loud sections of shows/movies, and I could never get the Android app or web app to connect to the DVR.  So, I received a new 7232 DVR today.  Prior to disconnecting the old, I did the proper method of ejecting of the ESata Drive.  
    I hooked up the new DVR, and (possibly mistakenly) hooked up the ESata drive as well before booting it up the first time.   Did the initialization, all went well.   Went through the routine of adding ESata, rebooted, didn't recognize the drive.   Realize I maybe shouldn't have plugged it in, so unplugged ESata cord, rebooted, did Set-Top Box Auto Correct, then went through the proper routine to add external storage.   However, when rebooting, the box blinks one light for 30 seconds, then the entire display lights up, then it reboots, repeating this routine ad infinitum (nothing ever displays on the TV).   
    So, thinking I got a bad box, I hook up the old DVR, get it working, and then run the add ESata routine.  It now is in the same infinite loop as the old box (for 30 minutes now as I type).  
    Removing the ESata, and rebooting, back to normal operation, though without ESata and all of the recorded shows.  
    Any ideas?   Do you think my "mistake" in hooking up the ESata drive to the new box right off the bat might have messed up the drive?   I'm ordering an ESata to Sata cable so I can hook up the drive to my PC and see if it's accessable.  Maybe I can reformat it, knowing we'll lose all our programs (actually, my wife's programs......no big deal to me )
    Or does it take a long time to initialize an existing ESata drive with lots of programs on it?  
    Solved!
    Go to Solution.

    Greetings, armond_in_nj!
    Thanks for your message responding to my plea for help!
    OK.... Finally have had time to try everything again AND make notes along the way.
    I have a Motorola STB, model HD DVR QIP 7216 P2 500GB.
    I have a Western Digital external eSata hard drive, model  WDBABT0010HBK-NESN – 1TB (on the "approved" list).
    And yes, I have tried everything mentioned in the post by "steveKane" just above my original. See below at the end for what happened when I tried to re-format my WD drive on my desktop PC.
    When I first got my WD external HD several months ago, I had to call Verizon support to get the DVR to recognize the Western Digital external HD, but we finally got that fixed and all was fine (i.e., programs recording to external HD, status visible under DVR/Recorder Status using my remote). Then, around mid-november, when I would schedule programs to record, either when I was asleep or at work, when I went to view them later, often times one program was broken into 2 or more segments. Then a little later, sometimes while watching a recorded program, the DVR would just freeze. I would reset the Set Top Box (STB) and could continue watching the program. But this all got worse and worse and, finally, I called tech support. After a frustrating hour with a tech support person, who declared everything was fine with my STB because I could press RECORD and the DVR would record a short segment of programming. During that hour conversation, we had reset the STB more than 10 times. I finally asked to speak with this technician's supervisor, who finally agreed with me that the STB needed replacing. When I received the new STB, it would not function at all. So.... another call to support, more attempts on their end to re-set the STB, and finally they agreed that I needed yet another new STB. When that arrived, I went through all the proper steps to set up the STB first, without the external HD and, only when the new STB was working properly did I try to get it to recognize my external HD.
    The Western Digital instructions for connecting their drive to my DVR are as follows:
    1. Power off the DVR box by disconnecting the AC power cord. --- Did that
    2. Connect one end of the eSATA cable to your My Book AV and the other end to the DVR box (do not use a USB cable to connect to DVR) -- Did that
    3. Connect one end of the AC power cord to the My Book AV and the other end to the electrical outlet. The power LED inlluminates. ---- I did, and it did
    4. Waii approximately 15 seconds for the hard drive to reach operating speed. -- Did that
    5. Power on the DVR box by reattaching the AC power cord. -- Did that
    6. Follow the on-screen instructions.
    This procedure did not work. There were no on-screen instructions when I powered the STB back on. So, I did the following:
    1. I went to "DVR/Enable more storage" and followed the prompts from there, which at one point told me to connect the external HD to the STB, which it already was. I pressed OK to proceed and got the message that "external storage is active for this STB. To detect the external hard, please press OK to reboot the STB".
    2. Did that, waited; during reboot, a white band appears briefly across the TV screen with the words "Please wait" in red, then it goes away as the reboot process continues. Eventually, I get a message that says "Press MENU to watch FiOS TV, or turn your TV off". I press MENU, the screen appears (with red background) saying "Verizon FiOS is starting up - one moment pleast. Initial download in progress. It takes about one minute", then after a minute or so, the TV image appears.
    3. I go to DVR/Recorder status, and the external HD is not there.
    Since the STB prompted me to connect the external HD during step 1 above, I decided to power everything off, disconnect the eSATA cable from the back of the STB, reconnect power to the external HD, then reconnect power to the STB to reboot.
    Everything in step 2 above proceeds as outlined there, but still I got no on-screen instructions after FiOS started back up. So, I went to DVR/Enable more storage, followed the prompts until asked to connect the external HD to the STB, at which time, now, I get a pop-up screen that says "The connected external HD has been previously used with another STB with a different DVR. Using the drive on this STB will remove all existing content on the drive. Do you want to use this drive?" Options are "ACCEPT" or "REJECT". I press OK to ACCEPT, then we go through the whole reboot thing again, and still no sign of the external HD under DVR/Recorder status.
    I even tried connecting the WD external HD to my desktop computer (running XP Professional) using a USB cable (following "steveKane's" suggestion in his posting of 12-02-12), thinking I could try to reformat the drive on my desktop. After connecting, I go to Window Explorer and the drive is not there. When I open the "Safely Remove Hardware" icon in the Task Bar, the drive is visible there. I tried stopping the device, removing it, then waiting a bit and reconnecting it, but get the same results. Not visible in Explorer so that I can try to re-format.
    The posting by "mcorbo" right above "steveKane's" posting says "The only way to reuse the drive is to let the dvr reformat it." So how does one get the DVR to reformat the drive????
    I hope I have given you the information needed.
    I'm at my wits end. Any suggestions would be greatly appreciated.

  • Windows XP Pro doesn't recognize new hard drive on T61 thnkpad

    Hard drive: 160GB 7200 RPM SATA
                        The Lenovo part number for the new hard drive on my invoice is: 41N5737
                        However, the sticker on the hard drive itself has this Lenovo part number: 42T1057
                        It is made by Hitachi.
    Thinkpad: T61 (8891-CTO)
    OS: Windows XP Pro SP2 (newly purchased, shrink-wrapped)
    This thinkpad had Vista Home on it. I bought the new hard drive for the purpose of loading a just-purchased copy of Windows XP Pro SP2 on it (. After installing the new hard drive:
    1. I turned on the machne and inserted the Windows XP CD.
    2. Files from the CD (drivers, etc.) started being loaded (into memory, I guess).
    3. Then got a prompt to select whether I'd like to install a new version of XP or restore an existing version.
    4. I selected Install a new version.
    5. Then I got a message saying Windows could not find a hard drive on my machine.
    6. Then I restarted, and interrupted the restart to look at the BIOS config settings
    7. I found the hard drive test function, and started the hard drive test.
    8. It took a while, but the hard drive test was successful. So hard drive is OK, and the BIOS is aware of it.
    How can I make Windows XP aware of my new hard drive?
    Thanks for any help....
    Solved!
    Go to Solution.

    Tdc3, welcome to the forum,
    change the BIOS settings in Config > SATA to Compatibility Mode from AHCI.
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • My internal hard drive isn't being recognized on my macbook pro but when I put the HD in my Mac Pro (desktop), the desktop computer recognizes the HD.  When I insert the installer CD on my laptop, it also doesn't recognize my hard drive. Please help!

    My internal hard drive isn't being recognized on my macbook pro but when I put the HD in my Mac Pro (desktop), the desktop computer recognizes the HD.  When I insert the installer CD on my laptop, it also doesn't recognize my hard drive. Please help! Thank you!
    I've also been getting an image with the folder and question mark. I've tried everything on the apple support page but it doesn't seem to work either.

    Well, I tried all of your suggestions and they didn't work -- no surprise because I was trying to backup to my external c.d. disk.  Duh!  The application for the home is in the mail.

  • I have a MacBook Pro 2007 and I installed Mac OS 10.6 but I lost power in the process and now the mac doesn't recognize my hard drive

    I have a MacBook Pro 2007 and I installed Mac OS 10.6 but I lost power in the process and now the mac doesn't recognize my hard drive, how can I fix this

    I've tried it but since I'm using a USB disk drive it keeps freezing up or showing you a folder blinking folder with a question mark. (?). When I start the mac up I hold the control button until the Mac OS install disk shows up. My hard drive doesn't show up anymore. Is there any other button I have to hold down to bring a different menu up. I have also tried to boot up holding control and C and nothing happens.  Thanks for the help so far

  • My imac doesn't recognize my backup drive anymore,what can i do?

    My Imac doesn't recognize my backup drive anymore,what can i do?

    Unfortunately, that usually means the drive has died although it doesn't mean some other hardware failure or even software failure (in some cases.)
    I think the wise thing to do is take it in for service.

  • Emac won't start up and tech tool doesn't recognize my hard drive.

    My emac's been running slow and crashing. Today it got to the point where I couldn't even use the finder when I started up. I tried to start up from tech tool and did so successfully. It recognized my hard drive and I ran the tests and repairs, but during one of the tests it got hung up. I restarted the computer and now all I get when I start up is a little folder in the middle of the screen with a question mark. I started back up from the tech tool cd, but it doesn't recognize my hard drive anymore. I'm really scared I've lost everything. I could sure use some help! The emac is running Tiger.
    Jane

    jamech,
    Welcome to the Apple Discussions!
    What version of Tech Tool where you using? If it was an older version, incompatible with OS X 10.4 Tiger, that could actualy make things worse --- see Only use Mac OS X 10.4-compatible disk utilities with Mac OS X 10.4 volumes.
    The version of Disk Utility that ships with OS X 10.4.2 and higher is more capable than earlier versions. Try booting from the Tiger install disc, then open Disk Utility from the Installer menu and see if you can run Repair Disk on the hard drive. Refer to Using Disk Utility and fsck. Take note of any errors reported and post back with the results. If errors are reported repaired, re-run Repair Disk until you either get a clean bill of health or a report of unrepairable errors.
    When you get the Mac running from the hard drive again, you'll need to determine why it was running slowly in the first place. Anything reported by Repair Disk is of interest here. You could try using a third-party utility such as OnyX to clear caches and logs, and to make sure the maintenance scripts are current (there's a timer in Tiger than will force the scripts to run if you normally have the Mac shut down or in system sleep overnight; the timer is based on elasped time and isn't exact).

  • FiOS HD-DVR crashing since adding external eSATA drive

    After the recent firmware update, I added an 2TB external eSATA drive to my FiOS DVR.  I'd really been looking forward to this because our DVR had been perpetually 90+% full.  After a couple of reboots, the drive was recognized and showed as a second DVR at 0% full in the DVR Status menu.  Just to make sure everything worked, I scheduled a bunch of recordings to make sure it was utilizing the new drive.
    A few days later, we found that the DVR had erased several of our recordings because it was out of space.  Checking the DVR status again, the new drive had disappeared. 
    After a couple of reboots, it appeared in the status menu again, and the DVR started recording to the external drive.  But a few days later, my wife couldn't find the recordings.  Turns out it had disappeared again. 
    This pattern has repeated itself several times over the last couple of weeks.  On two occasions, the DVR has completely frozen while we were in the middle of watching something, necessitating a complete reboot in order to watch TV, and interrupting any recording that was going on in the background.  Each time, at least 2 reboots has been required before the eSATA drive appears. 
    Needless to say, this whole thing is a disaster.  I spent a ton of money and the result is poorer service quality.  What can I do to fix this?

    After a few minutes searching I found the link of recommended drives.
    http://www22.verizon.com/ResidentialHelp/FiOSTV/Ot​her+Hardware/eSATA/129841.htm
    Here's a snipet from that page...
    Which Verizon FiOS TV DVRs are compatible with eSATA devices?
    The following FiOS TV DVRs are compatible with eSATA devices:
    Motorola QIP 7216
    Motorola QIP 7232
    Cisco CHS 435 HDC
    Which eSATA external storage devices can I use with my FiOS DVR?
    Verizon recommends the eSATA hard drives below for use with FiOS DVR. Customers choosing to install other drive types will assume the risk of compatibility with FiOS DVR and Verizon will not assist with compatibility or performance issues should they arise.
    Western Digital – WDBACS5000EBK-NEVZ – 500GB
    Western Digital – WDBACS0010HBK-NEVZ – 1TB
    Western Digital Retail – WDBABT0010HBK-NESN – 1TB
    I'm not sure why this happened...'Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied.'
    I'm assuming that the above drives were the only one tested at the time. We users can add to this list if we want. Anyone game?

  • Time machine doesn't recognize external hard drive

    Recently I went to the apple store to get help to switch from Mavericks to Mountain Lion (I had some problems with Mavericks). They used time machine to bring back my applications (from my external hard drive, LaCie) on the Mountain Liion software. They said my time machine/external hard drive should work the same when I got home. Now, when I go to back up my computer, time machine doesn't recognize that I've backed up my files before. In the past, when time machine was working, every time I plugged in my hard drive the icon for it would turn blue, time machine recognized it, and it would back up my files. Now, the icon for the hard drive shows up, but time machine doesn't recognize it.
    Some other things:
    - when I open my external hard drive on finder, it shows all of my previous back ups
    - I used disk utility to check my hard drive and macintosh HD - both are OK
    How can I use time machine to continue backing up files? Or am I going to have to partition or erase the hard drive and start a new back up?
    Thank you in advance

    nevermind! time machine suddenly recognized the disk after half an hour. sorry, I don't know how to delete this post!

  • The Toshiba website doesn't recognize my hard drive's serial number and P/N

    Hello,
    I bought my Toshiba Canvio Basics 3.0 hard drive from Amazon a little under two months ago. The hard drive stopped working for some reason (I didn't drop it or anything, it just stopped working).
    I was of course trying to use my warranty to fix it or exchange it, but the Toshiba website doesn't recognize my serial number and product number. They're right there, black and white on the sticker on the back of my hard drive, but the website says they're invalid.
    Anyone has any clue what's going on? I'd rather not throw 50 euros out the window for less than two months of use.
    Product number is HDTB105XK3AA -- and not HDTB105*E*K3AA as some websites say (including Amazon).
    Thanks for your help.

    Just adding to the above comments, I have a simialr issue. bought a 3gb drive from amazon and now 8 months later it has just stopped working (wont power up at all) again it has just sat new to my computer working fine for the last 8 months and has now just stopped.
    I contacted amazon and got this reply from the seller:
    "Hi Jack,
    Thanks for your e-mail and apologies for the problems with your laptop. Your laptop comes with a 1 year manufacturer warranty directly with Toshiba so they should be able to resolve this for you. Their customer contact number is 0333 222 7444 or if you prefer to go online the Toshiba Computer Support website (http://www.toshiba.co.uk/innovation/generic/computing-support/) has full contact/ e-mail options.
    Kind regards,
    Customer service Team"
    So came here to try and find more details but cannot find the model or anything regarding warranty, any assistance glady recieved

  • Disk Utility won't recognize new hard drive

    Hello,
    Thanks for taking the time to read this.
    The original hard drive (80 GB) went bad, so I replaced with a new 160 GB Western Digital one. I formatted the hard drive using Disk Utility from the Mac OS X Disk. It worked the first time I booted into Leopard (I just booted up to make sure the OS loaded...didn't install any new software and/or hardware).
    Then I shut it down and started it back up, and the computer didn't recognize the hard drive. I inserted the Mac OS X disk and ran Disk Utility, but the hard drive was not recognized.
    So now I'm thinking the new hard drive was also bad. So, I ordered another one (Seagate 160 GB) and it to was not recognized when I ran Disk Utility from the Mac OS X disk.
    When replacing all of them, I followed directions I found here and other websites. They all said to do it the same way, so I'm assuming the directions for replacing a hard drive in a laptop were correct.
    I searched Google and found several posts suggesting using an application called Disk Warrior, but from my understanding, you cannot run it from a disk, it needs to be installed, which is obviously impossible since the hard drive isn't recognized.
    Then I ran Open Firmware and did "devalias" from the prompt. From what I can tell in the list of hardware, the hard drive is recognized, but I am not sure. I took a picture of the screen printout but do not see an option to attached it to this post. Therefore, I'll just tell what it said for now and will create an image hosting account so I can add a URL for it later.
    In the list, "hd" is in the left column and in the right column of the same line is "/pci@f4000000/ata-6@d/disk@0" (without quotes).
    If anybody has any suggestions, they would be greatly appreciated.

    Welcome to the Apple discussions.
    I've replaced a few hard drives, and in instances where it's not recognized, it's either been a cable connection issue or I've seen others with a jumper issue. Either the hard drive to logic board cable isn't properly set, typically on the logic board side, or a jumper was left on the drive, where typically you can just remove it. I haven't personally had the cable fail, however, that's possible too.
    When you pulled the large plug from the back of the original hard drive, did you do it very carefully? It's not like a desktop hard drive plug that you can just pull out ... it needs to be wiggled out, gently. I have a hard time believing two new drives would be essentially DOA, although the first one worked for a bit, which leads me to wonder about the physical connections.
    Since you have your original OS X disks, you could try running the Apple hardware test to see if it gives you any error message(s).

  • IMac 400dv will not recognize new hard drive installed

    Hi,
    I had been having trouble with my iMac 400dv's hard drive. I had posted the problems I was having and had gotten some very nice feedback. The final decision was to install a new hard drive and battery.
    I purchased a refurbished 40GB Maxtor to replace my old 20GB. Installation was no problem except that my iMac will not recognize the new drive. If I reinstall the old one, it recognizes it right away, so I know it has been installed correctly.
    I took the new hard drive back to the store and the tech said that it wasn't set on the "Master" position. He set it and tested the drive and said that it was fine. I reinstalled and get the same result, no drive can be sellected to install the software. No matter where I set the pin, I get the same result. I called the phone help line (MicroCenter) and the new tech told me that the drive was too big for my mac, which makes no sense to me since they suggested I buy a 100GB in the 1st place.
    I have 1GB of memory, my installation disk if for 8.6 and I will bring it up to 9.2 if I can get it running again.
    Any suggestions?
    thanks,
    Lucy

    Lucy Rust...
    In my opinion no Macintosh user should attempt to install a refurbished HD under any condition. Especially any HD that is to be bootable as they are no longer reliable for the Mac.
    Master setting is a must for the HD and never tinker with an optical setting. Well, if you could mess with the optical setting, expect to do some micro-surgery.
    You should be good for a HD up to a capacity of 120GB. The threshold is somewhere around 137GB but you will not find such odd capacity on the market.
    I think the rest has been covered.
    ...Ron

  • HAL doesn't recognize my ext. drive with 1500GB, the 500GB one works

    Hi there
    Some days ago I bought a 1500GB external harddrive, but after plugin it in via USB, it doesn't appear in my file manager. I tested it with thunar and pcmanfm, with both it didn't work. I don't think, that it's their fault, I think HAL doesn't like my new drive. My older one with 500GB is automounted as it should be. And I also don't think, that its a hardware issue, because in an ubuntu live-session it works with both harddrives.
    This is how the two drives are partitioned
    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0008941c
    Device Boot Start End Blocks Id System
    /dev/sdb1 1 60801 488384001 83 Linux
    Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
    255 heads, 63 sectors/track, 182401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0004aa3c
    Device Boot Start End Blocks Id System
    /dev/sdc1 1 182401 1465136001 83 Linux
    As you can see, no difference here. The drive with 1500GB has xfs as filesystem, the 500GB has jfs, but that isn't the reason, I tried many filesystems on the 1500GB one and it didn't work with all of them
    In the AUR, there appeared a new packaged called devicekit and I thought, that this might spit out some helpful informations. I used the command "devkit -m"
    1500GB:
    action=add @ 10:14:29.876418
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1
    subsystem: usb
    device file: /dev/bus/usb/001/007
    symlink: /dev/char/189:6
    properties:
    TYPE=0/0/0
    DEVNAME=/dev/bus/usb/001/007
    DEVLINKS=/dev/char/189:6
    BUSNUM=001
    UDEV_LOG=0
    MINOR=6
    ACTION=add
    PRODUCT=152d/2336/100
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1
    DEVICE=/proc/bus/usb/001/007
    MAJOR=189
    SUBSYSTEM=usb
    DEVTYPE=usb_device
    DEVNUM=007
    SEQNUM=1668
    action=add @ 10:14:29.945265
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0
    subsystem: usb
    device file: (none)
    properties:
    TYPE=0/0/0
    INTERFACE=8/6/80
    UDEV_LOG=0
    ACTION=add
    PRODUCT=152d/2336/100
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0
    DEVICE=/proc/bus/usb/001/007
    SUBSYSTEM=usb
    DEVTYPE=usb_interface
    MODALIAS=usb:v152Dp2336d0100dc00dsc00dp00ic08isc06ip50
    SEQNUM=1669
    action=add @ 10:14:29.947723
    device: /sys/class/scsi_host/host4
    subsystem: scsi_host
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_host/host4
    SUBSYSTEM=scsi_host
    SEQNUM=1670
    action=add @ 10:14:29.952727
    device: /sys/class/usb_endpoint/usbdev1.7_ep81
    subsystem: usb_endpoint
    device file: /dev/usbdev1.7_ep81
    symlink: /dev/char/251:24
    properties:
    DEVNAME=/dev/usbdev1.7_ep81
    DEVLINKS=/dev/char/251:24
    UDEV_LOG=0
    MINOR=24
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep81
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1671
    action=add @ 10:14:29.978530
    device: /sys/class/usb_endpoint/usbdev1.7_ep02
    subsystem: usb_endpoint
    device file: /dev/usbdev1.7_ep02
    symlink: /dev/char/251:25
    properties:
    DEVNAME=/dev/usbdev1.7_ep02
    DEVLINKS=/dev/char/251:25
    UDEV_LOG=0
    MINOR=25
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep02
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1672
    action=add @ 10:14:29.986978
    device: /sys/class/usb_endpoint/usbdev1.7_ep00
    subsystem: usb_endpoint
    device file: /dev/usbdev1.7_ep00
    symlink: /dev/char/251:26
    properties:
    DEVNAME=/dev/usbdev1.7_ep00
    DEVLINKS=/dev/char/251:26
    UDEV_LOG=0
    MINOR=26
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.7_ep00
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1674
    action=add @ 10:14:29.992531
    device: /sys/class/usb_device/usbdev1.7
    subsystem: usb_device
    device file: /dev/usbdev1.7
    symlink: /dev/char/189:6
    properties:
    DEVNAME=/dev/usbdev1.7
    DEVLINKS=/dev/char/189:6
    UDEV_LOG=0
    MINOR=6
    ACTION=add
    DEVPATH=/class/usb_device/usbdev1.7
    MAJOR=189
    SUBSYSTEM=usb_device
    SEQNUM=1673
    action=add @ 10:14:34.967982
    device: /sys/class/bdi/8:32
    subsystem: bdi
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/bdi/8:32
    SUBSYSTEM=bdi
    SEQNUM=1679
    action=add @ 10:14:35.048659
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0
    subsystem: scsi
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0
    SUBSYSTEM=scsi
    DEVTYPE=scsi_device
    MODALIAS=scsi:t-0x00
    SEQNUM=1675
    action=add @ 10:14:35.049786
    device: /sys/class/scsi_disk/4:0:0:0
    subsystem: scsi_disk
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_disk/4:0:0:0
    SUBSYSTEM=scsi_disk
    SEQNUM=1676
    action=add @ 10:14:35.051976
    device: /sys/class/scsi_device/4:0:0:0
    subsystem: scsi_device
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_device/4:0:0:0
    SUBSYSTEM=scsi_device
    SEQNUM=1680
    action=add @ 10:14:35.060884
    device: /sys/class/scsi_generic/sg3
    subsystem: scsi_generic
    device file: /dev/sg3
    symlink: /dev/char/21:3
    properties:
    DEVNAME=/dev/sg3
    DEVLINKS=/dev/char/21:3
    UDEV_LOG=0
    MINOR=3
    ACTION=add
    DEVPATH=/class/scsi_generic/sg3
    MAJOR=21
    SUBSYSTEM=scsi_generic
    SEQNUM=1681
    action=add @ 10:14:35.067457
    device: /sys/class/bsg/4:0:0:0
    subsystem: bsg
    device file: /dev/bsg/4:0:0:0
    symlink: /dev/char/254:3
    properties:
    DEVNAME=/dev/bsg/4:0:0:0
    DEVLINKS=/dev/char/254:3
    UDEV_LOG=0
    MINOR=3
    ACTION=add
    DEVPATH=/class/bsg/4:0:0:0
    MAJOR=254
    SUBSYSTEM=bsg
    SEQNUM=1682
    action=add @ 10:14:35.105877
    device: /sys/block/sdc
    subsystem: block
    device file: /dev/sdc
    symlink: /dev/block/8:32
    symlink: /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0
    symlink: /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    properties:
    ID_SERIAL_SHORT=908888888888
    DEVNAME=/dev/sdc
    DEVLINKS=/dev/block/8:32 /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    ID_MODEL=41AS
    ID_SERIAL=ST315003_41AS_908888888888-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    MINOR=32
    ACTION=add
    ID_VENDOR=ST315003
    ID_BUS=usb
    DEVPATH=/block/sdc
    ID_TYPE=disk
    ID_REVISION=0100
    MAJOR=8
    SUBSYSTEM=block
    DEVTYPE=disk
    SEQNUM=1677
    action=add @ 10:14:35.144133
    device: /sys/block/sdc/sdc1
    subsystem: block
    device file: /dev/sdc1
    symlink: /dev/block/8:33
    symlink: /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0-part1
    symlink: /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0-part1
    symlink: /dev/disk/by-uuid/8a60b3b7-50bc-48a7-b3ba-aa0f13f32156
    symlink: /dev/disk/by-label/1500GB
    properties:
    ID_SERIAL_SHORT=908888888888
    ID_FS_LABEL=1500GB
    ID_FS_LABEL_ENC=1500GB
    DEVNAME=/dev/sdc1
    DEVLINKS=/dev/block/8:33 /dev/disk/by-id/usb-ST315003_41AS_908888888888-0:0-part1 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/8a60b3b7-50bc-48a7-b3ba-aa0f13f32156 /dev/disk/by-label/1500GB
    ID_MODEL=41AS
    ID_SERIAL=ST315003_41AS_908888888888-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    MINOR=33
    ACTION=add
    ID_VENDOR=ST315003
    ID_BUS=usb
    DEVPATH=/block/sdc/sdc1
    ID_TYPE=disk
    ID_REVISION=0100
    ID_FS_USAGE=filesystem
    MAJOR=8
    SUBSYSTEM=block
    ID_FS_TYPE=xfs
    ID_FS_UUID=8a60b3b7-50bc-48a7-b3ba-aa0f13f32156
    DEVTYPE=partition
    SEQNUM=1678
    ID_FS_UUID_ENC=8a60b3b7-50bc-48a7-b3ba-aa0f13f32156
    500GB:
    action=add @ 10:13:40.628381
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2
    subsystem: usb
    device file: /dev/bus/usb/001/006
    symlink: /dev/char/189:5
    properties:
    TYPE=0/0/0
    DEVNAME=/dev/bus/usb/001/006
    DEVLINKS=/dev/char/189:5
    BUSNUM=001
    UDEV_LOG=0
    MINOR=5
    ACTION=add
    PRODUCT=1058/910/106
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2
    DEVICE=/proc/bus/usb/001/006
    MAJOR=189
    SUBSYSTEM=usb
    DEVTYPE=usb_device
    DEVNUM=006
    SEQNUM=1653
    action=add @ 10:13:40.700691
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0
    subsystem: usb
    device file: (none)
    properties:
    TYPE=0/0/0
    INTERFACE=8/6/80
    UDEV_LOG=0
    ACTION=add
    PRODUCT=1058/910/106
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0
    DEVICE=/proc/bus/usb/001/006
    SUBSYSTEM=usb
    DEVTYPE=usb_interface
    MODALIAS=usb:v1058p0910d0106dc00dsc00dp00ic08isc06ip50
    SEQNUM=1654
    action=add @ 10:13:40.701744
    device: /sys/class/scsi_host/host3
    subsystem: scsi_host
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_host/host3
    SUBSYSTEM=scsi_host
    SEQNUM=1655
    action=add @ 10:13:40.702982
    device: /sys/class/usb_endpoint/usbdev1.6_ep81
    subsystem: usb_endpoint
    device file: /dev/usbdev1.6_ep81
    symlink: /dev/char/251:21
    properties:
    DEVNAME=/dev/usbdev1.6_ep81
    DEVLINKS=/dev/char/251:21
    UDEV_LOG=0
    MINOR=21
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep81
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1656
    action=add @ 10:13:40.705026
    device: /sys/class/usb_endpoint/usbdev1.6_ep02
    subsystem: usb_endpoint
    device file: /dev/usbdev1.6_ep02
    symlink: /dev/char/251:22
    properties:
    DEVNAME=/dev/usbdev1.6_ep02
    DEVLINKS=/dev/char/251:22
    UDEV_LOG=0
    MINOR=22
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep02
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1657
    action=add @ 10:13:40.709720
    device: /sys/class/usb_endpoint/usbdev1.6_ep00
    subsystem: usb_endpoint
    device file: /dev/usbdev1.6_ep00
    symlink: /dev/char/251:23
    properties:
    DEVNAME=/dev/usbdev1.6_ep00
    DEVLINKS=/dev/char/251:23
    UDEV_LOG=0
    MINOR=23
    ACTION=add
    DEVPATH=/class/usb_endpoint/usbdev1.6_ep00
    MAJOR=251
    SUBSYSTEM=usb_endpoint
    SEQNUM=1659
    action=add @ 10:13:40.719258
    device: /sys/class/usb_device/usbdev1.6
    subsystem: usb_device
    device file: /dev/usbdev1.6
    symlink: /dev/char/189:5
    properties:
    DEVNAME=/dev/usbdev1.6
    DEVLINKS=/dev/char/189:5
    UDEV_LOG=0
    MINOR=5
    ACTION=add
    DEVPATH=/class/usb_device/usbdev1.6
    MAJOR=189
    SUBSYSTEM=usb_device
    SEQNUM=1658
    action=add @ 10:13:45.659241
    device: /sys/class/bdi/8:16
    subsystem: bdi
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/bdi/8:16
    SUBSYSTEM=bdi
    SEQNUM=1664
    action=add @ 10:13:45.680716
    device: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host3/target3:0:0/3:0:0:0
    subsystem: scsi
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host3/target3:0:0/3:0:0:0
    SUBSYSTEM=scsi
    DEVTYPE=scsi_device
    MODALIAS=scsi:t-0x00
    SEQNUM=1660
    action=add @ 10:13:45.681808
    device: /sys/class/scsi_disk/3:0:0:0
    subsystem: scsi_disk
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_disk/3:0:0:0
    SUBSYSTEM=scsi_disk
    SEQNUM=1661
    action=add @ 10:13:45.695199
    device: /sys/class/scsi_device/3:0:0:0
    subsystem: scsi_device
    device file: (none)
    properties:
    UDEV_LOG=0
    ACTION=add
    DEVPATH=/class/scsi_device/3:0:0:0
    SUBSYSTEM=scsi_device
    SEQNUM=1665
    action=add @ 10:13:45.703093
    device: /sys/class/scsi_generic/sg2
    subsystem: scsi_generic
    device file: /dev/sg2
    symlink: /dev/char/21:2
    properties:
    DEVNAME=/dev/sg2
    DEVLINKS=/dev/char/21:2
    UDEV_LOG=0
    MINOR=2
    ACTION=add
    DEVPATH=/class/scsi_generic/sg2
    MAJOR=21
    SUBSYSTEM=scsi_generic
    SEQNUM=1666
    action=add @ 10:13:45.709314
    device: /sys/class/bsg/3:0:0:0
    subsystem: bsg
    device file: /dev/bsg/3:0:0:0
    symlink: /dev/char/254:2
    properties:
    DEVNAME=/dev/bsg/3:0:0:0
    DEVLINKS=/dev/char/254:2
    UDEV_LOG=0
    MINOR=2
    ACTION=add
    DEVPATH=/class/bsg/3:0:0:0
    MAJOR=254
    SUBSYSTEM=bsg
    SEQNUM=1667
    action=add @ 10:13:45.773375
    device: /sys/block/sdb
    subsystem: block
    device file: /dev/sdb
    symlink: /dev/block/8:16
    symlink: /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0
    symlink: /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    properties:
    ID_SERIAL_SHORT=574341505730373832303839
    DEVNAME=/dev/sdb
    DEVLINKS=/dev/block/8:16 /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    ID_MODEL=5000AAK_External
    ID_SERIAL=WD_5000AAK_External_574341505730373832303839-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    MINOR=16
    ACTION=add
    ID_VENDOR=WD
    ID_BUS=usb
    DEVPATH=/block/sdb
    ID_TYPE=disk
    ID_REVISION=1.06
    MAJOR=8
    SUBSYSTEM=block
    DEVTYPE=disk
    SEQNUM=1662
    action=add @ 10:13:45.839326
    device: /sys/block/sdb/sdb1
    subsystem: block
    device file: /dev/sdb1
    symlink: /dev/block/8:17
    symlink: /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0-part1
    symlink: /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0-part1
    symlink: /dev/disk/by-uuid/442a9a4c-ffd4-4d7f-b966-8c2935f7928f
    symlink: /dev/disk/by-label/500GB
    properties:
    ID_SERIAL_SHORT=574341505730373832303839
    ID_FS_LABEL=500GB
    ID_FS_LABEL_ENC=500GB
    DEVNAME=/dev/sdb1
    DEVLINKS=/dev/block/8:17 /dev/disk/by-id/usb-WD_5000AAK_External_574341505730373832303839-0:0-part1 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/442a9a4c-ffd4-4d7f-b966-8c2935f7928f /dev/disk/by-label/500GB
    ID_MODEL=5000AAK_External
    ID_SERIAL=WD_5000AAK_External_574341505730373832303839-0:0
    ID_INSTANCE=0:0
    UDEV_LOG=0
    ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0
    MINOR=17
    ACTION=add
    ID_VENDOR=WD
    ID_BUS=usb
    DEVPATH=/block/sdb/sdb1
    ID_TYPE=disk
    ID_REVISION=1.06
    ID_FS_USAGE=filesystem
    MAJOR=8
    SUBSYSTEM=block
    ID_FS_TYPE=jfs
    ID_FS_UUID=442a9a4c-ffd4-4d7f-b966-8c2935f7928f
    DEVTYPE=partition
    SEQNUM=1663
    ID_FS_UUID_ENC=442a9a4c-ffd4-4d7f-b966-8c2935f7928f
    I hope someone finds some useful informations in these lines!
    If you have some other test tools or command lines or whatever I could do to give you more or better informations, please let me know!
    p.s.: Right in this moment I was thinking about recompiling HAL with less patches, but even Arch uses many, so I'm not really sure which one or which combination could even be the reason. But I'll try it without any patch now right after posting this thread.

    I'm having a problem kind of like this. I have a 1TB Western Digital MyBook. It has the option of running in RAID0 or RAID1. I have it in RAID0 for more storage. My computer seems to find it, but it doesn't mount and it doesn't show up in /dev/.
    Here's what dmesg says when I plug it in
    usb 1-2: new high speed USB device using ehci_hcd and address 9
    usb 1-2: configuration #1 chosen from 1 choice
    input: Western Digital My Book as /class/input/input9
    generic-usb 0003:1058:0905.0004: input,hidraw3: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-2/input1
    Initializing USB Mass Storage driver...
    scsi2 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 9
    usb-storage: waiting for device to settle before scanning
    scsi 2:0:0:0: Enclosure WD My Book Device 104a PQ: 0 ANSI: 4
    scsi 2:0:0:0: Attached scsi generic sg2 type 13
    usb-storage: device scan complete
    tail /var/log/messages.log gives
    Feb 17 18:33:57 sage usb 1-2: new high speed USB device using ehci_hcd and address 9
    Feb 17 18:33:57 sage usb 1-2: configuration #1 chosen from 1 choice
    Feb 17 18:33:57 sage input: Western Digital My Book as /class/input/input9
    Feb 17 18:33:57 sage generic-usb 0003:1058:0905.0004: input,hidraw3: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-2/input1
    Feb 17 18:33:57 sage Initializing USB Mass Storage driver...
    Feb 17 18:33:57 sage scsi2 : SCSI emulation for USB Mass Storage devices
    Feb 17 18:33:57 sage usbcore: registered new interface driver usb-storage
    Feb 17 18:33:57 sage USB Mass Storage support registered.
    Feb 17 18:34:02 sage scsi 2:0:0:0: Enclosure WD My Book Device 104a PQ: 0 ANSI: 4
    Feb 17 18:34:02 sage scsi 2:0:0:0: Attached scsi generic sg2 type 13
    Feb 17 18:34:02 sage load-modules.sh: 'scsi:t-0x0d' is not a valid module or alias name
    The last line says that it can't find the "scsi:t-0x0d" module, but I can't find what I would need to enable to get that module. I can't find any related modules in the standard arch modules either. I'm using a custom kernel and I can't boot the standard arch kernel to test because it says something like "/dev/sda5" cannot be found and then it panics (the same startup options work fine on my custom kernel, the standard flips out for some reason).

  • HT203177 Time machine doesn't recognize my hard drive archive

    I have time machine archive on a hard drive (not time capsule). It recently stopped backing up. On checking, time machine recognizes the hard drive (in preferences it is listed as the back up drive.) The files appear to be present on looking into the drive, but Time Machine doesn't recognize that there are backup files there, it wants to complete another full backup. Meaning - it says for latest backup: "none".
    I am afraid if I do another full backup, I will lose the ability to access the older backups.
    When I try to access older files through time machine, it predictably cannot find them.
    How do I tell Time Machine that the files on that hard drive are the backup files?

    Update:
    1) Right click on TM icon - Menu choice "Browse other TM disks" allows me to see the data - i.e. it is a valid TM archive, not corrupted.
    2) Looking at TM preferences immediately after showed the proper disk was targeted, but still Latest backup: None.
    3) Shut down, anomalous shut down -required power button hit. (AHH - the problem??)
    4) restart using command  - R  works - i.e recognizes the disk and emergency recovery system software
    5) Restart - Still shows latest backup: None
    6) trying to access data through standard TM startup shows data now.
    7) go back to preferences - still no backup shown.
    Aside - I can't recall what the purple vs white dates on right side of the screen signify, and can't find it in the documentation right now. Anybody know?

  • Why doesn't my new hard drive come with Pages and Numbers?

    I just got a new hard drive installed in my Mac Book Pro.  It doesn't have Numbers and Pages as an included app.  How do I get those w/o having to pay the $40 app fee?

    If you previously downloaded them from the Mac App Store or associated them with an Apple ID, log into the Mac App Store with that Apple ID and download them from the Purchases tab.
    If you got them on an iWork DVD or with a Mac that originally shipped with 10.6.8 or earlier, install them from DVD.
    If you got them with a Mac that originally shipped with 10.7 or newer but didn’t associate them with an Apple ID, click here.
    (118314)

Maybe you are looking for

  • Pages not syncing with iCloud

    I am trying to figure out, why pages is not syncing with iCloud. I have Documents checked in the System Preferences of iCloud on my Mac Book Pro, I have Documents checked on my iPhone and I have the Pages app. Can someone shine some light on this iss

  • Strange display of query components in the report

    hey, when I create a query and execute the report, there are always these empty lines (sometimes 4 or so) between characteristics, key figures and free characteristics. Maybe it's important to tell you that I am using external hierarchies and variabl

  • Cant get noise reduction to work

    when I apply the noise reduction feature to a grainly picture nothing happens.  am I missing a step?

  • RAR 5.3 SP8 - Action Usage by User Report - Change Start Date?

    Hello, When we run the report "Action Usage by User" in RAR, it shows a default "Start Date" of 1/12/2009. RAR put this in there on its own. We never got the Action Usage Generation Job working correctly until a few weeks ago (we had some issues that

  • How to see all songs NOT stored locally on device?

    Hello, I am looking for a way to view songs that need to be downloaded on my iPod Touch FROM the device. The only way I see is to scroll through my songs (in the thousands) to look for songs with the cloud icon and tap it to start downloading. Is the