Aller au contenu principal

2015 Rescue Media does not see my USB3 external hard drives

Thread needs solution
Forum Member
Contributions: 8
Commentaires: 55

Hi Guy,

As the originator of this tread, I have made some progress, regarding this problem.

A long story, but I will try and keep it short.

Recently I procured a new PC, and found that I still experienced, intermittently, the ability to see my two Seagate external drives, using the Acronis boot media.

At the same time, I was experiencing some instability with my new PC booting up; occasionally it advised that "Overclocking had failed"; other times, the time had slipped, by an hour, and occasionally, I could not see my Seagate external drives.

In desperation, I reported the problems that I was experiencing to the manufacturer of my PC (Chillblast - A UK Company). They took control of my PC, using an online facility, and came to a conclusion that the problems, I was experiencing were caused by excessive bad sectors on my Seagate external drives!

I’m not sure how they performed the CHKDSK, but when they looked at the Event log (https://askleo.com/how_do_i_see_the_results_of_a_chkdsk_that_ran_on_boot/) this showed hundreds of errors – When I checked my Seagate external drives using the normal method (Properties, Tools Error Check), no errors were detected.

Since disconnecting my Seagate external drives, my new PC has proved stable; and I can always detect my new WD My Book external drive, with Acronis.

The supplier of my PC would not comment, on Acronis, but it looks to me, if external hard drives have too many bad sectors, this may prove problematic, to Acronis

 

 

 

 

 

Forum Member
Contributions: 14
Commentaires: 36

The 6673 (final, I believe) version of 2015, which you should be able to get without more $$, is also supposed to solve this problem (it did for me, although it was necessary to wait for some time for the drive list to get populated).

I agree 100% that the handling of this issue was terrible, and another similar episode would probably cause me to bail to one of the competitor products.

Also that the coders need to work on making the product less fussy.

Beginner
Contributions: 1
Commentaires: 5

Did you try to create a 'USB Pen drive as a universal restore  boot media' ? Were you successful with that. I have a CD created for the pupose and is successful  with that. But cannot create a Pen drive for the purpose, since that will be much faster than a CD.

My pen drive is not detected by Acronis TI2016 or even by the earlier versions, while my system detects the derive on all USB ports.

Dr. ABdul Rasheed

drkarasheed@gmail.com

 

Fichier attaché Taille
317365-124462.jpg 42.7 Ko
Forum Hero
Contributions: 57
Commentaires: 9276

Some pen drives report themselves as fixed drives rather than removeable drives and those that do will not work in creating recover media.  SanDisk drives are notorious for this.  You might try a different drive as I have found the cheap ones now available work fine.

Beginner
Contributions: 0
Commentaires: 5

Had a seagate 3TB backup solution , changed it out to a MY BOOK 3tb problem solved.

 

When you format the seagate hard drive to a partition below 270gb and the rest unformatted it sees it straight away so as a workround create a 10gb drive and a second max partition . seems to cure the issue. Also i noticed the seagate interface was recognised as a SCSI interface not a USB when using media boot. Soon as i purchased the MY BOOK i noticed the 3tb drive is recognised as a USB drive under media boot. Second  work around is to use 2014 as a recovery media as a backup works fine under windows using 2015 and 2016 under windows and restores fine using 2014, and the drive is recognised OK it only fails on the media in 2015 and 2016. (well actually it doesnt fail but it takes up to 22mins to recognise the 3tb drive, a 272gb drive takes 4 mins and under 270gb is seen straight away, because its seeing it as a scsi interface and doing a partition check?)

Conclusion? Acronis has an issue with the firmware on my seagate external usb drive. Acronis comes with MY BOOK so must have been tested. Acronis say they have tried a lot of seagate drives yet to confirm if mine was one of them but after all the testing i did for them i feel let down.

To be honest i have not fully tested this, these are my findings, after i gave up with the seagate and bought new drive i gave up. If you want to try and use your seagate then this might help otherwise by a MY book it worked for me? comes with free Acronis?

 

Forum Member
Contributions: 8
Commentaires: 55

Again, as the originator of this thread, I would add further comments!

I bought a new PC which instantly had problems booting up; it failed to see my Seagate drives, with Windows 10 media!

I contacted the manufacturer, Chillblast of the UK, who took control of my PC, using TeamViewer, and they performed CHKDSK on my two Seagate external drives.

Not sure how they did it, (not the normal way, in Windows 10) but they demonstrated to me that both my Seagate drives had excessive corrupt bad sectors.

I removed both drives, and this resolved my problems booting up. The manufacturer of my PC advised that drives with many bad sectors are frequently not detected/recognised, even in the BIOS

I bought myself a My Book 4TB excternal drive, and this works fine - I can detect this with Acronis Bootable media (2014, 2015 & 2016). 

So I am not sure whether my Seagate drives have always had too many bad sectors, and whether this has always been the cause of this problem (non detection by Acronis); if so my Seagate drives have been like this from new - Whatever, I shall stear clear of Seagate, in future. The WD drive appears very stable!

Beginner
Contributions: 0
Commentaires: 5

PS.

 

Although i had a seagate solution i opened up the unit and put other SCSI drives in it. Hitachi, samsung etc.  I put an old 75gb disk in there and the media saw it straight away on boot but still saw it as a SCSI. Made no difference it is most certainly the Firmware on the USB and how acronis reacts with it.

Never tried a backup whilst in the scsi state or a recovery as i was concentrating on why Acronis could not see it correctly and why over 270gb made a difference of 4 mins extra boot time for 272gb?

Un fortunaly there is no firmware upgrade on my particular USB3 and i got fed up with Acronis dragging their feet. The easiest solution was to buy another usb3. Alternativly if they do an external drive usb3  interface without the disk which i think i have seen then you can use the seagate drives. I have used the seagate in another usb2 backup shell and they work fine.

Look at deals out there i bought both my internal hard drives as usb2 external drives , ripped them apart and put them in my desktop. In fact i might even take the my book apart and use this as a multi drive backup solution.

 

 

Beginner
Contributions: 0
Commentaires: 8

That makes sence.  I've read on this forum someone waiting 45mins!  I wonder how long I'd have to wait for my Seagate 5tb USB 3 Expantion?  A few hours I imagine.   I'd like to test, but I tossed the recovery disc, and, have uninstalled ATI.  If I feel board and want to waste a few hours, I may install in a VM, update, and burn another disc to test.

I don;t mean to trash Acronis.  I'm just fed up with them, and have moved on.

Regular Poster
Contributions: 32
Commentaires: 180

I've read most of this thread, off and on- but I don't recall if anyone has had a chance to talk to Seagate about this problem?

Joe

Beginner
Contributions: 0
Commentaires: 8

I don't think so.  But, I think it's specific to Acronis and how they look at external usb drives.

My other backup software (AOMEI Backupper) that I have switched over to, does not have any issue with these same external usb drives.  AOMEI instantly sees the drives when booted from the recovery disc, or, from the pgm.  I havn't tried the 1-key recovery yet.

Mr. Krafts post about partion size and type is very interesting, and leeds me to further believe that Acronis is performing some type of scan on these drives - other than S.M.A.R.T..    

Someting changed with Acronis after TI2010.  Unfortunate forAcronis, and more unfortunate for all us customers who purchased their product.

Beginner
Contributions: 1
Commentaires: 5

I was reading all these posts for the last few days.

My grievance is different.

I cannot create a 'Bootable Pen drive forUniversal Restore' or Simply a 'Recovery bootable Pen drive'. I prefer a Pen drive because a USB 3 pendrive is read much faster than a DVD.

But still, there seems to be some thing in common. 'Acronis ATI 13,14,15 or 16 - not recognizing or detecting an external hard drive or Pen drive'.

I never had this issue with any of the other image backup appications like Macrium Reflect, EaseUS or Paragon. I have licensed versions for the first mentioned 3. So far, the best reliable one without any hitches anywhere, is Macrium Reflect.

Acronis support is perhaps the worst. But it seems that the Forums are keeping the customers with less troubles - but never without any. But to find out the specific topic on which I have to enter for a discussion, it takes very very long time. If the search facillity is improved, would have been muc easier.

The service from Acronis is over within one month of purchase of the Software.

By the time one finds out the troubles or issues the first one month is over. This actually is the main issue. They have service men all over, but this is ridiculous.

Regular Poster
Contributions: 66
Commentaires: 149

All versions of the Acronis rescue CD have this intermittent problem. I have often gotten a USB to show up if I first go into Windows and access the USB drive then bring the rescue CD up again. BUT 2015 does seem to have a permanent problem.

Forum Hero
Contributions: 70
Commentaires: 8346

drkarasheed - you can only create a recovery disk to a USB flash drive that is of the "removable" type.  You cannot create recovery disks with Acronis to a standard USB hard drive, or any drive that shows up in Windows as a "fixed" disk.  Acronis will not let you pick a "fixed" disk as they don't want anyone accidentally creating bootable media out on their backup drive or where the user is sure to have personal data.  It's a safety feature. 

There are some USB flash drives that are set as "fixed' disks by the manufacturer - primarily some sandisks that came out around Windows 8.1 to support Windows-2-go.  If you have one of these, it's a no-go for bootable media.  

However, there is a work-a-round.  You can always create recovery media on a removable flash drive adn take a full disk image of it.  Then restore that image to a regular UsB drive and you now have a bootable media on any type of disk.  In fact, I do this by paritioning a USB hard drive with 3 paritions... 1 parition in the front that is 2GB, a second 2GB partitions after that and the rest all data.  I restore my WinPE recovery media to parition 1, my Linux recovery media to parition 2 and I store my backup and portable apps on the main parition which is NTFS.  That way, I can easily restore newly created flash drive images to just the smaller partitions at the front of the USB drive and update the media as needed, without having to worry about formatting the main NTFS partition in the process.  I can then use my system boot override or one time boot menu and pick the partition I want to boot to (linux or WinPE).

`````````````````````````````````````

As Eddy mentioned, it is also best to ensure that your USB flash drive is plugged into the system and detected by Windows with a drive letter before launching Acronis.  If the drive is accessible to Windows and then Acronis is launched (and it is not of the "fixed" type), it will be selectable as an option to build recovery media.

Additional caveats... 1) use 32Gb or less... there are bootability issues with flash drives larger than 32Gb - see the sticky on the main page.   2) Drives that have been formatted with other tools may leave other hidden paritions that Windows cannot see (Windows will only show you 1 parition on flash drives).  As a result, instead of doing a quick format, do a full format of the flash drive to make sure any hidden paritions are wiped out too. 

Beginner
Contributions: 0
Commentaires: 10

I was having the lack of seeing seagate usb3 drives in recent days.

I just realized I was using the base TI 2015 (6525 ver) during my recent issues that are addressed in this post. 
The good news is I just booted with the TI 2015 (6613 ver) stand alone cd. 
It can see the seagate usb3 drive just fine now.

Thanks.
Lynn Sattler

Forum Moderator
Contributions: 237
Commentaires: 6949

Lynn Sattler wrote:

I was having the lack of seeing seagate usb3 drives in recent days.

I just realized I was using the base TI 2015 (6525 ver) during my recent issues that are addressed in this post. 
The good news is I just booted with the TI 2015 (6613 ver) stand alone cd. 
It can see the seagate usb3 drive just fine now

 Thank you for sharing your experience, Lynn! Yes, it's always recommended to use the latest available build

Beginner
Contributions: 0
Commentaires: 4

I've just discovered this thread, as it turns out I've just had a drive failure in a desktop. This box was acting as a server where we would keep all of our 'user' data off of our laptops. I bought new Seagate internal drives to replace the defective Toshiba drive (all internal). The 'data' drives are a couple of LaCie 1TB USB2.0 drives and the backup drives a couple of WD 'My Book' 2TB USB3.0 drives. The server is using ATI2015 to backup the data, one time backup of the server internal drive (image).

Since I bought a Seagate drive I downloaded the Disk Wizard, which is a modified ATI2020 and used it to create bootable media on a SanDisk thumb drive (since I couldn't find my original bootable 2015 CD).

When I attempted to recover the server image using the Linux bootable image it appeared to hang everytime I got to the point where I told it to 'proceed' ... I'd wait 20-25minutes, nothing. Note it always found all of the drives and was able to see all of the partitions on every disk.

Gave up on that and went and created a WinPE bootable media (as the helps files indicate, the Windows version may be more compatible with the hardware). Sure enough as soon as I hit 'Proceed', I got a screen that said something like 'Writing partitions ...' 8 Minutes remaining ... Turns out took 33minutes, and then booted from the internal hard drive.

So I take from that, that the Linux version of the bootable media still has issues ... regardless of what drives are attached to the USB ports.

I bought two Seagate internal drives and have been using the same bootable WinPE thumb drive to clone the boot drive after major changes (partition resize, major Windows updates, ATI2015 re-install ...) Always works.

 

So I'm going to make some copies of the WinPE bootable drive, just in case.