airflow
Contributor
- Joined
- May 29, 2014
- Messages
- 111
Hi,
I have the problem that since after the recent stable update one of my pools couldn't be properly imported any more. Hardware is ASRock E3C226D2I, Intel Core i3-4130T, 2x 2.90GHz, Kingston ValueRAM DIMM Kit 16GB (ECC capable), Intel P3600 as the drive in question and some other harddrives which are not relevant.
The GUI showed in the volume manger "couldn't determine space (0)" (or similar) for the volume in question. I tried to "import volume" in the GUI, which didn't offer any volumes to import in the drop-down-list. "zpool import" on CLI just output nothing. I then tried to detach the volume in the GUI, which worked (without wiping disks of course). My idea was to then again try import the volume via CLI, to find out what is going wrong here. But still - "zpool import" just outputs nothing.
I have to say I don't really know how to troubleshoot this correctly. I read the documentation regarding importing volumes, but that didn't really help. The disk is correctly initalized when booting, dmesg shows it normally. The volume manager offers me to create a new volume with this disk, but I don't want to do this, as I prefer to import the existing pool of this disk.
I have an idea how I triggered this. I hammered the drive before the reboot with lots of write/read tests. After that I deleted 200GB of testdata. FreeNAS shows strange behaviour in combination with this drive regarding trim, which is exactly what happens when you delete loads of data. I guess I rebooted too early after this, when trimming was still in progress... My precious data is on another, redundant store. Still I'd like to learn from this experience - which options do I have here? Why is import failing?
Thanks for hints!
airflow
I have the problem that since after the recent stable update one of my pools couldn't be properly imported any more. Hardware is ASRock E3C226D2I, Intel Core i3-4130T, 2x 2.90GHz, Kingston ValueRAM DIMM Kit 16GB (ECC capable), Intel P3600 as the drive in question and some other harddrives which are not relevant.
The GUI showed in the volume manger "couldn't determine space (0)" (or similar) for the volume in question. I tried to "import volume" in the GUI, which didn't offer any volumes to import in the drop-down-list. "zpool import" on CLI just output nothing. I then tried to detach the volume in the GUI, which worked (without wiping disks of course). My idea was to then again try import the volume via CLI, to find out what is going wrong here. But still - "zpool import" just outputs nothing.
I have to say I don't really know how to troubleshoot this correctly. I read the documentation regarding importing volumes, but that didn't really help. The disk is correctly initalized when booting, dmesg shows it normally. The volume manager offers me to create a new volume with this disk, but I don't want to do this, as I prefer to import the existing pool of this disk.
I have an idea how I triggered this. I hammered the drive before the reboot with lots of write/read tests. After that I deleted 200GB of testdata. FreeNAS shows strange behaviour in combination with this drive regarding trim, which is exactly what happens when you delete loads of data. I guess I rebooted too early after this, when trimming was still in progress... My precious data is on another, redundant store. Still I'd like to learn from this experience - which options do I have here? Why is import failing?
Thanks for hints!
airflow