BRiT Posted July 20, 2010 Share Posted July 20, 2010 DISCLAIMER: This is the first time I'm using the cache drive feature. It functions under unRAID 4.5.6, but not unRAID 5.0 beta 1. I already have the drive setup as 4 partitions: Linux, Linux Swap, WinOS, and Linux Boot/Root. I followed the steps outlined in the thread "unRAID, Slackware Development system, & Windows"[ http://lime-technology.com/forum/index.php?topic=3899.0 ]. In Settings, Disk Settings, Cache I assign the drive, it shows as "pci-0000:00:1f.2-scsi-0:0:0:0 host0 (sda) wwn-0x50014ee0abdd9a95". When I start the array, the drive shows up as Unformatted because mounting failed. My first thought is shouldn't it try mounting /dev/sda1 instead of /dev/sda? My second thought is did I mess up the partition setup on the disk? And third thought was how LimeTech mentioned possibly changing partition detection for future advanced format drives and filesystems, but I don't think that was done in this early beta. What additional information is needed to troubleshoot? fdisk -l /dev/sda Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x4604798c Device Boot Start End Blocks Id System /dev/sda1 1 102927 826761096 83 Linux /dev/sda2 102928 107907 40001536 7 HPFS/NTFS /dev/sda3 107908 109152 10000462+ 82 Linux swap /dev/sda4 * 109153 121601 99996592+ 83 Linux Jul 20 13:24:40 Reaver emhttp: array_start Jul 20 13:24:40 Reaver emhttp: shcmd (137): udevadm settle Jul 20 13:24:40 Reaver emhttp: mounting disks Jul 20 13:24:40 Reaver emhttp: shcmd (138): mkdir /mnt/disk1 Jul 20 13:24:40 Reaver emhttp: shcmd (138): mkdir /mnt/cache Jul 20 13:24:40 Reaver emhttp: shcmd (138): mkdir /mnt/disk2 Jul 20 13:24:40 Reaver emhttp: shcmd (139): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Jul 20 13:24:40 Reaver emhttp: shcmd (140): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger Jul 20 13:24:40 Reaver emhttp: shcmd (141): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sda /mnt/cache 2>&1 | logger Jul 20 13:24:40 Reaver logger: mount: /dev/sda already mounted or /mnt/cache busy Jul 20 13:24:40 Reaver emhttp: disk21 mount error: 32 Jul 20 13:24:40 Reaver emhttp: shcmd (142): rmdir /mnt/cache /dev/root 98427444 9201992 84225624 10% / tmpfs 2005148 0 2005148 0% /dev/shm /dev/sde1 7835584 49376 7786208 1% /flash /dev/sda2 40001532 15285272 24716260 39% /win7 /dev/md1 1953454928 994196636 959258292 51% /mnt/disk1 /dev/md2 1953454928 829679360 1123775568 43% /mnt/disk2 shfs 3906909856 1823875996 2083033860 47% /mnt/user root@Reaver:~# mount /dev/root on / type ext3 (rw,relatime,errors=continue,data=writeback) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) tmpfs on /dev/shm type tmpfs (rw) /dev/sde1 on /flash type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) /dev/sda2 on /win7 type fuseblk (rw,allow_other,blksize=4096,default_permissions) Jul 19 17:08:13 Reaver emhttp.50b1: Device inventory: Jul 19 17:08:13 Reaver emhttp.50b1: pci-0000:00:1f.2-scsi-0:0:0:0 host0 (sda) wwn-0x50014ee0abdd9a95 Jul 19 17:08:13 Reaver emhttp.50b1: pci-0000:00:1f.2-scsi-1:0:0:0 host1 (sdb) wwn-0x50014ee2ad71c74d Jul 19 17:08:13 Reaver emhttp.50b1: pci-0000:00:1f.2-scsi-4:0:0:0 host4 (sdc) wwn-0x50014ee2581c623e Jul 19 17:08:13 Reaver emhttp.50b1: pci-0000:00:1f.2-scsi-5:0:0:0 host5 (sdd) wwn-0x50014ee202c6e6ff Jul 19 17:08:13 Reaver emhttp.50b1: pci-0000:03:00.0-scsi-0:0:0:0 host6 (sr0) no id unraid 4.5.6 information Jul 20 13:50:12 Reaver emhttp.456: Device inventory: Jul 20 13:50:12 Reaver emhttp.456: pci-0000:00:1f.2-scsi-0:0:0:0 host0 (sda) wwn-0x50014ee0abdd9a95 Jul 20 13:50:12 Reaver emhttp.456: pci-0000:00:1f.2-scsi-1:0:0:0 host1 (sdb) wwn-0x50014ee2ad71c74d Jul 20 13:50:12 Reaver emhttp.456: pci-0000:00:1f.2-scsi-4:0:0:0 host4 (sdc) wwn-0x50014ee2581c623e Jul 20 13:50:12 Reaver emhttp.456: pci-0000:00:1f.2-scsi-5:0:0:0 host5 (sdd) wwn-0x50014ee202c6e6ff Jul 20 13:51:06 Reaver emhttp.456: shcmd (34): udevadm settle Jul 20 13:51:06 Reaver emhttp.456: shcmd (35): mkdir /mnt/disk2 Jul 20 13:51:06 Reaver emhttp.456: shcmd (35): mkdir /mnt/disk1 Jul 20 13:51:06 Reaver emhttp.456: shcmd (35): mkdir /mnt/cache Jul 20 13:51:06 Reaver emhttp.456: shcmd (36): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Jul 20 13:51:06 Reaver emhttp.456: shcmd (37): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger Jul 20 13:51:06 Reaver emhttp.456: shcmd (38): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sda1 /mnt/cache 2>&1 | logger Jul 20 13:51:06 Reaver kernel: REISERFS (device sda1): found reiserfs format "3.6" with standard journal Jul 20 13:51:06 Reaver kernel: REISERFS (device sda1): using ordered data mode Jul 20 13:51:06 Reaver kernel: REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 20 13:51:06 Reaver kernel: REISERFS (device sda1): checking transaction log (sda1) Link to comment
limetech Posted July 20, 2010 Share Posted July 20, 2010 You are doing things correctly, this is a bug. Link to comment
dmenke Posted July 28, 2010 Share Posted July 28, 2010 I have a similar problem with my cache drive under 5.0 beta1. It showed up un-formatted after the upgrade. I went ahead and formatted it, as it was empty anyway. It formatted, and shows up ok on the main page. I double checked all the settings, but data goes right to the array, and skips the cache. Not a huge problem, but I thought I would let you know. Doug Link to comment
limetech Posted August 2, 2010 Share Posted August 2, 2010 Same bug. Fixed in -beta2 about to be released. Link to comment
bubbaQ Posted August 2, 2010 Share Posted August 2, 2010 "in -beta2 about to be released." :D :D Link to comment
Giraffeninja Posted October 16, 2010 Share Posted October 16, 2010 I'm having this same issue using Beta 2. Preclear the drive just to make sure. Assign the drive as cache, format it. All writes go directly to the array and not the cache drive. I made sure all shares are setup to use the cache drive. Am I missing something? Was it fixed in beta 2? Link to comment
Giraffeninja Posted October 16, 2010 Share Posted October 16, 2010 Ok so after mounting the cache drive and making a folder with the same name as one of the shares it appears to be working. Link to comment
sacretagent Posted November 29, 2010 Share Posted November 29, 2010 I'm having this same issue using Beta 2. Preclear the drive just to make sure. Assign the drive as cache, format it. All writes go directly to the array and not the cache drive. I made sure all shares are setup to use the cache drive. Am I missing something? Was it fixed in beta 2? Same ISsue here cache drive not been used by unraid 5.2 he even spins down and sits there doing nothing will try the share folder trick that was mentioned above but if this is necessary shouldn't the system have made these folders ? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.