April 4, 20179 yr Community Expert 2 minutes ago, hilljd00 said: Updated from 6.2 to 6.3. No errors reported but my cache drive has completely vanished. --- Apr 4 00:39:53 Daedalus emhttp: shcmd (84): /usr/local/sbin/update_cron &> /dev/null ... ... Apr 4 01:40:25 Daedalus emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall ---------------------------- In Daedalus/Main the cache drive presents as: Unmountable disk present: Cache • SanDisk_SDSSDHII480G_153648400405 (sdj) Syslog snippets are seldom sufficient.
April 4, 20179 yr Author Community Expert 5 minutes ago, hilljd00 said: What info would? Tools - Diagnostics, post complete zip.
April 4, 20179 yr Author Community Expert Since you have a cache pool maybe this would be more appropriate:
April 4, 20179 yr Community Expert One of you cache disks is bad, the HDD: 196 Reallocated_Event_Count 0x0032 021 021 000 Old_age Always - 2005 197 Current_Pending_Sector 0x0022 087 087 000 Old_age Always - 520 Try mounting the cache read only to copy the data:
April 4, 20179 yr Community Expert 38 minutes ago, hilljd00 said: See attached. daedalus-diagnostics-20170404-0347.zip In this case it may be best to first try to start the array after removing the HDD from the pool (assuming the pool was the default RAID1 profile), but you need to disconnect it from the server, unassigning it is not enough. If cache still unmountable then see the FAQ linked above.
April 4, 20179 yr How do I split the drives? As my SSD is 480GB and my 2.5" HDD is 500GB but it is only showing 490GB for both. I don't remember linking them?
April 4, 20179 yr Community Expert 6 minutes ago, hilljd00 said: How do I split the drives? As my SSD is 480GB and my 2.5" HDD is 500GB but it is only showing 490GB for both. I don't remember linking them? Since the cache doesn't mount you can't do a normal removal, power down, disconnect the HDD from the server and power back on. Linking was done when you added it to the pool. Edited April 4, 20179 yr by johnnie.black
April 5, 20179 yr Ok. I've pulled the faulty drive and it has automatically reassigned itself as the cache drive. The problem is the 'Shares' tab cannot see the drive. What am I doing wrong?
April 5, 20179 yr Community Expert 2 minutes ago, hilljd00 said: Ok. I've pulled the faulty drive and it has automatically reassigned itself as the cache drive Don't quite understand what you're saying but since your problem is not related to this release start a thread in the support forum and post new diags.
April 5, 20179 yr Author Community Expert 3 minutes ago, johnnie.black said: Don't quite understand what you're saying but since your problem is not related to this release start a thread in the support forum and post new diags. I will split his posts into General Support.
Archived
This topic is now archived and is closed to further replies.