duderaid Posted December 9, 2009 Share Posted December 9, 2009 I'm running the latest beta 4.5b13 and I know the kernel supports the drives. I can see them when I want to configure the array, but once that is done I cannot start the array. Is there something that I am missing or does Unraid need something else compiled in to it to get the next step? All disks were cleared using the preclear script first. Thanks Aaron Link to comment
Joe L. Posted December 9, 2009 Share Posted December 9, 2009 I'm running the latest beta 4.5b13 and I know the kernel supports the drives. I can see them when I want to configure the array, but once that is done I cannot start the array. Is there something that I am missing or does Unraid need something else compiled in to it to get the next step? All disks were cleared using the preclear script first. Thanks Aaron To help you we need more clues... A copy of your syslog AFTER you assign the drives and press the "Start" button is needed. A screen shot of the main management page might help too. or at least explain what you see. (and what you don't see that you expected) Instructions on how to post a syslog under Troubleshooting in the wiki. Joe L. Link to comment
duderaid Posted December 10, 2009 Author Share Posted December 10, 2009 The big thing I see is the HDIO_GET_IDENTITY ioctl error: -22 I have attached the whole syslog. I couldn't find much on this or the super.dat errors. Dec 9 19:43:25 Tower emhttp: shcmd (47): modprobe md-mod super=/boot/config/super.dat slots=8,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Dec 9 19:43:25 Tower kernel: md: unRAID driver 0.95.3 installed Dec 9 19:43:25 Tower kernel: md: could not read superblock from /boot/config/super.dat Dec 9 19:43:25 Tower kernel: md: initializing superblock Dec 9 19:43:25 Tower kernel: md: import disk0: HDIO_GET_IDENTITY ioctl error: -22 Dec 9 19:43:25 Tower kernel: mdcmd (2): set md_num_stripes 1280 Dec 9 19:43:25 Tower kernel: mdcmd (3): set md_write_limit 768 Dec 9 19:43:25 Tower kernel: mdcmd (4): set md_sync_window 288 Dec 9 19:43:27 Tower emhttp: shcmd (48): rmmod md-mod >>/var/log/go 2>&1 Dec 9 19:43:27 Tower kernel: md: unRAID driver removed Dec 9 19:43:27 Tower emhttp: shcmd (49): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,32,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Dec 9 19:43:27 Tower kernel: md: unRAID driver 0.95.3 installed Dec 9 19:43:27 Tower kernel: md: could not read superblock from /boot/config/super.dat Dec 9 19:43:27 Tower kernel: md: initializing superblock Dec 9 19:43:27 Tower kernel: md: import disk0: HDIO_GET_IDENTITY ioctl error: -22 Dec 9 19:43:27 Tower kernel: md: import disk1: HDIO_GET_IDENTITY ioctl error: -22 Dec 9 19:43:27 Tower kernel: mdcmd (2): set md_num_stripes 1280 Dec 9 19:43:27 Tower kernel: mdcmd (3): set md_write_limit 768 Dec 9 19:43:27 Tower kernel: mdcmd (4): set md_sync_window 288 Link to comment
Joe L. Posted December 10, 2009 Share Posted December 10, 2009 as you discovered, the error is that your disk interface card does not support the ioctl call HDIO_GET_IDENTITY needed by unRAID. Dec 9 19:43:27 Tower kernel: md: import disk0: HDIO_GET_IDENTITY ioctl error: -22 Dec 9 19:43:27 Tower kernel: md: import disk1: HDIO_GET_IDENTITY ioctl error: -22 Normally, the HDIO_GET_IDENTITY call is only valid on ATA devices... and not on SATA or SCSI devices. You might send Tom at limetech a PM or email ,and point him to this thread. Yours is not the first disk interface to partially work. Perhaps your syslog will give him a clue or two. Link to comment
Kaygee Posted December 10, 2009 Share Posted December 10, 2009 Anyone know what a 9800S is? I've never heard of it before? Is it a typo and meant to say 9500S? Link to comment
duderaid Posted December 10, 2009 Author Share Posted December 10, 2009 Yep. My mistake. 9500S Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.