Thanks in advance for help

I am using 4.5 beta

I replaced an IDE data drive with an SATA data drive. When I reboot, both the parity drive and the other data drive are still assigned properly as they were before and as expected, the IDE drive is missing. When I go to the "Devices" I can pull down the menu that does have the new drive listed, but when I select the new drive it simply reverts back to the missing IDE drive.

Thanks in advance for help

I am using 4.5 beta

I replaced an IDE data drive with an SATA data drive. When I reboot, both the parity drive and the other data drive are still assigned properly as they were before and as expected, the IDE drive is missing. When I go to the "Devices" I can pull down the menu that does have the new drive listed, but when I select the new drive it simply reverts back to the missing IDE drive.

Post a syslog.  Don't think I've ever seen that behavior, but it sounds as if the new drive is not working properly.

 

 

What version "beta" (exactly) are you running?

If a recent one, you might be able to use your web-browser... simply browse to

//tower/log/syslog

to get to the syslog, then simply use the browser "File->Save-As" to save it to a syslog.txt file and attach it to your next post.

 

 

I will try a different drive. You are probably right.

 

 

It was either the drive i was using or the sata cable. I put in a different IDE drive and now that drive is blue and upgrading. Thanks. I will post more if i have anymore hardware to test.

Aug 11 14:40:25 Tower emhttp: put_disk_settings: fopen: Read-only file system

Your flash drive could not be written to, so the settings changes could not be saved.  When I checked the identification and setup of your flash drive, it indicated the following:

Aug 11 14:33:19 Tower kernel: scsi 0:0:0:0: Direct-Access     Memorex  Flashdrive 303B  PMAP PQ: 0 ANSI: 0 CCS

Aug 11 14:33:19 Tower kernel: sd 0:0:0:0: [sdd] 251648 512-byte hardware sectors: (128 MB/122 MiB)

Aug 11 14:33:19 Tower kernel: sd 0:0:0:0: [sdd] Write Protect is on

 

Perhaps there is a little switch on it that was bumped?

 

Edited to add:  Or it has reached the end of its life, used up all of its writes.