Hi all,
TL;DR I can’t boot with 2 drives, one is the system drive, and one is a 2.5” in an enclosure.
I’m back with a different problem than last time. bodhi was gracious enough to assist last time and the help was much appreciated.
My new issue is that I am now working with a Pogoplug Pro. I have installed Debian and its working fine. The WiFi works, if I wanted to use it, but I have it wired for now. I have it hooked up to be a LMS client / server.
However, and here is where the problem begins, I am unable to boot with two USB drives on the plug. When I do attempt to boot up, I get one of two different situations. I’ll explain below.
Let me first explain what I’ve tired. I’ve attempted to follow the following threads:
http://forum.doozan.com/read.php?2,5233,5957
& http://forum.doozan.com/read.php?2,7185
I have used a regular mounting, the LABEL mounting (where in I label a drive and use that label in the fstab file) and I’ve also tried to use the UUID method for identifying a drive as well.
I thought that the issue was that I was using a USB 3.0 enclosure for a 2.5” drive to hold the music that I wanted to auto mount on boot. When I used that enclosure, and I rebooted the plug, I was also pinging my plug from a Windows machine. It would alternate between these two responses when I attempted to boot:
The green LED would occasionally flash when I was in the boot process. But the Pogoplug never came up no matter how long I waited.
I’ve heard there can be issues with 3.0 devices, so I went out and bought a 2.0 enclosure. I might add, my system drive is a Sandisk Cruiser Fit (USB 2.0)
So after I had installed the drive into the 2.0 enclosure, I was getting a different issue. Now all I got was
Over and over. Also, not only did the greed LED flash, an amber one would flash. I counted the Amber one and it flashed 6 times, before going out and green came back.
Again, I’m thankful to anyone who might want to assist me in my discovery of a solution.
I know that with either enclosure, the drive was getting enough power, At least I assume so. I say that because I was able to mount it normally and then travel through the directory path and see the files I’d copied over.
I’m open to suggestion as to what I might try next. Thanks again!
TL;DR I can’t boot with 2 drives, one is the system drive, and one is a 2.5” in an enclosure.
I’m back with a different problem than last time. bodhi was gracious enough to assist last time and the help was much appreciated.
My new issue is that I am now working with a Pogoplug Pro. I have installed Debian and its working fine. The WiFi works, if I wanted to use it, but I have it wired for now. I have it hooked up to be a LMS client / server.
However, and here is where the problem begins, I am unable to boot with two USB drives on the plug. When I do attempt to boot up, I get one of two different situations. I’ll explain below.
Let me first explain what I’ve tired. I’ve attempted to follow the following threads:
http://forum.doozan.com/read.php?2,5233,5957
& http://forum.doozan.com/read.php?2,7185
I have used a regular mounting, the LABEL mounting (where in I label a drive and use that label in the fstab file) and I’ve also tried to use the UUID method for identifying a drive as well.
I thought that the issue was that I was using a USB 3.0 enclosure for a 2.5” drive to hold the music that I wanted to auto mount on boot. When I used that enclosure, and I rebooted the plug, I was also pinging my plug from a Windows machine. It would alternate between these two responses when I attempted to boot:
Request timed out. Reply from 192.168.1.35: Destination host unreachable.
The green LED would occasionally flash when I was in the boot process. But the Pogoplug never came up no matter how long I waited.
I’ve heard there can be issues with 3.0 devices, so I went out and bought a 2.0 enclosure. I might add, my system drive is a Sandisk Cruiser Fit (USB 2.0)
So after I had installed the drive into the 2.0 enclosure, I was getting a different issue. Now all I got was
Reply from 192.168.1.35: Destination host unreachable.
Over and over. Also, not only did the greed LED flash, an amber one would flash. I counted the Amber one and it flashed 6 times, before going out and green came back.
Again, I’m thankful to anyone who might want to assist me in my discovery of a solution.
I know that with either enclosure, the drive was getting enough power, At least I assume so. I say that because I was able to mount it normally and then travel through the directory path and see the files I’d copied over.
I’m open to suggestion as to what I might try next. Thanks again!